Migration

Opsgenie migration checklist, for a move to CallHeim.

Opsgenie reaches end of support on 5 April 2027. This is the checklist: forward alerts in parallel before you import anything, and finish the move with margin before that date.

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.

Competitor information last verified October 2026. Sources are linked beside each fact.

Cut-over checklist

Six steps, in order.

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. 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.

  1. 01

    Inventory

    List your Opsgenie teams, services, schedules, escalation policies and users, and have a read-only Opsgenie API token ready. You will compare these against the import afterward.

  2. 02

    Forward alerts in parallel

    CallHeim receives Opsgenie outgoing webhooks, so you can forward alerts to CallHeim alongside Opsgenie and compare before anything changes for your team.

  3. 03

    Run the dry run

    Connect the read-only Opsgenie token, choose your account’s region (United States or Europe), and review the counts of what would map and what would fail. The report lists each failed or skipped item with its reason.

  4. 04

    Review

    Compare each imported schedule and escalation policy with the original, and attach an escalation policy to every imported service: Opsgenie services import with their team only.

  5. 05

    Cut over

    Once the parallel run and the imported configuration look right, re-point the remaining senders and stop sending to Opsgenie.

  6. 06

    Decommission

    Retire the old Opsgenie integrations before Opsgenie reaches end of support on 5 April 2027.

The process

What writes, and when.

  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 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 Opsgenie keys are not reused.

  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.

Opsgenie specifics

What is different about an Opsgenie move.

Outgoing webhook to CallHeim

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.

Priority mapping

Opsgenie priorities P1 to P4 arrive as the same CallHeim severities, and Opsgenie P5 alerts arrive as P4.

From your Opsgenie account

What to check after the import.

An Opsgenie service keeps its team only, so attach an escalation policy to each imported service. Then compare each schedule and escalation policy with the original.

What the importer reads, what to review and what is not migrated are on the migration hub, with the same list for PagerDuty and Opsgenie.

Read the full review list →

How they map

Schedules and escalation policies in CallHeim.

Schedules and escalation policies are the two objects to compare with the original after an import. This is how Opsgenie's concepts map onto CallHeim, and the mapping to use if you would rather rebuild one directly than import it.

Schedules: rotations, layers, overrides and time zones

Teams with member rosters own schedules and link to escalation policies. Schedules use any IANA time zone.

Schedules support layers, an override that sits above the layers, layer restrictions to weekdays, business hours or nights, follow-the-sun templates, time off, shift-swap requests with approval, and coverage-gap detection with suggested fills.

Opsgenie rotations
A schedule made of one or more layers — the base rotation is a single layer.
Opsgenie layers
Schedule layers, stacked in order.
Opsgenie overrides
An override that sits above the layers and takes precedence.
Opsgenie time zones
Any IANA time zone, set per schedule.

Escalation policies: tiers, timeouts and fallback

An unanswered tier times out and the escalation moves to the next tier, ending at the fallback.

Escalation policies have up to 8 tiers, each paging a person, a team or a schedule, with per-tier timeouts from 1 to 240 minutes, optional repeats and a mandatory fallback. The whole chain must fit within 24 hours.

Opsgenie escalation rule tiers
Up to 8 tiers per policy.
Opsgenie per-step timing
A per-tier timeout from 1 to 240 minutes.
Opsgenie next escalation / repeat
An unanswered tier times out and advances to the next tier automatically.
Opsgenie final notify / catch-all
A mandatory fallback target, required on every policy.

The importer keeps every user, schedule and team target of an escalation rule, up to 8 tiers. Check any tier that had a target of another kind, which is left out. Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged.

For the full mechanics of tiers, timeouts and fallbacks, see the escalation policy guide; for rotation design, layers and time-zone handling, see the on-call rotation guide.

A list of escalation policies showing their tiers, fallback target and repeat count
Escalation policy

Escalation policies in the CallHeim console: tiers, per-tier timeouts and a fallback target.

Questions

About the move.

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.

How does pricing work?

Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated. Alerts are not metered or billed. Seat caps are the only published plan limits. Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; audit-log export, an IP allowlist for administrative changes, private status pages and SCIM user provisioning on Business and above; email-to-alert (per-organization inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.

CallHeim

Forward one sender before the support date decides for you.

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