OpsGenie support ends April 5, 2027. Atlassian announced the OpsGenie end of life in 2025: new sales stopped in June, and full end of support lands in April 2027. Most teams are treating it like a calendar item.
The teams we spoke to who already went through it say that was their first mistake.
We talked to 25 engineering teams about incident management. Three were in the middle of or had just completed an OpsGenie migration. None of them said it went as fast as expected. One described rebuilding on-call schedules from scratch because the CSV export didn't map cleanly to their new tool. Another ran both tools in parallel for 11 weeks because they found integration gaps mid-migration.
The April 2027 deadline feels distant. It isn't.
The official dates, what Atlassian decided to replace OpsGenie with, the data retention cliff most teams miss, and what to do in the next 30 days.
What You'll Learn
- The exact timeline and what the dates mean
- What Atlassian is actually offering instead (it's not one thing)
- The part most teams miss: what happens to your data
- How to decide: stay on Atlassian or go third-party
- What to do this week, not someday
The timeline
| Date | What happens |
|---|---|
| June 4, 2025 | New OpsGenie sales stopped |
| April 5, 2027 | End of support for existing customers |
Source: Atlassian's official migration page.
April 5, 2027 is the published end-of-support date. That's when the OpsGenie end of life takes effect and access to OpsGenie will be shut off.
Existing customers can still add seats until April 5, 2027, but cannot upgrade or downgrade editions after June 4, 2025.
For most teams, budget 6 to 16 weeks for the actual migration depending on how many integrations you have. The teams we spoke to who had straightforward setups still took 6 to 8 weeks. The ones with complex integrations took longer, and one team ran a second migration three months later after picking the wrong tool under time pressure.
If you're planning to start in Q1 2027, you're already in the danger zone.
What Atlassian is offering instead
Not one product. Two.
This is where a lot of teams get surprised. OpsGenie was one tool with one bill. Atlassian isn't replacing it with one thing. They're splitting it across two products and asking you to pick which half you need.
Jira Service Management (JSM) is the ITSM option. Incident workflows, change management, service portals, asset management. If your team is already deep in Jira and thinks in ITSM terms, this is Atlassian's intended path.
Compass is the engineering option. Alerting, on-call scheduling, software catalog. Less overhead than JSM, built for engineering teams who want on-call without the full ITSM stack on top of it.
Most OpsGenie teams we talked to didn't want to navigate this choice. They had one tool. They didn't want to pick between two, figure out the feature overlap, or pay for both. That's why many teams are using the shutdown as a reason to look outside Atlassian entirely, not just to find the nearest replacement.
What happens to your data
OpsGenie Enterprise had effectively unlimited alert data retention. After migrating to JSM, the limits drop sharply:
| JSM plan | Alert data retention |
|---|---|
| Free | 1 month |
| Standard | 1 year |
| Premium | 3 years |
Source: Atlassian support documentation.
If you're in a regulated environment, run compliance reports, or regularly go back to historical incident data, this is a meaningful change. Check your current OpsGenie retention usage before you commit to a JSM plan.
One of the teams we spoke to caught this only after starting their JSM trial. They had 4 years of alert history used for quarterly reviews. Standard plan wasn't going to cover it. They switched their evaluation to third-party tools instead.
What you're actually deciding
Before you shortlist tools, there's a fork you need to resolve first.
Are you staying in the Atlassian ecosystem, or leaving it?
Staying on Atlassian makes sense if:
You're already deep in Jira. Your incidents are ITSM-shaped: change requests, service portals, asset management. You don't want to introduce a vendor outside the Atlassian stack. In that case, start a JSM or Compass trial now and don't overthink it.
Leaving Atlassian makes sense if:
You want one bundled product at one price. You need more than a year of alert data retention on a reasonable plan. Your team runs primarily in Slack and JSM's interface feels like overhead. Or you were on OpsGenie specifically because it was standalone and simple, and neither JSM nor Compass is that.
The third-party options most teams land on: PagerDuty, incident.io, Runframe, Squadcast, Grafana Cloud IRM. See our full OpsGenie alternatives comparison for what each costs once you include on-call, which is often a separate line item.
A word on waiting
Waiting is the most common choice. It's also the one teams most often regret.
From the teams we spoke to: the ones who migrated cleanly started 6 months before their target cutover. The ones who started 3 to 4 months out had rushed evaluations, unexpected integration failures, and in one case, an incident during the actual cutover because they hadn't run the tools in parallel long enough.
"We thought we had plenty of time in September," one engineering manager told us. "By November we were scrambling."
Waiting is fine if you're reading this in early 2026. By Q3 2026, you're behind.
What to do this week
You don't need to pick a tool today. But do these three things first.
Audit your OpsGenie setup. List every integration, every escalation policy, every on-call schedule. Then ask: does each of these have a direct equivalent in the tools you're evaluating, or will you need to rebuild it? Teams consistently underestimate how long this takes. One team had 18 integrations. Five didn't have direct replacements in the tool they picked. Budget time to rebuild from scratch.
Export whatever Atlassian makes available now. On-call schedules, user lists, escalation policies, incident history. Don't wait until migration time. Exports don't always import cleanly into other tools. Some rebuild time is unavoidable, but you want the source data in your hands early.
Set a real cutover date. Not "sometime before April 2027." Pick a specific date at least 8 weeks before April 5, 2027 and put it on the roadmap. The teams that miss the deadline treated this as background work until they couldn't anymore.
The bottom line
OpsGenie is going away. Two questions are worth settling before you pick anything: are you staying in the Atlassian ecosystem, and what happens to your alert data retention when you get there?
Get those right and the rest is execution.
If you're still deciding where to go, our OpsGenie alternatives comparison covers what's available, what it actually costs with on-call included, and how other teams are making the call.
Ready to start the actual migration? Our OpsGenie migration guide covers the export steps, how to run the parallel period, and the realistic timeline most teams need.