Migrations
Opsgenie end of support: the 2027 deadline and how to plan your move
Migrations · Updated 2026-10-19 · 9 min read · By the CallHeim team
Atlassian stopped selling Opsgenie on 4 June 2025. Opsgenie reaches end of support on 5 April 2027: access is shut off and customer data that has not been moved is deleted, so move or export what you need before then. Atlassian’s Opsgenie licensing page, checked 2026-10-19. The real question for an on-call team is not whether to leave, but when to start and where to go. If you want the wider comparison first, see our Opsgenie alternatives guide; this page is the dated timeline and the planning checklist.
What “end of support” actually means
Atlassian announced the change on 4 March 2025 and closed new Opsgenie sales on 4 June 2025: since that date nobody can sign up for Opsgenie, and existing customers cannot change plans. (Atlassian’s Opsgenie licensing page, checked 2026-10-19)
If your team already has an Opsgenie subscription, it keeps working until the end-of-support date, and you can still add seats. Renewals are allowed only if the term ends before 5 April 2027. Nobody new can start an Opsgenie subscription. (Atlassian’s Opsgenie licensing page, checked 2026-10-19)
Why the deadline is easy to underestimate
Nothing about Opsgenie changes for most users today. Alerts still fire, schedules still rotate, escalation policies still page the right person. Opsgenie keeps working until support ends, so nothing forces the move; set your own date.
An on-call configuration is also not just data. It is the accumulated shape of how a team actually responds to incidents: who covers what, which alerts route where, which escalation tiers exist because of a specific past outage. Rebuilding that from scratch under deadline pressure, in the same week you are also trying to keep the lights on, is a worse position than starting the move while there is no pressure at all.
A timeline: work backward from 5 April 2027
Working backward from the end-of-support date, rather than forward from “whenever we get to it,” is what keeps a migration from turning into a scramble. As of October 2026 there are under six months left, so a reasonable plan looks like this:
| Suggested timing | What to get done |
|---|---|
| October 2026 | Inventory everything you actually rely on in Opsgenie and shortlist destination platforms. |
| By December 2026 | Pick a destination and start a parallel run: forward alerts to it alongside Opsgenie. |
| By January 2027 | Import configuration and incident history; test escalation and paging end to end on the new platform. |
| By February 2027 | Make the new platform primary. Keep Opsgenie live only as a fallback while you confirm nothing was missed. |
| By March 2027 | Remove Opsgenie access, with margin before 5 April 2027, not on the deadline itself. |
What happens to your data
Until the end-of-support date, nothing about your Opsgenie data changes on its own. Decide now what you want to keep: users, teams, schedules, escalation policies, integrations, maintenance windows and incident history. Export or move what you need before 5 April 2027. If your own migration is not done by then, the record of who was on call for what, and why, goes with the product.
Where Atlassian points you: Jira Service Management
Atlassian’s licensing and migration pages name Jira Service Management (JSM) as Opsgenie’s successor. (Atlassian’s Opsgenie migration page, checked 2026-10-19)
Atlassian’s documented migration path is an automated tool (under Settings > Plan your move) that runs without downtime, a 120-day window of parallel access to both products, and a 14-day migration trial so you can see the result before committing. Alerting and on-call ship in every JSM plan; AI-assisted grouping and automation are reserved for the Premium and Enterprise tiers. (Atlassian’s Opsgenie migration page, checked 2026-10-19)
Not everything carries over unchanged. Atlassian’s own deprecation notes list Incident Command Center, Edge Encryption, MSP sub-accounts, Heartbeats V1 and Policies V1 as items that do not map directly to JSM; Opsgenie groups become JSM teams on the way across. (Atlassian’s Opsgenie deprecations documentation, checked 2026-10-19) Jira Service Management is priced per agent; see Atlassian’s pricing page before you budget against it.
Weighing your options
JSM is the path Atlassian built for you, and it is a reasonable default if your team already lives in the Atlassian suite. It is not the only option, and treating it as the only option skips a decision worth making deliberately. Whatever you evaluate, the same questions apply:
- Migration effort. Does the destination have a real import path for your schedules, escalation policies and integrations, or are you rebuilding them yourself?
- Integration coverage. Do the monitoring tools that currently page through Opsgenie have a supported path into the new platform?
- Pricing model. Per-agent, per-user, or usage-based — and what is actually included at the tier you would buy, versus sold as an add-on?
- Paging channels. Which channels are proven for your team’s real usage, not just listed as supported?
- Where it fits your stack. Staying inside a suite you already use (JSM inside Atlassian) trades a smaller number of new tools to learn against a dedicated on-call product that may fit your incident workflow more directly.
If you want the fuller comparison across every named option — PagerDuty, Jira Service Management and CallHeim, with sourced facts on each — our Opsgenie alternatives guide covers all three side by side. For dedicated on-call and incident response platforms beyond that set, our guide to PagerDuty alternatives covers the same evaluation criteria against a wider set of named vendors.
Cost is also worth pricing out explicitly rather than assumed. A per-agent JSM price and a per-user price on a dedicated on-call platform are not directly comparable line items until you know exactly which roles at your organization actually need a paid seat — escalation targets and incident responders, typically, rather than every engineer who might occasionally look at a dashboard. Get an actual quote for your team size on each option before treating either as the cheaper choice.
A migration checklist
- List every object type you actually use in Opsgenie: users, teams, schedules, escalation policies, integrations, notification preferences, incident history and maintenance windows.
- Confirm which of those your destination platform actually imports, and which you will need to rebuild yourself rather than assume will “just come across.”
- Run a parallel-forwarding period before cutting over, so gaps in coverage show up while Opsgenie is still the safety net underneath.
- Test the full paging path on the new platform — not just that the configuration exists, but that a real alert reaches a real person.
- Set your own internal cutover date well ahead of 5 April 2027, so a stalled migration does not collide with the actual end of support.
- Tell the whole team the old tool is going away before it goes away, not after.
How CallHeim handles this
The importer reads your PagerDuty or Opsgenie configuration from a US or EU account, and a dry run shows you the result before anything is written to your organization.
Run in parallel during a move: CallHeim receives PagerDuty Events API v1 and v2 requests and Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast (now SolarWinds Incident Response), Zenduty (now Xurrent IMR) and Grafana OnCall. Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused.
Incident history import covers the last 90 days, and imported incidents never page anyone. Re-running an import fills in what is missing and never overwrites changes you made in CallHeim.
See CallHeim compared with Opsgenie, the Opsgenie migration path, the Opsgenie integration setup notes, or the fuller Opsgenie alternatives guide for how CallHeim stacks up against PagerDuty and Jira Service Management too.
Key takeaways
- Opsgenie reaches end of support on 5 April 2027; plan the move now.
- Existing subscriptions keep working until then and can still add seats — nobody new can start one.
- Atlassian’s documented path is an automated migration tool into Jira Service Management, with a 120-day parallel-access window and a 14-day trial.
- A handful of Opsgenie features (Incident Command Center, Edge Encryption, MSP sub-accounts, older heartbeat and policy versions) do not carry over unchanged.
- Work backward from the deadline: inventory now, start a parallel run by December 2026, and leave margin before 5 April 2027 rather than aiming at it directly.
Questions
Common questions, answered.
When exactly does Opsgenie shut down?
Opsgenie reaches end of support on 5 April 2027 (Atlassian). Atlassian stopped selling it on 4 June 2025.
Can I still renew or add seats to my existing Opsgenie plan?
You can add seats until 5 April 2027, and renewals are allowed if the term ends before that date. New customers cannot buy Opsgenie.
What happens to our data if we do not migrate in time?
Access is shut off on 5 April 2027 and customer data that has not been moved is deleted, so move or export what you need before then.
Do we have to move to Jira Service Management?
No. It is Atlassian’s named successor, and PagerDuty, CallHeim and other on-call platforms are also options.
How far in advance should we start planning?
Start now. With under six months left as of October 2026, aim to finish the cutover by March 2027, with margin before 5 April 2027.
Will an import carry over our whole Opsgenie configuration?
CallHeim’s importer reads users, teams, services, schedules, escalation policies, 90 days of incident history and maintenance windows, and a dry run lets you review the result before anything is created. Test the full paging path after any import.
Try it
See this in your own on-call rotation.
14-day trial for up to 5 seats, no card required.