Opsgenie new sales ended June 4, 2025; the service shuts down April 5, 2027 with permanent data deletion. Every customer migrates — the question is where. Seven realistic paths below, with the honest trade-offs. The deadline everyone forgets: export your alert history and audit logs before Atlassian deletes them; no vendor imports that archive for you.
The seven paths
1. OpsPing — the like-for-like move
Speaks the Opsgenie v2 alert API (GenieKey scheme): most integrations move by changing endpoint and key. Importer for users, teams, schedules, rotations, escalations, heartbeats, integrations. $8–$15/responder/month.
Watch out: Terraform config resources and some policy specifics are not drop-in; verify per integration.
2. Jira Service Management — Atlassian's sanctioned path
If you are consolidating on Atlassian ITSM, JSM keeps you in one ecosystem. Pricing is per agent (~$20 Standard, ~$51.42 Premium, annual, 2026 list).
Watch out: Atlassian's own migration tool drops deprecated notification policies, incident rules, and Opsgenie actions; on-call depth is not Opsgenie's.
3. PagerDuty — the enterprise incumbent
Most mature platform, 750+ integrations, active Opsgenie rescue program with contract buyouts. $21–$41/user/month.
Watch out: highest cost of the bunch; AIOps and automation are add-ons.
4. Grafana Cloud IRM — the observability-suite path
If your metrics and dashboards already live in Grafana Cloud, IRM keeps on-call in the same platform; usage-based pricing.
Watch out: locks you further into Grafana Cloud; billing is per monthly active user.
5. Better Stack — the monitoring bundle
Monitoring + on-call + status pages from one vendor; $29/responder/month annual plus add-ons.
Watch out: you buy a monitoring bundle; add-on pricing stacks.
6. incident.io — the Slack-native workflow
Great if incident response should live in Slack for the whole company; $15/user/month plus on-call add-on.
Watch out: per-seat pricing and on-call as an add-on; paging is not the core.
7. Squadcast — the reliability suite
On-call plus SLO tracking; Pro $20/user/month annual, now in the SolarWinds portfolio.
Watch out: suite breadth and enterprise packaging you may not need.
The migration checklist that actually matters
- Integrations first: inventory every tool that posts to Opsgenie. If you pick an Opsgenie-API-compatible platform (OpsPing), most just need a new endpoint and key.
- The can't-break layer: schedules, rotations, overrides, PTO, escalation chains. Import them — do not rebuild by hand at 11pm the night before cutover.
- Per-user notification rules: the safety nets Atlassian's migration drops. Recreate or import.
- Alert policies and forwarding rules: suppress/delay/enrich logic — map to the new platform's policy engine and dry-run before trusting it.
- Historical export: alerts, incidents, audit logs — before April 5, 2027, permanently.
- Verify with a real test alert through every path before flipping the rotation.
Full step-by-step with the API compatibility reference: the Opsgenie migration guide.
FAQ
When does Opsgenie shut down?
Support ends April 5, 2027, with permanent data deletion. Atlassian stopped new sales on June 4, 2025. Migration scheduling is already congesting — every Opsgenie customer moves in the same window.
What is the closest like-for-like Opsgenie replacement?
For teams whose integrations and automation are built on the Opsgenie v2 alert API, OpsPing is purpose-built for the move: same GenieKey auth scheme and documented API subset, importer for schedules and escalations, $8–$15/responder/month. Atlassian's designated path is Jira Service Management — a service desk with on-call around the edges.
How much lead time should we budget?
Small teams: an afternoon to a week (repoint integrations, import config, verify). Larger orgs with Terraform-managed configuration and many alert policies: plan a full on-call cycle of running both systems in parallel before flipping the rotation.