TL;DR
Atlassian ended OpsGenie sales on June 4, 2025 and shuts the product down on April 5, 2027. Its recommended route is an OpsGenie to JSM migration. Atlassian’s tool moves most of your setup and keeps OpsGenie open for 120 days after the move. Chat tools, actions and incident rules still need a manual rebuild. JSM is an ITSM ticketing platform first, with incident management built into it. Voice alerts and advanced escalation come with Standard. Heartbeats, post-incident reviews and custom roles need Premium. JSM is probably the right home if your team already runs on Atlassian or needs a service desk. If you want standalone incident management software like OpsGenie, Spike is the better move. It starts at $7 per user per month, and OpsGenie teams get 20% off the first year on an annual plan. Our guide to OpsGenie alternatives for startups compares Spike with five other options, and our enterprise guide covers seven tools for larger organisations.
Atlassian retires OpsGenie on April 5, 2027, and Jira Service Management (JSM) is its official replacement. This guide explains how the OpsGenie to JSM migration works, what carries over and what changes for your on-call team. It also breaks down JSM pricing after OpsGenie and the trade-offs of running incidents inside an ITSM platform. If you’d rather stay on a standalone incident management tool like OpsGenie, we compare JSM with Spike as well. Spike is our product, so we’ll be clear about where JSM is the stronger choice.
Key dates for the OpsGenie to JSM migration
Four dates set the timeline for an OpsGenie to JSM migration. Atlassian lists them on its migration page.
- June 4, 2025: End of sale. Existing customers can still add seats, but editions and sites are frozen.
- Your migration date: You choose it when you schedule the move in OpsGenie.
- 120 days after your migration: OpsGenie turns off for your site. A site admin can turn it off earlier.
- April 5, 2027: End of support. OpsGenie shuts down for every customer, and any data you haven’t moved is deleted.
What is JSM, and why is Atlassian moving OpsGenie into it?
Jira Service Management (JSM) is Atlassian’s IT service management (ITSM) platform. IT and support teams use it to run service desks, handle requests and approve changes. Incident management is one part of it. After the migration, OpsGenie’s alerting and on-call features live inside JSM under Operations. Our guide to JSM explains the full product.
Atlassian is retiring OpsGenie to bring alerting and service management into one product. Its support guide says the move lets your team handle “every alert and incident in one tool”. In practice, that tool is the same one your service desk and Jira tickets run in.
OpsGenie was built only for alerts, on-call and incident response. JSM is a ticketing platform that also handles incidents. If you already run a service desk in JSM, alerts in the same place mean one less tool to manage. If you don’t, you’d be adopting a full ITSM platform to replace an on-call tool. Our JSM review covers what works on each plan for on-call and alerting.
How to migrate from OpsGenie to JSM, step by step
Atlassian’s migration tool copies most of your OpsGenie setup into JSM. You handle the checks and approvals before your migration date and a few manual rebuilds after it.
Before you start
- Open Settings and then Plan your move in OpsGenie to check that your site is eligible. If OpsGenie is already merged into your JSM subscription, the page sits under Settings, Products and Moving from Opsgenie in JSM. Global escalations or global schedules can delay eligibility.
- Start a JSM trial from inside OpsGenie and test your busiest schedule in it.
- Choose your JSM plan. The cost section below shows which plan fits which OpsGenie setup.
- List what you’ll rebuild by hand: chat tools, actions and incident rules, custom roles, scripts that call the OpsGenie API and heartbeat scripts.
- If you use a phone number from OpsGenie, port it to your own Twilio account. Atlassian suggests doing this before the migration starts.
- Decide who will help. Atlassian support doesn’t do hands-on migrations and points customers to its Solution Partners.
- Line up approvals. An OpsGenie owner who is also a site admin starts the move, and a billing admin approves the new price.
- Schedule your migration date.
Atlassian calls the move “largely automated” with no downtime. It’s also permanent. There’s no rollback, so the JSM trial and the 120 days are your safety net.
What happens after you start the move
On your migration date, Atlassian copies your OpsGenie data and settings into JSM. Nothing in OpsGenie is erased during the copy. The OpsGenie API keeps working during the move. Atlassian recommends the JSM Operations REST API once the move is complete.
What happens when OpsGenie becomes read-only
Alerts and on-call schedules in OpsGenie then turn read-only. Nobody can edit them there, not even admins. Every change happens in JSM from this point, though new alerts still show up in OpsGenie for reference. This is the time to finish the rebuilds in the next section.
What happens when OpsGenie turns off
OpsGenie switches off by itself 120 days after your migration date. A site admin can turn it off sooner from the migration guide in JSM, under Complete Opsgenie migration. Atlassian says this step can’t be undone. Once it’s off, the OpsGenie web and mobile apps stop working for everyone. Anything that never moved is deleted, including chat connections and OpsGenie actions. All alerts and on-call notifications then come from JSM.
What carries over to JSM, what you rebuild, and what to watch for
Atlassian’s migration tool carries over most of your OpsGenie setup, including users, schedules, escalation policies and alerts. Chat tools, actions and incident rules need a manual rebuild in JSM. A few parts that do carry over still have catches, such as schedule editing rights and heartbeat addresses.
| Part of your setup | Carries over automatically? | What’s left for you |
|---|---|---|
| Users and roles | Yes, with most roles | Assign the product admin role where it’s missing |
| Schedules, escalation policies and alert history | Yes | Export any history your JSM plan won’t keep |
| Contact methods and notification rules | Yes | Ask each person to check their own |
| Chat tools | No | Reconnect Slack and Microsoft Teams in JSM |
| Actions and incident rules | No | Rebuild them in Jira Automation |
| Heartbeats | Yes, if assigned to a team | Point scripts to the new address |
| API and scripts | No | Move scripts to the JSM Operations REST API |
| Integrations | Most of them | Use current versions for new setups |
| Incoming call routing | No | Port your number to your own Twilio account |
| Incidents and post-incident reviews | Yes | Rebuild incident templates and move new incidents by hand |
| Mobile app | No | Install the Jira Cloud app |
Users and roles
Every OpsGenie user syncs to JSM, along with most roles. Atlassian notes that some OpsGenie admins won’t get the product admin role, so you’ll need to assign it after the migration. Users with a custom role that JSM doesn’t support get the basic User role instead.
The catch is schedule editing. In JSM Operations, team admins edit schedules while regular users can only view them. JSM’s own custom roles with narrower rights sit on Premium and Enterprise. A Reddit thread from 2024 describes the problem. A team needed people who could edit on-call schedules and nothing else. They couldn’t find a JSM role for it, and one reply said they would “need to grant admin rights” instead. It can be useful to check during the JSM trial that your schedule editors can still do their job.
Schedules, escalation policies and alert history
Schedules, rotations, escalation policies and alerts carry over automatically. How far back your alert history goes depends on your JSM plan. An export through the OpsGenie API gives you your own copy that doesn’t depend on your plan. Our export guide lists the API calls.
Contact methods and notification rules
Contact methods, notification rules and forwarding rules move with each user. One Reddit user who moved in one of Atlassian’s earlier migration waves said admins could no longer see these settings afterwards. That included whether someone had a phone number set or the mobile app installed. Consider asking everyone to check their own contact methods in the first week.
Chat tools
Slack and Microsoft Teams connections don’t carry over because they need fresh authentication. JSM’s migration guide walks you through reconnecting them. Alerts then reach your chat through JSM’s ChatOps integration.
Actions and incident rules
OpsGenie actions and incident rules don’t carry over. The replacement is Jira Automation, which has templates for common flows. Automation usage is measured in steps, with 3,000 steps per user each month on Standard and 6,500 on Premium. Each trigger, condition or action that runs counts as one step.
Heartbeats
Heartbeats carry over, but their address changes from opsgenie.net to atlassian.net. Any script that pings the old address needs updating. JSM doesn’t support heartbeats without a team, so those are dropped. One user on the Atlassian Community forum also found that a heartbeat ping now needs an API token with write access.
API and scripts
Scripts that call the OpsGenie API need new endpoints in JSM. An Atlassian support engineer explained on the forum that the integration endpoint api.atlassian.com/jsm/ops/integration/v2/alerts keeps existing OpsGenie integrations running. For new work, the documented JSM Operations endpoints are the safer bet. A few calls have no direct match. One user on the Atlassian Community forum needed help from other users to find the call for a person’s voice and SMS contacts. That call also returns one person at a time.
Integrations
Most integrations carry over automatically. About 24 outdated integration versions can’t be added as new integrations in JSM. Existing ones that use those versions still move, and you can view and edit them in JSM.
Email integrations keep their opsgenie.net address for now. Scot from the OpsGenie support team confirmed on the forum that these addresses keep working until April 2027, even after you turn off OpsGenie. New email integrations you create in JSM get a JSM address. Moving your alert sources over well before 2027 saves a rush near the deadline.
Incoming call routing
Incoming call routing now sits under Operations and General configuration in JSM. A phone number that came with OpsGenie doesn’t move to JSM on its own. Atlassian asks you to port it to your own Twilio account before OpsGenie turns off, or you may lose the number. The transfer goes through Atlassian Support and Twilio, and Twilio’s checks can take days or weeks. Once it’s in your Twilio account, you set it up in JSM’s Incoming Call Routing settings.
Incidents and post-incident reviews
Existing incidents, linked alerts and post-incident reviews carry over into a JSM project called Opsgenie Migrated Incidents. Responder roles, stakeholder filters and incident templates don’t carry over. Incidents created in OpsGenie after the migration don’t sync automatically and need a one-time manual transfer.
Mobile app
The Jira Cloud mobile app replaces the OpsGenie app. Everyone on call needs it installed and signed in before OpsGenie turns off.
What isn’t available in JSM
A few OpsGenie features have no home in JSM. Atlassian names some integrations and some global features without listing them all. The OpsGenie Teams API is also gone, and a new API replaces it. Nine OpsGenie reports don’t carry over, and neither does their historical data. They include the Postmortem Report, Service Health Report, DevOps Metric and the API usage reports.
If you can’t or don’t want to move to JSM Cloud
The migration tool moves you to JSM Cloud only. If you run JSM Data Center, Atlassian offers two paths. You can move JSM Data Center to Cloud and then move OpsGenie, or move OpsGenie to a new JSM Cloud site. If you decide not to move at all, you can download your OpsGenie data directly.
OpsGenie vs JSM: what changes for your on-call team
The table compares OpsGenie Standard with today’s JSM plans. The OpsGenie column comes from Atlassian’s own comparison of the two products. The JSM columns come from the current pricing page, which we read on October 25, 2026.
| Comparison criteria | OpsGenie Standard | JSM Standard | JSM Premium |
|---|---|---|---|
| Phone (voice) and SMS alerts | Unlimited | Unlimited SMS and voice | Unlimited SMS and voice |
| Escalation and routing | Advanced escalation rules | Advanced escalation and routing | Advanced escalation and routing |
| Incoming call routing | 1 number included | Included | Included |
| Heartbeat monitoring | Included | Not included | Included |
| Post-incident reviews | Unlimited | Not included | Included |
| Custom roles | Included | Not included | Included |
| Alert data retention | 1 year | 1 year | 3 years |
| Status pages | Sold separately as Statuspage | Not included | Not included (Enterprise only) |
| Single sign-on | Included | Needs Atlassian Guard | Needs Atlassian Guard |
| Support | 9/5 regional | 24/7 for critical issues |
Note: Atlassian’s comparison of OpsGenie dates from March 2025. Atlassian updates JSM plans often, so it’s worth checking the pricing page before you choose.
JSM isn’t a step down everywhere, and some of its strengths don’t fit in a table. Premium adds AI alert grouping, AI incident creation and draft post-incident reviews. It also brings advanced problem management and change approval workflows, which OpsGenie never offered. If your team already works in Jira, alerts and incidents sit right next to the tickets and changes they relate to.
How much will JSM cost after you leave OpsGenie?
JSM prices by agent. Atlassian’s migration page doesn’t publish a price for your migration. It points you to Plan your move in OpsGenie and mentions a possible limited-time discount. Here’s what the public pricing page shows for a 10-person on-call team on monthly billing.
| JSM plan | Price per agent per month | Monthly cost for 10 agents |
|---|---|---|
| Free | $0 for up to 3 agents | Not available for 10 agents |
| Standard | $26.90 | $269 |
| Premium | $61.60 | $616 |
| Enterprise | Annual billing only | Price from Atlassian sales |
Note: We read these prices on October 25, 2026 at 10 agents. The per-agent price drops as the team grows.
The plan you need depends on what you used in OpsGenie:
- Alerts, schedules, escalations and phone alerts: JSM Standard covers these.
- Heartbeats, post-incident reviews or custom roles: These need Premium.
- Status pages, built-in single sign-on or 5 years of alert history: These need Enterprise. On lower plans, status pages and SSO mean a separate Statuspage or Atlassian Guard subscription.
Licences are the cost that’s easiest to miss. Everyone on call becomes a JSM agent, so each of them needs a paid seat. The Reddit user mentioned under contact methods said they ended up paying for both a Jira Software seat and a JSM agent seat for the same people.
Atlassian honours your OpsGenie contract for its full term, though nothing runs past April 5, 2027. If you migrate before your OpsGenie term ends and don’t have JSM on the same site, Atlassian extends your JSM subscription by the time left on OpsGenie. That extension only applies with more than 30 days left. If JSM is already on your site, support or your account manager can tell you whether a refund applies. Our JSM pricing breakdown goes deeper on each plan.
What OpsGenie users say about moving to JSM
These voices come from earlier migration waves and from users still choosing a tool, so some of the problems may since have been fixed.
A team on Reddit in 2024 said its on-call group was worried about the switch. They wrote that the only way to preview the result was to “click the start button and hope”. The JSM trial and the migration guide’s list of manual steps now cover that gap.
One user on the Atlassian Community forum who was still choosing a tool said the hard part of leaving OpsGenie is scheduling. In their words, “the alerting is the easy part. it’s the rota that gets you.” They described hand-editing overrides at 11pm when someone books a week off.
The same Reddit user who couldn’t see contact methods after the move also saw an upside. Once JSM is set up, an incident can show related changes, Confluence pages and similar past incidents in one place. They added that this takes a while to build.
Is JSM the right choice for your team?
JSM makes most sense when you want service management and incident response in one product. If OpsGenie is all you’re replacing, you’d be paying for a full ITSM platform.
JSM usually works best if:
- you already run Jira and Confluence and want one vendor
- you need ITSM features such as service requests, change management or problem management
- you have the budget for Premium if you rely on heartbeats, post-incident reviews or custom roles
Another tool may suit you better if:
- you want standalone incident management software like OpsGenie
- keeping your OpsGenie setup would push you onto Premium
- you want status pages without moving to Enterprise
- you want people to edit schedules without Premium or team admin rights
If the second list sounds like your team, it can be helpful to see how Spike compares.
A standalone alternative to JSM: Spike
You’ll redo part of your setup whichever tool you choose. Chat tools, scripts and automation need attention on any route. So it makes sense to pick the tool that’s worth that effort.
Spike is standalone incident management software built around the ideas you already know from OpsGenie. Teams, schedules, rotations, overrides, escalation policies and routing rules all map across. Our concept mapping sheet shows each OpsGenie term next to its Spike equivalent.
| Comparison criteria | JSM Standard | JSM Premium | Spike Business |
|---|---|---|---|
| Monthly price per user (10 users) | $26.90 per agent | $61.60 per agent | $14 |
| Phone and SMS alerts | Unlimited SMS and voice | Unlimited SMS and voice | Unlimited phone and SMS |
| Status pages | Not included | Not included | Public and private included |
| Editing schedules without admin rights | Not available | With a custom role | With the Responder role |
| Heartbeat monitoring | Not included | Included | Not included |
| Help with the move | Automated tool and Solution Partners | Automated tool and Solution Partners | Our team imports your schedules and escalation policies |
Spike costs $7 per user per month on Standard and $14 on Business. Standard includes one schedule and 100 shared phone and SMS alerts a month, so Business is the better fit for larger rotations. Business also adds role-based access, so its Responder role can work with on-call schedules without admin rights. Custom roles cover anything narrower.
Both plans include status pages, the Slack app and the Microsoft Teams bot. AI features come with both plans too, including AI incident titles, severity and priority suggestions and an MCP server. If your team keeps Jira for tickets, Spike’s Jira Cloud integration creates a ticket straight from an incident. Our list of JSM alternatives for teams that keep Jira compares the Jira sync in seven on-call tools.
Spike has no heartbeat monitoring. If you rely on OpsGenie heartbeats, a tool like Cronitor or Healthchecks can watch your jobs and send alerts into Spike.
Moving to Spike also doesn’t have to be a one-way switch. JSM’s migration is permanent, and OpsGenie goes read-only during it. With Spike, both tools can run side by side until you trust the new setup. Our parallel run plan covers the daily checks. HitPath took this route. Their CTO Mark Brody ran OpsGenie and Spike together for about a month:
The migration was easy. Most of the integrations were webhooks, and I ran different escalation policies depending on the different roles we were monitoring. It was a two or three-stage approach, so it wasn’t like flipping the switch on everything at once. We ran OpsGenie and Spike together for about a month, and everything lined up, just to make sure nothing was falling through the cracks. Once we were confident, we canceled our OpsGenie service and opened the gates on Spike.
Our team offers free guided onboarding on every plan and can import your schedules and escalation policies for you.
Virtually Human moved on-call schedules for 15 people across 8 time zones from OpsGenie to Spike with zero disruption. Their Engineering Manager Steven Ryder put it this way:
Spike has been a breath of fresh air compared to OpsGenie. Moving to Spike is something we’re really happy we did. I agree with Spike that handling On-call scheduling and escalations need not be complicated or expensive
OpsGenie teams get 20% off the first year on an annual Spike plan. Our OpsGenie migration guide walks through the move to Spike in three steps and compares JSM, PagerDuty and Spike side by side.
FAQs
These are real questions from the Atlassian Community forum, Google searches and Atlassian’s own docs.
What happens to my OpsGenie Jira integration?
It carries over with the rest of your setup. After the migration, Atlassian lists Jira Software and Jira Service Management integrations under Syncs in JSM. A quick test with one alert through each sync shows whether tickets still flow the way you expect.
How do I get JSM critical alerts to ring through Do Not Disturb on Android?
JSM alerts reach Android phones through the Jira Cloud mobile app. Its Critical Alerts option only works on iOS, so Android needs a Do Not Disturb exception for the Jira app instead. Users on the Atlassian Community forum shared where that setting sits:
- Samsung: Settings, Do not disturb and App notifications
- Pixel: Settings, Modes, Do Not Disturb and Apps, then add Jira
Atlassian tracks Android support for Critical Alerts as an open feature request. A test alert at night before your first on-call shift often helps.
Does our OpsGenie Terraform setup still work after the move?
The OpsGenie Terraform provider gives way to Atlassian’s own atlassian-operations provider. Atlassian publishes a migration guide that maps each OpsGenie resource to its new name, such as opsgenie_team to atlassian-operations_team. Entity IDs stay the same, but you write the import file yourself. The provider currently covers six resource types and three data sources, so some settings may still need managing in JSM itself.
Can I move OpsGenie to Compass instead of JSM?
Not for long. Atlassian’s OpsGenie docs still list Compass as a destination, but in April 2026 Atlassian announced that Compass will be phased out. Its Compass support docs plan the end of support for December 31, 2027 and say alerts and on-call “must be migrated to Jira Service Management”. A move to Compass now means a second move to JSM within about a year.
Can I still start an OpsGenie free trial?
No. OpsGenie stopped new sales and trials on June 4, 2025. JSM has a free plan for up to 3 agents, and its paid plans come with a free trial.
Start your OpsGenie to JSM migration
April 5, 2027 is the final deadline, but your own clock starts on your migration date. OpsGenie turns off 120 days later, and the rebuilds need to be finished by then. If JSM fits your team, Plan your move in OpsGenie and a JSM trial are the best place to start.
If you’d rather stay with standalone incident management software like OpsGenie, Spike is the better move. Its free 14-day trial needs no credit card, so go ahead and try it out alongside OpsGenie. One schedule and one alert source are enough to get a feel for it. You can also book a call with our team or share the case for switching with your manager. Good luck with the move.
