Opsgenie vs. Jira Service Management vs. Compass: Where to Move Next
Atlassian’s Opsgenie migration guide now lists only Jira Service Management plans as destinations (Atlassian). Atlassian also says Compass closed to new customers on May 13, 2026, and that Compass access ends December 31, 2027 (Atlassian Community). Its Compass docs add that Compass alerting and on-call work has to move to Jira Service Management anyway (Atlassian).
Atlassian’s path for Opsgenie customers is Jira Service Management. The other option is a standalone on-call tool outside Atlassian. Plan around one date in particular: if you use Atlassian’s migration tool, Opsgenie shuts down automatically 120 days after your migration date (Atlassian).
Opsgenie, Jira Service Management, and Compass at a glance
Product | Status, per Atlassian | Where alerting and on-call go |
|---|---|---|
Opsgenie | End of sale June 4, 2025; shuts down April 5, 2027 (Atlassian) | To Jira Service Management through Atlassian’s migration tool (Atlassian) |
Jira Service Management | The only destination in Atlassian’s Opsgenie migration guide (Atlassian) | Receives Opsgenie and Compass alerting (Atlassian) |
Compass | Closed to new customers May 13, 2026; access ends December 31, 2027 (Atlassian Community) | Must move to Jira Service Management (Atlassian) |
The Opsgenie date that arrives first
Atlassian’s shutdown article says that once Opsgenie is off, users can’t log in or retrieve data, the mobile app stops, and remaining Opsgenie integrations stop working. Atlassian honors existing Opsgenie contracts for their term or until April 5, 2027, whichever comes first (Atlassian).
Teams that use Atlassian’s migration tool hit an earlier deadline. According to the same shutdown article, Opsgenie shuts down automatically 120 days after your migration date unless you turn it off sooner, and turning it off can’t be undone.
See the Opsgenie Rescue Hub.
Jira Service Management: what changes when Opsgenie moves in
According to Atlassian’s feature comparison, your Jira Service Management plan decides which Opsgenie features you keep. Atlassian’s migration guide recommends a plan from your current one: Essentials maps to Standard, Standard maps to Premium, and Enterprise maps to Premium or Enterprise.
Atlassian’s feature comparison lists these on Premium and Enterprise only:
Voice call notifications. SMS is on every plan, with limits on Free.
Alert policies and team notification policies.
Heartbeats.
Global Slack and Microsoft Teams integrations.
On-premises integrations, which move from the Opsgenie Edge Connector to the Jira Edge Connector.
Atlassian’s feature comparison page also lists items that don’t migrate. The Incident Command Center is deprecated. Opsgenie actions and incident rules become Automation rules, limited per user per month by plan. REST API calls have to move to Jira Service Management endpoints (Atlassian).
On price, Atlassian says each customer sees their quote inside Opsgenie under Settings > Plan your move, and may qualify for a limited-time promotional discount (Atlassian). Will everyone who gets paged need a paid Jira Service Management seat? Ask your Atlassian account team before you schedule a date, because the answer affects your cost.
Can Opsgenie teams still move to Compass?
Not if you’re new to Compass. Atlassian says Compass has been closed to new customers since May 13, 2026, and that access ends December 31, 2027 (Atlassian Community). Its catalog and scorecards are moving to Atlassian’s DX product (Atlassian).
DX doesn’t include alerting: Atlassian’s Compass to DX guide says all alerts and operations work must migrate to Jira Service Management. Atlassian’s Compass to Jira Service Management guide says that migration has to start before your Compass contract ends or December 31, 2027, whichever comes first, and that Forge integrations set up in Compass don’t sync.
Leaving Atlassian for on-call
If Opsgenie only paged people, both Atlassian paths keep on-call inside an IT service management product. A standalone on-call tool is the other route. We make JAMS Incident Management, which works fully standalone without JAMS Scheduler. Here’s how it handles the points above:
Voice calls start on Starter, which is $6 per user per month billed annually for up to 25 users. That’s $150 a month for a 25-person team. Starter includes 50 SMS or WhatsApp messages and 10 voice calls per user per month, pooled across the team, plus escalation policies.
Alerts go out by voice, SMS, WhatsApp, push, email, Microsoft Teams, or Slack until someone acknowledges. Voice and SMS use US, UK, and Australian numbers, with other regions on request.
The Opsgenie migration check is live and read-only. Run it, send the report to JAMS Software, and the team moves your schedules for you. The Opsgenie migration guide walks through it.
If you run Opsgenie for clients as an MSP, check how child accounts migrate. Atlassian’s feature comparison says the MSP setup is deprecated and that child accounts become free accounts after migration (Atlassian). JAMS Incident Management partner accounts give each client a separate tenant with its own schedules, escalation policies, and alert history. Clients never see each other.
Want to hear an alert before you sign up? Anyone can trigger a sample alert call from incident.jamssoftware.com without an account.
JAMS Software moved its own support team’s on-call off PagerDuty in under an hour, end to end. The PagerDuty migration case study shows how. See the JAMS Incident Management page for plan details.
Which one to pick
Choose Jira Service Management if your service desk already runs there, or you need change and problem management next to on-call (Atlassian). Price Premium before you schedule, because Atlassian puts voice calls on Premium and Enterprise (Atlassian). Pick a migration date that keeps the 120-day window inside your current contract.
Skip Compass for an Opsgenie move. Atlassian has published its end date (Atlassian).
Choose a standalone on-call tool if Opsgenie only ever paged people. Your alerting stays separate from your ticketing system.
FAQ
When does Opsgenie shut down?
Atlassian’s end of support date is April 5, 2027, when access is shut off and unmigrated data is deleted (Atlassian). Teams using Atlassian’s migration tool lose Opsgenie sooner: it shuts down automatically 120 days after the migration date unless an admin turns it off first (Atlassian).
Can I still migrate Opsgenie to Compass?
Atlassian’s Opsgenie migration guide lists only Jira Service Management plans as destinations (Atlassian). Atlassian also says Compass has been closed to new customers since May 13, 2026, and that access ends December 31, 2027 (Atlassian Community). Compass alerting has to move to Jira Service Management before then.
Does Jira Service Management include voice call alerts?
Only on Premium and Enterprise, according to Atlassian’s feature comparison. SMS is on every plan, with limits on Free. If your Opsgenie setup relies on phone calls to wake someone up, check which plan Atlassian recommends for you under Settings > Plan your move before you schedule a date.
What happens to Opsgenie data that isn’t migrated?
Atlassian says any Opsgenie data that hasn’t been moved is deleted when Opsgenie shuts down on April 5, 2027 (Atlassian). After a migration, only migrated data is available in Jira Service Management (Atlassian). Export schedules, escalation policies, and integration settings you want to keep before your shutdown date.
