Opsgenie dies on April 5, 2027, with permanent data deletion — the only real question is where your paging goes. OpsPing is the shortest path: it speaks the Opsgenie v2 alert API (GenieKey scheme), so most integrations move by changing the endpoint and key, and the importer carries over users, teams, schedules, rotations, escalations, heartbeats, and integrations. Atlassian's sanctioned path, Jira Service Management, is a service desk with on-call added — and its own migration tool drops deprecated notification policies, incident rules, and Opsgenie actions. If you need deep Atlassian ITSM anyway, JSM may still be right; if you need a pager, this is a like-for-like move.
Side by side
| OpsPing | Opsgenie | |
|---|---|---|
| Status | Live and shipping | Shut down April 5, 2027 — permanent data deletion |
| Free tier | Up to 5 responders, unlimited push | Legacy free tier ended with new sales (June 2025) |
| Paid pricing | $8–$15/responder/month | Was $9–$13/user/month (legacy list) |
| Alert API | Opsgenie v2-compatible (GenieKey scheme, documented subset) | v2 alert API (the reference) |
| Integrations | Change endpoint + key; verify each before cutover | 200+ integrations |
| Push delivery | iOS Critical Alerts, Android DND-bypass alarms, per-severity sounds | Mobile push with known silent-mode failures on Android |
| Status pages | Included | Required Atlassian Statuspage separately |
| Postmortems | One-click from audit trail, MD/PDF | Not native (incident timeline only) |
| Private deployment | Private single-tenant deployments available | Opsgenie Edge (legacy on-prem agent) |
Opsgenie legacy list prices shown for reference; new sales ended June 4, 2025 (atlassian.com). Checked October 16, 2026.
What transfers — and what does not
Schedules (rotations, overrides, PTO), escalation policies, users, teams, heartbeats, and integrations import. Alert API calls keep working with a host and key change — the GenieKey header and v2 alert shape are supported. Not drop-in: Terraform configuration resources, Opsgenie forwarding-rule and policy specifics beyond the shipped policy engine, and Edge-based on-prem ingestion. The full mapping is in the Opsgenie migration guide.
Why not just move to Jira Service Management?
You can — it is Atlassian's sanctioned path, and if your org standardizes on Atlassian ITSM it is coherent. The costs: JSM is priced per agent, its on-call depth is not Opsgenie's, the migration tool drops deprecated automation, and Compass (Atlassian's other landing spot) sunsets in 2027 too. Full JSM comparison →
Move before the deadline crunch
Every Opsgenie customer migrates in the same 2026–2027 window. Moving early means no calendar pressure and free migration support.