Migration

Migrate from PagerDuty or Opsgenie.

Moving off PagerDuty or Opsgenie is mostly about keeping your schedules, escalation policies and services intact while you stay on call. This page covers what the CallHeim importer reads, what to check after an import, and how to run it with a dry run first.

If you are on Opsgenie

Atlassian stopped selling Opsgenie on 4 June 2025. Opsgenie reaches end of support on 5 April 2027: access is shut off and customer data that has not been moved is deleted, so move or export what you need before then. Atlassian’s Opsgenie licensing page, checked 2026-10-19.

What your options are

Seven object types

What the importer reads.

The importer reads your PagerDuty or Opsgenie configuration from a US or EU account, and a dry run shows you the result before anything is written to your organization.

The importer reads users, teams, services, schedules with their layers, restrictions and overrides, escalation policies with every tier target, 90 days of incident history, maintenance windows and PagerDuty e-mail integrations. Notification preferences and integration keys are not carried over: CallHeim’s built-in paging steps apply until each person sets their own, and each sender gets a new CallHeim URL.

Where to find it. An organization admin runs the importer from the organization settings in the app, with a read-only token from PagerDuty or Opsgenie. CallHeim stores the imported data in AWS us-east-1, whatever the region of the old account. A live import that would take you over your plan’s seat limit is refused, so on the 5-seat trial run the dry run and the parallel run first.

  • extracts

    Users

    Name, e-mail, role, time zone and one phone number. People arrive as invited records, so they can receive e-mail pages before they sign in; you invite each person later. An imported phone number is used for text and call pages only after its owner verifies it.

  • extracts

    Teams

    Name and description.

  • extracts

    Services

    Name, description and team. A PagerDuty service also keeps its escalation policy; attach one to each Opsgenie service.

  • extracts

    Schedules

    Each layer with its rotation, members and on-call restrictions, plus upcoming overrides. A layer that has already ended in the old tool is skipped.

  • extracts

    Escalation policies

    Tiers and timeouts, up to 8 tiers, with every user, schedule and team target of each tier.

  • extracts

    Incidents

    Each incident’s log entries become its timeline, so analytics do not start from an empty chart. Imported incidents cannot be reopened or escalated.

  • extracts

    Maintenance windows

    Start, end and the service it applies to.

Incident history import covers the last 90 days, and imported incidents never page anyone. Re-running an import fills in what is missing and never overwrites changes you made in CallHeim.

After the import

What to review, and what is not migrated.

What needs review

  • Schedules: check who is on call now and at the next few handoffs against the old tool. A layer that had already ended is skipped, and a layer set to end on a future date keeps running until you remove it.
  • Escalation policies: every user, schedule and team target of a tier carries over. Check a tier that had a target of another kind, which is left out, a policy with more than 8 tiers, and the repeat count, which is reduced if the policy would otherwise outrun CallHeim’s escalation time limit.
  • Service links: a PagerDuty service keeps its team and escalation policy when both import, and an Opsgenie service keeps its team only, so attach an escalation policy to each one. If a team or policy did not import, the link points at nothing.
  • Maintenance windows: a window that covers several services is attached to the first one, and a window that targets something other than a service arrives without a service.
  • Imported users: they arrive as invited records, with no sign-in and no invite e-mail. They can be paged by e-mail before they sign in, and CallHeim’s built-in paging steps apply until each person is invited and sets their own. Texts and calls start only after your admin turns SMS and voice on and the person verifies a phone.
  • Seat limit: a live import that would take your organization over its plan’s seat limit is refused before anything is written. A dry run only notes it.

What is not migrated

  • Per-user notification preferences and channel order
  • Any vendor other than PagerDuty or Opsgenie
  • Integration secrets and routing keys — every sender needs a new CallHeim key
  • Per-team import — each run reads the whole vendor account

Worth the extra time

Checking escalation policies and schedules.

Of everything on the needs-review list, these two object types decide who gets paged, so compare them with the original before cutover, not during it.

Escalation policies

Tiers and timeouts import, up to 8 tiers, and a tier keeps every user, schedule and team target it had: a rule that notifies two people together arrives as one tier that pages both. After Import, open each imported policy and check what was left out: a target of any other kind, a tier past the eighth, and a repeat count that would outrun CallHeim’s escalation time limit, which is reduced to fit.

Schedules

Each schedule arrives with its layers, rotations, on-call restrictions and upcoming overrides. Before cutover, open the old schedule and the imported CallHeim schedule side by side and check who is on call now and at the next few handoffs. A layer that had already ended is skipped, and a layer set to end on a future date keeps running until you remove it. Fix any difference directly in CallHeim’s schedule editor.

The process

The recommended workflow.

Six steps. Only Import creates or updates anything in your CallHeim organization.

  1. 01Parallel run

    no organization write

    Forward alerts to CallHeim alongside your existing tool, so you can compare the two before anything changes for your team.

  2. 02Dry run

    no organization write

    CallHeim reads your PagerDuty or Opsgenie account with a read-only token; choose the United States or Europe region your account is hosted in. The dry run writes nothing to your CallHeim organization, and keeps a copy of the extract for the import.

  3. 03Review

    no organization write

    Open the report on the dry run to see the items that failed or were skipped, with the reason for each. Then compare your schedules, escalation policies and service links with the old tool, so you know the imported configuration pages the same people before you rely on it.

  4. 04Import

    writes to your organization

    Run the same process for real. It creates the mapped users, teams, services, schedules, escalation policies, incidents and maintenance windows in your organization. Re-running an import fills in what is missing and never overwrites changes you made in CallHeim. A failed or stalled run can be resumed, and Undo on the result card of a finished import deletes only what that import created and nobody has edited or used since.

  5. 05Re-point senders

    no organization write

    Give each alert source a new CallHeim integration URL and key. Existing PagerDuty or Opsgenie keys are not reused, and a tool with a fixed events.pagerduty.com endpoint cannot be repointed.

  6. 06Cut over

    no organization write

    Once the parallel run and the imported configuration look right, stop forwarding to the old tool and retire it.

Only Import creates or updates records in your CallHeim organization.

Running both tools in parallel

Run in parallel during a move: CallHeim receives PagerDuty Events API v1 and v2 requests and Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast (now SolarWinds Incident Response), Zenduty (now Xurrent IMR) and Grafana OnCall.

Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused.

Squadcast is now SolarWinds Incident Response, Zenduty is now Xurrent IMR, and the open-source Grafana OnCall project was archived on 24 March 2026.

When a run does not go to plan

  • A failed or stalled run can be resumed. You enter the token and pick the account region again, and it continues the same job instead of starting a new one.
  • On PagerDuty, teams, incident history and maintenance windows are optional reads: if your plan refuses one, that part is skipped with a note and the run carries on instead of failing.
  • The report on a finished run lists the failed and skipped items, each with its reason.
  • A finished live import can be undone from its result card. Undo deletes only the records that import created and that nobody has edited or used since; it keeps edited records, people who have signed in, incidents someone has worked on, and anything those depend on.
  • Undo itself cannot be reversed, so check your on-call coverage afterwards.

Questions

About migrating.

Can I migrate from PagerDuty?

Yes. Connect a read-only PagerDuty token, choose your account’s region and run a dry run to review the result before anything is written to your organization. Then run Import and re-point your senders one at a time.

Can I migrate from Opsgenie?

Yes. Forward alerts to CallHeim first: it accepts Opsgenie outgoing webhooks, so you can send alerts to both tools while you compare. Then run a dry run, review it and run Import. Finish well before 5 April 2027, when Opsgenie reaches end of support.

Is there a trial?

Yes. 14-day trial for up to 5 seats, no card required.

CallHeim

Start with the parallel run, not the cut-over.

Start a 14-day trial, connect one alert source and send yourself a test page.