Opsgenie reaches end of support on 5 April 2027. On that date access is switched off and any Opsgenie data that has not been moved is deleted. Alerting, on-call and incident response now live in Jira Service Management and Compass, and the move is largely automated. The real work is planning it calmly, not racing in March.
The dates that matter
4 June 2025
End of sale
No new Opsgenie customers. Existing ones can still add seats.
Now
Plan and test
Pick a target, run a demo migration, train responders.
5 April 2027
End of support
Access shuts off. Data not moved is deleted.
Renewals are still possible, but only for terms that end before 5 April 2027.
Jira Service Management or Compass?
For IT and service teams
Jira Service Management
- Alerting and on-call, plus full incident, change and problem management
- Part of Service Collection, with Rovo agents and Assets
- Best fit when service desks and operations share one process
For developer teams
Compass
- Alerting and on-call in a developer portal
- Organised around components and their owners
- Best fit when engineers run their own services
Why JSM is a strong landing spot now
At Team '26 Europe, Atlassian added more reasons to consolidate incident work in Jira Service Management:
- Workforce Management (GA). Schedules, real-time availability, capacity and skill-based routing in one place.
- AI Change Risk Assessment (GA). Risk scores for every change, with one-click mitigations.
- Solution Composer (open beta). Describe a service desk in plain language and Rovo sets it up.
Your migration checklist
- Inventory what you use. Alerts, schedules, escalations, integrations, heartbeats and API scripts.
- Choose your target. Jira Service Management, Compass, or both for different teams.
- Check your hosting. On JSM Data Center, move JSM to Cloud first, then move Opsgenie.
- Run a demo migration. Use the in-app tool under Settings, Migrate Opsgenie, on a test account first.
- Rebuild the edges. Re-point integrations and custom API calls, then test real alerts end to end.
- Train responders. Walk on-call teams through the new views before the switch.
In questions
When does Opsgenie end of support happen?
Opsgenie end of support is on 5 April 2027. On that date access to Opsgenie is shut off, the product is no longer available, and any customer data that has not been migrated is deleted. New sales already ended on 4 June 2025, and renewals must end before April 2027.
Where do Opsgenie features go?
Opsgenie's alerting and on-call features are available in Jira Service Management and Compass. Jira Service Management adds end-to-end incident, change and problem management, so it suits IT and service teams. Compass focuses on alerting and on-call for developer teams organised around components.
How hard is the Opsgenie migration?
For most customers the move is largely automated through Atlassian's in-app migration tool, found in Opsgenie under Settings, Migrate Opsgenie. The effort sits around it: mapping integrations and API scripts, testing alerts end to end and training on-call teams on the new experience.
What if we run Jira Service Management Data Center?
Opsgenie moves into Jira Service Management Cloud. Data Center customers first move Jira Service Management to Cloud, then move Opsgenie. Alternatively, Opsgenie can be moved to a new Jira Service Management Cloud site. Either path needs to be complete before 5 April 2027.
When should we start the migration?
Start planning now. Leave time for a demo migration, integration rework, testing with real alerts and responder training. Finishing well before April 2027 keeps on-call coverage continuous and avoids a rushed cutover during the busiest weeks before the deadline.
Move off Opsgenie with no gap in on-call
ONETEEM runs Atlassian Cloud migrations and Jira Service Management setups. We help you choose the right target, migrate schedules and integrations, and get responders ready before April 2027.
Sources: Opsgenie migration, Atlassian, Opsgenie end of support, Atlassian, Service Collection at Team '26 Europe.
