Cross-posted from the Fluidify blog.
Atlassian is shutting Opsgenie down. Sales already stopped in June 2025, and the Opsgenie end of life lands on April 5, 2027, when the product goes dark and any data that hasn't been moved is deleted. This is the short version: the dates, what each one changes for a team that still runs Opsgenie today, and what to decide before the window closes.
Key takeaways
- Opsgenie end of sale was June 4, 2025. The Opsgenie shutdown (end of support) is April 5, 2027, and Atlassian says unmoved data is deleted on that date.
- Until then, existing customers keep their contract for its term or until the shutdown date, whichever comes first, and can still buy extra seats. Edition upgrades, downgrades, and new sites stopped at end of sale.
- Atlassian's automated move gives 120 days of parallel Opsgenie access after your migration date. Atlassian doesn't say how that window meets the shutdown, but it can't outlast a product that's gone. By our count, a move scheduled after December 6, 2026 gets less than the full 120 days, and the later the move, the shorter the overlap.
The Opsgenie shutdown timeline
June 4, 2025, end of sale: Opsgenie stopped being sold to new customers, directly or through partners. From the same date, existing customers can no longer upgrade or downgrade their edition or add sites, per Atlassian's Opsgenie migration page.
Today through April 4, 2027, the run-off period: Opsgenie keeps working. Atlassian honors existing contracts for their term or until the end of support date, whichever comes first, and you can still buy additional Opsgenie seats. In practice that means a team that grows can add people, but it can't change plans to get a feature it doesn't already have.
April 5, 2027, end of support and shutdown: Atlassian's FAQ says Opsgenie will be shut down and no longer accessible, and that customer data in Opsgenie that hasn't been moved will be deleted. That's the real deadline. Every other date in this post is about how much room you leave yourself before it.
What the Opsgenie end of life means if you still run it
The shutdown isn't only an account closing. Opsgenie is usually wired into a lot of other systems, and each of those connections has to go somewhere:
- Every alert source needs a new destination: monitoring tools, cloud alarms, CI pipelines, and custom scripts that send alerts to Opsgenie's API or email integrations will stop paging anyone after April 5, 2027 unless they're pointed at a new tool first.
- On-call schedules and escalation policies have to be recreated or migrated: they encode who gets woken up, in what order, and after how long. If they don't exist in the new tool before cutover, nobody gets paged.
- Scripts and infrastructure-as-code that call Opsgenie's API break: anything using an Opsgenie API key, the Opsgenie Terraform provider, or webhook payloads shaped for Opsgenie needs to be rewritten for the destination tool.
- History disappears unless you export it: alert and incident history matters for compliance, postmortems, and on-call reporting. Atlassian's page says you can still download your Opsgenie data, but treat "export before the deadline" as the safe plan, not something to test after the shutdown.
Your two options before April 5, 2027
Move into Jira Service Management: this is Atlassian's path. Opsgenie's alerting and on-call features now live in Jira Service Management (JSM), and Atlassian runs an automated move that syncs your Opsgenie data on a date you choose, with a 14-day migration demo beforehand and 120 days of parallel access afterward. An Opsgenie owner who is also a site admin starts the move. If you move before your Opsgenie subscription ends and have more than 30 days left, Atlassian extends your destination subscription for the remaining time. Pricing for your recommended JSM plan shows up in Opsgenie under Settings > Plan your move, and Atlassian mentions a limited-time promotional discount to soften the price difference.
Move to a different on-call tool: if your team doesn't want alerting and on-call bundled into a service desk product, wants to get off per-user pricing, or needs a self-hosted option, the shutdown is a forced decision point either way, so it's a reasonable moment to evaluate alternatives. We compare nine of them in our Opsgenie alternatives guide, including what each one costs and how much of your Opsgenie setup it can import.
Whichever way you go, the work is the same shape: inventory what you have, move schedules and escalation policies, redirect alert sources, run old and new in parallel, then cut over. Our Opsgenie migration guide and checklist walks through that step by step for either destination.
The 120-day parallel access window has a hard edge
Atlassian's automated move includes 120 days of parallel Opsgenie access after your scheduled migration, so you can check that alerts, schedules, and escalations behave the same way in JSM before Opsgenie goes away. Atlassian's page doesn't spell out what happens to that window close to the shutdown, but parallel access to Opsgenie can't continue once Opsgenie itself is switched off. Counting back 120 days from April 5, 2027 lands on December 6, 2026. That date is our own arithmetic, not an Atlassian deadline, and the point it makes holds whenever you read this: a migration scheduled after December 6, 2026 can only overlap until April 5, so every week of delay is a week less of overlap.
If that date has already passed by the time you're reading this, any move you schedule from now on gets less than the full 120 days. Ask Atlassian to confirm the exact parallel-access end date when you book the move, and plan your validation around that date rather than the headline 120 days.
The same logic applies if you're moving to a non-Atlassian tool. Your parallel run, where both systems receive the same alerts, needs to cover at least one full on-call rotation and ideally a couple of real incidents. Working backward from the shutdown, that run needs to start well before the end of Q1 2027.
What to do this month
- Decide the destination: JSM or a different tool. Everything else waits on this.
- Inventory Opsgenie: list every team, schedule, escalation policy, integration, API key, and heartbeat. Note which ones are actually still in use.
- Export what you need to keep: schedules, alert and incident history, and anything you'd need for an audit. Our guide to exporting Opsgenie schedules covers the calendar and API options.
- Pick a migration date with room behind it: if you're going the JSM route, a move scheduled before December 6, 2026 gets the full 120-day overlap by our count. After that, every week you wait takes a week off the overlap, so book the earliest date you can.
- Book the cutover and the decommission: write down the date each alert source switches, and the date you'll stop paying for Opsgenie.
FAQ
When does Opsgenie shut down? Opsgenie's end of support is April 5, 2027. Atlassian says the product will no longer be accessible after that date and that customer data that hasn't been moved will be deleted.
Can I still buy Opsgenie? No, not as a new customer. Opsgenie end of sale was June 4, 2025. Existing customers can still buy additional seats until April 5, 2027, but can't change editions or add sites.
Will my Opsgenie contract renew? Atlassian honors your existing contract for its term or until the end of support date, whichever comes first. Nothing runs past April 5, 2027.
Is Opsgenie being replaced by Jira Service Management? Atlassian has moved Opsgenie's alerting and on-call features into Jira Service Management and built an automated migration path into it. Some Atlassian pages also mention Compass. You're not required to stay with Atlassian, though, and any on-call tool that can receive your alerts is a valid destination.
What happens to my data after the Opsgenie shutdown? Atlassian says any customer data in Opsgenie that has not been moved will be deleted on April 5, 2027. Export schedules, alert history, and anything you need for compliance before then.
How long does an Opsgenie migration take? It depends on how many integrations, teams, and custom routing rules you have. Planning for several weeks including a parallel run is realistic for most teams. The step-by-step version is in our migration checklist.
If you're looking beyond JSM
We build FluidifyAI Regen, an on-call and incident tool that can import Opsgenie schedules and escalation policies through Opsgenie's API, at a flat $100 a month with no per-seat pricing. We've written a full Opsgenie-to-Regen walkthrough if that's the direction you're leaning. Either way, the important thing this month is picking a date.
Top comments (0)