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. Nine 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.
What imports, and whether on-call is included
| Tool | What imports from Opsgenie | On-call scheduling included |
|---|---|---|
| OpsPing | Self-serve importer: users, teams, services, schedules and overrides, escalation policies, heartbeats, integrations; routing, policies, notifications and maintenance are review-gated. History is archive-only. Applying needs Team or Business | Yes, every plan (Free: 1 schedule) |
| Jira Service Management | Atlassian’s automated migration: alerts, on-call schedules, escalation policies, most integrations. Chat integrations are reconnected by hand; actions and incident rules move to Jira Automation | Yes, all plans (Free up to 3 agents) |
| PagerDuty | No self-serve importer documented. Vendor-run Professional Services migration for Opsgenie customers buying Operations Cloud Core (first 50, up to 250 users): users, contact methods, notification rules, teams, escalation policies, on-call schedules | Yes (Free: 1 schedule) |
| Grafana Cloud IRM | Self-serve open-source migration tool: user notification rules, schedules with rotations and overrides, escalation policies, supported integrations. Time-restricted schedules are not supported | Yes (free up to 3 active users) |
| Better Stack | Not documented | Yes, with a responder license |
| incident.io | Self-serve: schedules (with overrides) and escalation policies; users must be matched first | Paid add-on on Team and Pro; Basic has one schedule |
| Squadcast | Open-source migrator on GitHub: users, teams, squads, services, escalation policies, schedules (generates Terraform) | Yes |
| AlertKick | Self-serve: users (matched by email), schedules, escalation policies | Yes, every plan (Free: 1 roster) |
| FluidifyAI Regen | Self-serve importer (CLI and UI): users, schedules with rotations, and escalation policies; dry-run available. Does not import teams, overrides, or integrations | Yes, on the $100/month flat plan (30-day trial; no seat limits) |
Checked October 23, 2026 against each vendor’s own pages: Atlassian, PagerDuty, Grafana, incident.io, Squadcast, AlertKick. FluidifyAI Regen facts from FluidifyAI’s Opsgenie alternatives page (dated November 9, 2026; re-checked November 16, 2026). Better Stack and Grafana on-call inclusion per AlertKick’s Opsgenie alternatives guide. “Not documented” means we found no vendor documentation for it.
The nine paths
1. OpsPing — the like-for-like move
A paging-first Opsgenie alternative with a self-serve importer and a documented Opsgenie-compatible alert API. $15–$25/responder/month ($12–$20 billed annually), with unlimited stakeholders free on every plan. Feature parity, API caveats, cost (including the switcher discount), and the cutover steps are on OpsPing vs Opsgenie. To run the numbers, use the on-call cost calculator; the migration guide is the wizard walkthrough.
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 (Standard $21.50, Premium $55.28, annual list, as of Nov 2026). Side-by-side: OpsPing vs Jira Service Management.
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/user/month annual, $25 monthly (Professional, as of Nov 2026). Detail: PagerDuty vs Opsgenie.
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 ($34 monthly), as of Nov 2026, plus add-ons. Detail: Better Stack vs Opsgenie.
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 ($19 monthly) plus a $10 on-call add-on, as of Nov 2026. Detail: incident.io vs Opsgenie.
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; SolarWinds IR (formerly Squadcast) Pro is $15/user/month on annual billing, as of Nov 2026.
Watch out: suite breadth and enterprise packaging you may not need.
8. AlertKick — the per-server bundle
On-call plus uptime checks, a server agent and eBPF security, with flat plans priced by server rather than per user: Free plus paid tiers. Self-serve importer for users, schedules and escalation policies. OpsPing vs AlertKick →
Watch out: no automated voice calls; no SAML SSO or SCIM yet (per AlertKick’s own pages).
9. FluidifyAI Regen — the flat-price platform
Regen is $100/month flat, with no seat limits and a 30-day free trial (as of November 9, 2026). A built-in importer (CLI and UI) reads Opsgenie users, schedules with rotations, and escalation policies, including a dry-run mode; it does not import teams, overrides, or integrations, so those are rebuilt by hand. Paging covers Slack, Microsoft Teams, Telegram, SMS, and voice. Facts from FluidifyAI’s Opsgenie alternatives page ↗, re-checked November 16, 2026.
Watch out: integrations, teams and schedule overrides have to be rebuilt; FluidifyAI also notes there is no iCal calendar export for shifts yet.
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 — see setup guides for Datadog, Grafana, Zabbix, Google Cloud Monitoring, Uptime Kuma, Elastic/Kibana, and CloudWatch SNS.
- 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.
Moving your Opsgenie heartbeats
The OpsPing importer brings Opsgenie heartbeats across by name: interval and unit, enabled state, description, owner team (when that team is imported too), and the expiry alert’s message, tags and priority. Your cron jobs and scripts keep pinging the same heartbeat name. Change three things in the ping line: the host (api.opsping.com), the key (an OpsPing API key with write scope — the GenieKey header syntax still works), and the method. OpsPing accepts heartbeat pings as POST only, so a GET ping, the form Opsgenie’s docs show first, needs -X POST.
# Before: Opsgenie (EU accounts use api.eu.opsgenie.com)
curl -X GET 'https://api.opsgenie.com/v2/heartbeats/nightly-backup/ping' \
-H 'Authorization: GenieKey OPSGENIE_API_KEY'
# After: OpsPing (or -H 'Authorization: OpsPingKey OPSPING_API_KEY')
curl -X POST 'https://api.opsping.com/v2/heartbeats/nightly-backup/ping' \
-H 'Authorization: GenieKey OPSPING_API_KEY'
- Response: OpsPing answers
200with{"data":{"result":"pinged"},"took":…,"requestId":…}, not Opsgenie’sPONG - Heartbeat receivedtext, so update any script that checks the response body. - Unknown names: a ping for a name OpsPing has never seen creates that heartbeat with a 60-minute interval and P3 priority. Import first, then repoint, so each job keeps its real interval.
- Expiry and recovery: if no ping arrives within the interval, OpsPing opens an alert; the next ping closes it automatically.
- Plan: heartbeats are included on Team and Business.
Endpoint details are in the API reference.
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 that want a paging-first tool rather than a service desk, OpsPing is the like-for-like path on this list. The feature, API, cost, and migration-step comparison is on OpsPing vs Opsgenie. Atlassian's designated path is Jira Service Management — a service desk with on-call around the edges; see OpsPing vs Jira Service Management.
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.
Will our cron jobs keep pinging Opsgenie heartbeats after the move?
Yes, once each ping line is updated. The importer brings heartbeats across by name, so jobs keep the same heartbeat names. Change the host to api.opsping.com, use an OpsPing API key with write scope (the GenieKey header syntax still works), and send the ping as POST, because OpsPing does not accept GET, PUT or PATCH pings. See Moving your Opsgenie heartbeats.