Migration
Migrate from PagerDuty, checklist first.
A PagerDuty migration is mostly about not breaking paging while you move. This is the checklist: forward alerts in parallel before you import anything, and cut over only once the comparison is boring.
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.
- 01
Inventory
List your PagerDuty services, schedules, escalation policies and users, and have a read-only PagerDuty API token ready. You will compare these against the import afterward.
- 02
Forward alerts in parallel
CallHeim accepts PagerDuty Events API v1 and v2 request bodies at a CallHeim integration URL, so tools that let you set the endpoint and key can be pointed at CallHeim alongside PagerDuty.
- 03
Run the dry run
Connect the read-only PagerDuty 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.
- 04
Review
Compare each imported schedule and escalation policy with the original, and check that every service pages through 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 PagerDuty.
- 06
Decommission
Retire the old PagerDuty integrations and routing keys once every sender is confirmed on CallHeim.
The process
What writes, and when.
- 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.
- 02Dry run
no organization write
CallHeim reads your PagerDuty 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.
- 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.
- 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.
- 05Re-point senders
no organization write
Give each alert source a new CallHeim integration URL and key. Existing PagerDuty routing keys are not reused, and a tool with a fixed events.pagerduty.com endpoint cannot be repointed.
- 06Cut over
no organization write
Once the parallel run and the imported configuration look right, stop forwarding to the old tool and retire it.
PagerDuty specifics
What is different about a PagerDuty move.
Event bodies are accepted as-is
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.
A fixed endpoint cannot be repointed
A tool that hard-codes events.pagerduty.com as its destination cannot be repointed at CallHeim; it needs a configurable webhook or integration URL. Check each sender before you plan a cut-over date around it.
From your PagerDuty account
What to check after the import.
Escalation policies and schedules decide who gets paged, so compare both with the original before you cut over.
- A PagerDuty service keeps its team and escalation policy when both import. If a team or policy did not import, the service link points at nothing.
- A PagerDuty maintenance window that covers several services is attached to the first one.
- Teams, incident history and maintenance windows are optional reads on PagerDuty: if your plan refuses one, that part is skipped with a note and the run carries on.
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.

Escalation policies in the CallHeim console: tiers, per-tier timeouts and a fallback target.
Questions
About the move.
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.
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.
Forward one sender before you touch the rest.
Start a 14-day trial, connect one alert source and send yourself a test page.