Editor’s Note (June 2026): This blog was published in June 2025, shortly before the Opsgenie end-of-sale date. Since then, several developments have changed the migration picture. Opsgenie is no longer available for new purchases or trials as of June 4, 2025, and teams with Jira Service Management (JSM)-bundled Opsgenie lost access in October 2025. At Atlassian Team ‘26 in May 2026, Atlassian announced the Incident Command Center, an AI-native response hub within Jira Service Management that uses Rovo AI to investigate root causes and recommend resolution steps. This addition significantly bolsters Jira Service Management (JSM) as the migration destination. JSM is also now part of Atlassian’s Service Collection alongside Customer Service Management, Assets, and Rovo agents. With less than 10 months remaining before Opsgenie’s end of support on April 5, 2027, all unmigrated data will be deleted. ServiceRocket is refreshing this article to cover the latest JSM capabilities, Atlassian’s automated migration tooling, and updated guidance on choosing between JSM and Compass.
Atlassian has announced that Opsgenie will no longer be available for new purchases or trials starting June 4, 2025, with end of support (EOS) on April 5, 2027. This change affects organizations that rely on Opsgenie for alerting, on-call scheduling, and incident response.
To help teams navigate this transition, Atlassian has introduced automated tooling and detailed guidance for migrating to Jira Service Management (JSM) or Compass, depending on your needs.
Atlassian is consolidating incident management features into Jira Service Management, creating a unified platform for ITSM, change management, alerting, and on-call coordination.
For engineering teams focused on software health and reliability, Compass may be a better fit, offering a developer-first approach to service ownership and team accountability.
Choosing the right destination depends on how your team uses Opsgenie today.
Jira Service Management is ideal for teams looking for a full ITSM solution, with integrated incident, change, and problem management.
Compass is recommended for engineering organizations managing distributed systems or microservices. If you’re exploring Compass, you may also want to see how teams are extending it using Forge to fit custom workflows and tooling needs.
While Jira Service Management and Compass both provide paths forward, they support very different use cases. Here’s how key Opsgenie features stack up across all three tools:
Use this comparison to assess not only what you need now, but what you’ll need next. If your team’s priority is end-to-end incident response, Jira Service Management may be the better fit. If you’re looking to build ownership and visibility across a distributed architecture, Compass could be the way forward.
At ServiceRocket, we help teams manage migrations and set the foundation for long-term success.
We’ll assess your Opsgenie usage and recommend a migration path aligned with your operational model — whether that’s Jira Service Management or Compass.
Our experts walk you through Atlassian’s tooling to ensure alerts, schedules, and integrations are transferred accurately and with minimal disruption.
There may be time-sensitive incentives for teams migrating early to Jira Service Management. We’ll help you understand what’s available and how to plan accordingly.
Beyond migration, we help you build a Center of Excellence tailored to your organization’s goals. Whether your focus is scaling ITSM, tightening governance, or driving engineering efficiency, we align Atlassian tools to your long-term objectives.
Your Opsgenie setup is unique. Let’s work together to evaluate your current use, guide your migration, and build toward a scalable future.
Additional Resources
Looking for more context or technical guidance?
