Last updated
To switch from Opsgenie to OpsPing, export a backup and import your users, teams, schedules and escalation policies with the OpsPing migration wizard, then repoint each alert source to api.opsping.com with a new OpsPing key. Run both systems in parallel and test a firing and a resolution through every source before you move the rotation. Opsgenie support ends April 5, 2027 (timeline); the import dry run is free and applying it requires the Team or Business plan.
Steps
Inventory everything that talks to Opsgenie
List every alert source (Alertmanager, Grafana, Datadog, CloudWatch, custom scripts calling the Opsgenie API), every heartbeat ping, every @opsgenie.net email integration, and any Terraform that manages Opsgenie resources. Note which sources rely on Opsgenie closing alerts by alias when a problem resolves — those need the webhook path in step 4.
Export a backup and choose how much history to keep
Open the OpsGenie migration wizard, verify your email, pick the US or EU Opsgenie region, and provide an Opsgenie API key that can read your configuration. Choose no history, the last 30, 90 or 365 days, or all available. The backup arrives as AES-256 encrypted ZIPs. Historical alerts and incidents are archive-only: they are never imported or paged in OpsPing.
Import your configuration
Sign in as an administrator of the destination OpsPing tenant and review the plan before approving it. The import runs in dependency order: users, teams, services, schedules and overrides, escalation policies, heartbeats, then integrations. Routing, alert policies, notification rules and maintenance are separate review-gated groups that are off unless you select them. A dry run is free on any plan; applying the import requires Team or Business.
Repoint each alert source with a new OpsPing key
For every source, change both the destination and the credential. There are three paths, and you can mix them:
- Opsgenie-compatible API: point the tool at
https://api.opsping.comand use a new OpsPing API key with theGenieKeyheader. Creation, deduplication by alias, and actions by alert ID work; close by alias does not. Details and copy-paste configs are on the API compatibility page. - Native webhook integration: for Alertmanager, Grafana, Datadog and CloudWatch, OpsPing's webhook mappers create alerts and close them automatically on resolution.
- Email: every OpsPing integration has its own
@alerts.opsping.comaddress to replace an@opsgenie.netone;[P1]–[P5]subject tags set priority.
Update heartbeat pings
Heartbeats import by name, so jobs keep the same heartbeat names. Change the host to api.opsping.com, use an OpsPing key with write scope (the GenieKey header syntax works), and send pings as POST — OpsPing does not accept GET, PUT or PATCH pings. Import before you repoint: a ping for an unknown name creates a new heartbeat with a 60-minute interval.
Get every responder's phone ready
Have each responder install the OpsPing mobile app, sign in, and allow push notifications, including iOS Critical Alerts or Android Do-Not-Disturb bypass. On Team and Business, add a verified voice number as the urgent fallback and email for lower-urgency context. OpsPing does not use SMS.
Run both systems in parallel and test every path
Keep Opsgenie live while OpsPing receives the same alerts. For each source, send one firing and one resolution and confirm priority, tags, team and service routing, who was paged, deduplication, and that the alert closes. Small teams often finish this in an afternoon to a week; larger organizations with many policies or Terraform-managed config should plan for a full on-call cycle in parallel.
Cut over, then retire Opsgenie
Move the rotation to OpsPing at a shift handoff, remove the Opsgenie destinations from each tool, and keep the exported archive somewhere durable. Atlassian deletes data that was not moved to Jira Service Management on April 5, 2027 (Atlassian ↗).
What moves, and what does not
| Item | How it moves |
|---|---|
| Users, teams, services | Imported, with existing matching resources identified rather than recreated |
| Schedules, rotations, overrides | Imported; unsupported cases are listed in the import report |
| Escalation policies | Imported; review mapped responders and order before approving |
| Heartbeats | Imported by name; pings must switch to POST |
| Alert API senders | Repoint URL and key; supported subset only (see API compatibility) |
| Alert and notification policies | Exact mappings are review-gated; lossy rules stay manual |
| Email integrations | Replace each @opsgenie.net address with the integration's @alerts.opsping.com address |
| Historical alerts and incidents | Archive-only download; never imported |
| Opsgenie Edge, analytics, Jira Service Management features | Not migrated |
The full wizard reference, including the advanced CLI path, is in the Opsgenie migration guide. If you are still deciding where to go, see Opsgenie alternatives and OpsPing vs Opsgenie.
Plans
Free covers 5 responders, 1 team, 1 schedule, a single-level escalation policy, 3 integrations, and unlimited push. Team is $8 per responder per month and Business is $15, both with unlimited schedules and multi-level escalations, voice fallback, and email delivery. See pricing.
FAQ
How long does switching from Opsgenie take?
Small teams can usually repoint integrations, import configuration and verify in an afternoon to a week. Larger organizations with Terraform-managed configuration and many alert policies should plan to run both systems in parallel for a full on-call cycle before moving the rotation.
Do I have to rewrite my integrations?
Usually not. Tools that send to the Opsgenie v2 alert API can be repointed to api.opsping.com with a new OpsPing key using the GenieKey header. Sources that auto-close alerts by alias should use OpsPing's native webhook integration instead, because close by alias is not part of the supported subset.
What does the import cost?
The importer dry run is free on every plan. Applying an import requires the Team plan ($8 per responder per month) or Business ($15 per responder per month).
Are historical Opsgenie alerts imported?
No. History can be included in the encrypted backup for your records, but historical alerts and incidents are archive-only and are never imported or paged in OpsPing.
Can we keep Opsgenie running while we test?
Yes. Atlassian says existing customers can keep using Opsgenie until end of support on April 5, 2027, so you can run both in parallel and send each alert source to both while you verify.
Opsgenie® is a trademark of Atlassian. OpsPing is not affiliated with, sponsored, or endorsed by Atlassian.