Opsgenie sunsets 5th April 2027: upgrade to Oppex
Opsgenie sunsets 5th April 2027. Atlassian has announced that it keeps working until 5 April 2027; after that it is shut down, and any data not moved is deleted. Since 4 June 2025 you can no longer change your Opsgenie edition. Atlassian points customers to Jira Service Management, priced per agent, or to Compass for alerting and on-call next to a component catalog.
So every Opsgenie team has to move. The only real decision is where — and since you are changing tools anyway, this is the moment to pick the one built for engineering incident response, not the default.
The default move, and what it gets you
Jira Service Management is a good product for what it was designed to do: IT service management. It is built around tickets, request portals and IT assets, with alerts and on-call as one part of it. For an engineering team that used Opsgenie to get paged and fix production, that is a lot of service desk around a small piece of what you actually used.
Two other things are worth knowing before you accept the default:
- The AI you want sits on a higher tier. AI alert grouping and advanced incident management come with JSM Premium; status pages only with Enterprise.
- Finding the cause is still manual. Getting the right people in and digging for the cause still take up most of the incident clock.
What Oppex does instead
Oppex is built only for engineering incidents: noise reduction, on-call, AI investigation, fixes and reporting in one place.
- Related alerts are grouped into one incident before anyone is paged, with the reason for each grouping shown.
- Oppex Nova checks deploys, metrics, logs, traces, past incidents and runbooks, and gives you the likely cause, a confidence level and a recommended fix in about two minutes.
- You approve the fix in Slack and it runs; automated runbooks act where your policy allows.
- The root-cause report is drafted for you, with owners, due dates and Jira links — so you keep using Jira for the follow-ups.
Oppex proposes; your engineers decide. Every finding links to the signal behind it, and nothing runs automatically on a guess.
You have to move off Opsgenie. Choose where.
Side by side: Oppex Business and JSM Premium
| Oppex Business | JSM Premium | |
|---|---|---|
| Built for | Engineering incident response and on-call | IT service management, with alerts and on-call |
| Alert noise reduction | In every Oppex plan, with the reason shown | AI alert grouping on Premium and Enterprise |
| AI root-cause analysis | Evidence and confidence level in about two minutes | Root cause analysis inside the incident ticket (Rovo) |
| Status pages | Included in Business | Enterprise plan only |
| Pricing model | Published price per user; unlimited incidents | Per agent, priced in agent tiers |
What it costs
JSM Premium is the like-for-like plan, because it is where Atlassian puts AI alert grouping and advanced incident management. Oppex Business includes both, plus status pages:
| Team size | Oppex Business | JSM Premium | You save each year |
|---|---|---|---|
| 10 users | $2,400 | $6,200 | $3,800 (61%) |
| 20 users | $4,800 | $14,500 | $9,700 (67%) |
| 50 users | $12,000 | $28,000 | $16,000 (57%) |
Annual list prices from Atlassian's public pricing page, October 2026, for the 6–10, 16–25 and 26–50 agent tiers. JSM Standard ($2,700 / $6,100 / $11,000 a year at those sizes) does not include AI alert grouping or advanced incident management. More detail in the full Oppex vs. Opsgenie comparison.
A plan that finishes well before the deadline
Every month closer to April 2027 leaves less room to test the new tool before you depend on it. Start now and the whole move takes four weeks:
- Week 0 — free noise audit. Send one week of alerts; we show you your noisiest services and agree a success target.
- Week 1 — shadow mode. Opsgenie keeps paging as normal. Oppex receives a copy of every alert, groups and investigates it, and pages nobody.
- Weeks 2–3 — side by side. Oppex pages for your pilot services, with Opsgenie still on as a backup.
- Week 4 — your decision. We review pages, noise, MTTA, MTTR and hours saved against the target. If we miss it, Opsgenie keeps running while you decide.
- After week 4 — migration complete. Oppex becomes your primary incident management platform, months before Opsgenie sunsets.
Our team moves your users, teams, services, on-call schedules and escalation policies across from Opsgenie, and connects your existing monitoring, chat and ticketing tools.
Frequently asked questions
When does Opsgenie shut down?
Atlassian has announced that Opsgenie keeps working until 5 April 2027. After that it is shut down and any data that has not been moved is deleted. Since 4 June 2025 customers can no longer change their Opsgenie edition.
Do Opsgenie customers have to move to Jira Service Management?
No. Atlassian points customers to Jira Service Management or Compass, but you can move to any incident management tool. Since you are changing tools anyway, it is a good moment to pick one built for engineering incident response rather than IT service management.
How does Oppex pricing compare with Jira Service Management?
Oppex Business is $20 per user per month billed annually and includes AI alert grouping, AI investigation, automated runbooks and status pages. At October 2026 list prices that is $4,800 a year for 20 users against $14,500 for JSM Premium, the JSM plan that includes AI alert grouping and advanced incident management.