Migration
Opsgenie migration checklist, for a move to CallHeim.
Atlassian's own end-of-support date gives every Opsgenie customer a deadline. This is the checklist: forward alerts in parallel before you import anything, and decommission Opsgenie well before the shutdown date rather than on it.
Competitor information last verified September 2026. Sources are linked beside each fact.
Cut-over checklist
Six steps, in order.
- 01
Inventory
List your Opsgenie teams, services, schedules, escalation policies and users. This is what the importer will read.
- 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.
- 03
Run the dry run
Connect a read-only Opsgenie token and review the counts of what would map and what would fail.
- 04
Review
Check schedule layers and overrides, and relink any service that is not pointed at the right escalation policy.
- 05
Cut over
Once the parallel run and the imported configuration look right, re-point the remaining senders and stop sending to Opsgenie.
- 06
Decommission
Retire the old Opsgenie integrations well before 2027-04-05 — the date Atlassian shuts Opsgenie down and deletes data not already moved.
The process
What writes, and when.
- 01Parallel run
no workspace write
Forward alerts to CallHeim alongside your existing tool, so you can compare the two before anything changes for your team.
- 02Dry run
no workspace write
CallHeim reads your PagerDuty or Opsgenie account with a read-only token. The dry run writes nothing to your CallHeim workspace, and keeps a copy of the extract for the import.
- 03Review
no workspace write
Check what the dry run mapped and what it could not. Schedule layers and overrides may arrive empty, escalation rules keep only the first target of each tier, and team and service-to-policy links need checking by hand.
- 04Import
writes to your workspace
Run the same process for real. It creates the mapped users, teams, services, schedules, escalation policies, incidents and maintenance windows in your workspace. Re-running an import updates the same records instead of duplicating them, and overwrites edits made to imported records.
- 05Re-point senders
no workspace 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.
- 06Cut over
no workspace write
Once the parallel run and the imported configuration look right, stop forwarding to the old tool and retire it.
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 bodies, Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast, Zenduty and Grafana OnCall.
Every sender needs a CallHeim integration URL and key; existing PagerDuty routing keys are not reused.
Priority mapping
Opsgenie’s P5 priority is clamped to CallHeim’s lowest severity, P4 — CallHeim has no P5 equivalent.
Opsgenie end of support is 5 April 2027: access is shut off then, and data not migrated by that date is deleted. (Atlassian Opsgenie licensing page, checked 2026-09-24)
The Opsgenie REST API keeps working until the end-of-support date, so a dry run or a re-point can still read it up to 2027-04-05.
From your Opsgenie account
What migrates from Opsgenie.
Users
Name, e-mail, role and one phone number. Imported as invited records — each person still has to be invited to sign in.
Teams
Name and description.
Services
Name, description and team.
Schedules
Created as a shell; layers, overrides and restrictions come from whatever the vendor API returns for that schedule.
Escalation policies
Tiers and timeouts, up to 8 tiers.
Incidents
The last 90 days of history, so analytics do not start from an empty chart.
Maintenance windows
Start, end and the service it applies to.
Before you commit
What needs manual review after migration.
- Schedule layers and overrides: the extractor requests a plain list, so layers, overrides and phone contact methods may arrive empty depending on what the vendor API returns.
- Escalation rules: only the first target of each tier carries over.
- Team and service links: services are written before their escalation policy, so an imported service may not page through the right policy until you relink it.
- Imported users: they arrive as invited records and are not reliably pageable until they sign in.
Import tooling (early access) reads your PagerDuty or Opsgenie configuration (US-region accounts); an optional dry run lets you review the result before anything is written to your workspace.
Recreate by hand where needed
Rebuilding schedules and escalation policies in CallHeim.
Schedule layers, overrides and escalation targets are exactly the fields the importer flags for manual review above. This is the mapping to use when you rebuild them directly rather than wait on the import.
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.
Coverage gaps are shown in the console; they are not alerted in advance.
Escalation policies: tiers, timeouts and fallback
Escalation runs on an AWS Step Functions state machine: an unanswered tier times out and advances to the next tier or the fallback.
Escalation policies have up to 8 tiers, per-tier timeouts from 1 to 240 minutes, and a mandatory fallback target.
- 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.
Escalation rules: only the first target of each tier carries over. Recreate each tier by hand where a rule had more than one target, and make sure every alert source is bound to a service whose escalation policy you have rebuilt — an unbound source pages nobody.
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.
What an escalation policy looks like once rebuilt in CallHeim (example data).
Questions
About the move.
Can I migrate from Opsgenie?
Atlassian ends Opsgenie support on 5 April 2027; data not moved by then is deleted. Import tooling (early access) reads your PagerDuty or Opsgenie configuration (US-region accounts); an optional dry run lets you review the result before anything is written to your workspace. CallHeim also accepts Opsgenie outgoing webhooks, so alerts can be forwarded to both platforms during a parallel run.
Is there a trial?
CallHeim is in early access. 14-day trial with up to 5 seats and no card required. Adding a user beyond a plan’s seat limit is refused (Trial 5, Starter 10, Pro 50, Business 200); existing users and paging are not affected.
How does pricing work?
Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated. Paid plans are activated directly by the CallHeim team. Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; email-to-alert (per-workspace inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.
Forward one sender before the shutdown date decides for you.
CallHeim helps teams stay in control when critical systems are not. Explore the platform, connect one source, and send yourself a page.
Early access · every workspace starts with a 14-day trial for up to 5 seats, no card required