Atlassian is retiring Opsgenie. A team that still pages through it has to be somewhere else by 5 April 2027.
4 June 2025
End of sale
No new customers or edition changes.
5 April 2027
End of support
Access stops. Data that wasn't migrated is deleted.
Large teams mostly follow Atlassian's path. This guide is for a team of two to ten people that used Opsgenie for three things: waking whoever is on call, escalating when they don't answer, and noticing when a scheduled job stops checking in.
Where Atlassian wants you to go
Atlassian offers two destinations: Jira Service Management or Compass, through an in-product migration tool (source). Jira Service Management is a service desk with alerting inside it. Compass is a developer portal. If your support queue already runs in Jira Service Management, moving the alerts there is the shortest path.
If it doesn't, look at what the plan you would land on keeps.
What a small team loses on the cheaper plans
On Jira Service Management Free and Standard, heartbeats, voice notifications and incoming call routing are Premium and Enterprise only (source).
For a team that relied on Opsgenie heartbeats to catch a backup that didn't run, that means paying for Premium or finding heartbeats somewhere else. Even on Premium there is work to do: Heartbeat URLs move from opsgenie.net to atlassian.net, so every script that pings one has to change (source).
The other options
PagerDuty
The default for larger engineering organisations: SMS and voice calls, Android and incident workflows, priced per user. Its free plan has one schedule and one escalation policy. Acciti vs PagerDuty has the numbers.
Better Stack
Uptime monitoring, status pages and on-call in one product, priced per responder. Worth a look if you also want your sites checked from outside. Acciti vs Better Stack.
Grafana OnCall
Many roundups written this year still recommend the open-source edition as the free choice. It isn't one any more: Grafana OnCall's open-source edition was archived on 24 March 2026, and its mobile push, SMS and phone alerts stopped working (source).
Acciti
Acciti covers the three jobs above and nothing past them. An emergency repeats until someone acknowledges it, then climbs your escalation policy through the rotation. Heartbeats watch your cron jobs. Grafana, Sentry, Better Stack and your own scripts send alerts in. One Team plan covers everyone.
It doesn't call or text, has no Android app and keeps no incident timeline. If your rota needs any of those, pick one of the products above. Acciti vs Opsgenie puts the two side by side.
A checklist for moving
- Export your schedules, escalation policies and heartbeat list now. For a small team, a screenshot of each schedule is enough.
- List every integration that sends Opsgenie an alert. Search your code and your monitoring for
opsgenie.comandopsgenie.net. - Build the rotation and escalation policy in the new tool, and invite everyone on the rota.
- Point each integration at the new tool and send one test alert through each.
- Replace every heartbeat URL in your cron jobs, and confirm each one checks in.
- Send a test emergency with nobody answering, and check that it reaches the second person on the policy.
- Run both for a week before turning Opsgenie's integrations off.
Opsgenie and Grafana details as their own pages stated them on 21 October 2026.