TL;DR
Atlassian ended OpsGenie sales on June 4, 2025. It shuts the product down on April 5, 2027 and deletes any data you haven’t moved. An OpsGenie migration is probably easier to plan now than in the final month. JSM is a good fit if you are heavily invested in Atlassian, and PagerDuty works if you have the budget for its add-ons. Spike is often the smoother move if you want a tool that feels familiar. You’ll feel at home from day one because your schedules, escalation policies and alert routing work the way you expect. Our team can import your setup, and OpsGenie teams get 20% off the first year on an annual plan.
Your OpsGenie migration has a deadline of April 5, 2027. A careful move usually takes weeks, so it helps to start early. This guide covers the key dates, three migration options, and what carries over from OpsGenie. It also shows how to move to Spike, step by step. Spike is our tool, so we’ll be upfront about where it fits and where another option suits you better.
To make the move easier, we built a free OpsGenie migration resource including a checklist, an export guide, and a parallel run plan.
When does OpsGenie shut down?
OpsGenie shuts down on April 5, 2027. Atlassian ended new sales on June 4, 2025. After the shutdown the product is no longer accessible, and Atlassian deletes any data you haven’t moved.
The OpsGenie REST API keeps working until then, so you can still export your setup. If you turn OpsGenie off early, all access ends at once. The mobile app and the remaining integrations stop with it, and there is no way to undo the switch. It can be helpful to export everything before anything gets switched off.
Atlassian honours your current OpsGenie subscription until its term ends or until April 5, 2027, whichever comes first. You can keep OpsGenie live while you set up Spike and run both side by side. If your renewal comes up before the shutdown, the new term has to end by April 5, 2027 and plan changes aren’t allowed. A renewal can work as buffer time for a careful move rather than a reason to wait. A move squeezed into the final months leaves little room to fix gaps in coverage.
Atlassian’s automated move to JSM keeps OpsGenie open for 120 days, and it turns read-only along the way. That window only applies to the JSM route. With Spike you decide how long both tools run.
You’ll find why Atlassian is shutting OpsGenie down and what maintenance mode means for you in our OpsGenie shutdown guide.
OpsGenie migration options: JSM, PagerDuty, or Spike
Atlassian points OpsGenie users to JSM. PagerDuty is the other popular name in on-call, and Spike is our tool. The table below compares all three so you can weigh them side by side. For a wider comparison with incident.io, Xurrent and SolarWinds, see our guide to OpsGenie alternatives for startups. For larger organisations, our guide to OpsGenie alternatives for enterprise teams compares seven tools on access control, migration help and pricing. We checked every price on October 19, 2026. Vendors change prices from time to time, so it can be useful to confirm them before you buy.
OpsGenie migration compared: JSM vs PagerDuty vs Spike
| Comparison criteria | JSM | PagerDuty | Spike |
|---|---|---|---|
| Monthly price per user | $21.50 per agent on Standard and $55.28 on Premium. | $25 on Professional. A free plan covers up to 5 users. | $7 on Standard and $14 on Business. |
| Phone, SMS and voice alerts | SMS and voice alerts on every paid plan. | 100 SMS or phone notifications a month on Free. Included on Professional with no stated cap. | 100 shared phone and SMS alerts a month on Standard. Unlimited on Business. |
| Schedules, overrides and escalation policies | Advanced escalation and routing on every paid plan. | 1 schedule and 1 escalation policy on Free. Included on Professional. | Overrides and escalation policies on both plans. 1 schedule on Standard and unlimited on Business. |
| Slack and Microsoft Teams | Chat integrations need to be reconnected by hand after the move. | Basic on Free and enhanced on Professional. | Slack app and Microsoft Teams bot on both plans. |
| Status pages | Included on Enterprise only. Sold separately as Statuspage on lower plans. | A paid add-on on Professional. | Included on both plans. Private status pages on Business. |
| AI features | Rovo AI and AI alert grouping. Monthly Rovo credits per user grow with the plan. | Generative AI and noise reduction are paid add-ons on Professional. | AI incident titles, severity and priority suggestions, and an MCP server on every plan. |
| Moving your OpsGenie setup | Atlassian’s tool moves most of your setup. Chat integrations, actions and incident rules need a rebuild. | PagerDuty’s Professional Services team helps under its OpsGenie offer. We couldn’t find a self-serve OpsGenie importer. | Our team imports your schedules and escalation policies. You can also build them with Terraform, the API or the MCP server. |
| Help during the migration | Atlassian’s automated tool does the move. For hands-on help, Atlassian works with its Solution Partners. | Up to 80 free service hours for the first 50 qualifying customers with up to 250 users, on the Operations Cloud Core plan. | Free guided onboarding on every plan. |
Note: JSM’s per-agent price changes with team size. We read these prices at the default of 75 agents.
Move to JSM if you’re heavily invested in Atlassian
If your team already works in Jira and Confluence, JSM is the path of least resistance. Atlassian’s migration tool moves most of your setup for you. That covers users, alerts, schedules, escalation policies, existing incidents and most integrations. OpsGenie stays open for 120 days after the move.
There are a few trade-offs to weigh. Heartbeats, post-incident reviews and custom roles sit on Premium, which costs $55.28 per agent per month. Slack and Teams connections need to be set up again after the move. Actions and incident rules stay behind in OpsGenie, so they have to be rebuilt in Jira Automation. Incident templates don’t carry over either. For hands-on help with the move, Atlassian points you to its Solution Partners.
One Reddit user who went through an earlier forced move said they lost sight of their team’s notification policies. That included phone numbers and whether people had installed the app. It came from an earlier migration wave, so consider checking whether it still applies to your account.
Our JSM pricing breakdown, JSM vs Spike comparison and OpsGenie to JSM migration guide go deeper on each point.
Move to PagerDuty if you have the budget for its add-ons
PagerDuty is a mature on-call tool, and its Professional plan covers the basics at $25 per user per month. Phone and SMS notifications are included with no stated cap. Slack and Microsoft Teams come with enhanced features on the same plan.
The bill grows once you need more than the basics. Status pages, generative AI and runbook automation are paid add-ons on Professional. Noise reduction needs AIOps, which is a separate purchase. It’s worth pricing those add-ons before you compare totals.
PagerDuty also offers help with the move. Its Professional Services team gives up to 80 free hours to the first 50 qualifying OpsGenie customers with up to 250 users. The offer applies only to the Operations Cloud Core plan. It isn’t a discount, and PagerDuty says it may change the offer at any time.
Our PagerDuty pricing breakdown covers the costs in more detail, and our OpsGenie vs PagerDuty comparison asks whether PagerDuty is the right migration path for you.
Move to Spike if you want your OpsGenie setup to feel familiar
Spike uses the concepts you already know from OpsGenie. Teams, schedules, rotations, overrides, escalation policies and routing rules all work the way you expect, so you feel at home from day one. Nearly all of them map one to one. Our concept mapping sheet lets you look up any OpsGenie term and see its Spike equivalent.
Spike costs $7 per user per month on Standard and $14 on Business. The Slack app, the Microsoft Teams bot, status pages and AI features come with both plans. Our team offers free guided onboarding on every plan and can import your schedules and escalation policies for you. You can also build them yourself with Terraform, the API or the MCP server.
There are two limits worth knowing. Standard allows one schedule and 100 shared phone and SMS alerts a month, so Business is the better fit if you need more than one schedule. Spike also has no heartbeat monitoring. If you rely on OpsGenie heartbeats, a tool like Cronitor or Healthchecks can watch your jobs and send alerts into a Spike integration.
People who use Spike day to day say the same thing. A system administrator on G2 gave it 4.5 out of 5 on G2 and wrote:
What I like best about Spike.sh is its simplicity. The interface is clean and well designed, and setting up escalations, on-call schedules and integrations is quick and intuitive. Once a setup is in place it’s easy to repeat for other teams or services, so adding new ones takes minutes rather than hours.
A verified reviewer in pharmaceuticals also gave it 4.5 out of 5 on G2:
Escalation policies are easy to create, and the UI is very smooth and interactive.
What carries over from OpsGenie, and what doesn’t
Most of your setup can be exported through the OpsGenie API. A few pieces stay behind and need to be set up again in your new tool. Knowing which is which before the move saves you surprises later.
What you can export from OpsGenie
The OpsGenie API gives you all of this with a read-only key. Only account owners and admins can create that key.
- Users and teams
- Schedules and rotations
- Escalation policies
- Team routing rules
- Alert and notification policies
- Integration settings
- Heartbeats
- Each person’s notification rules
- Alert history
Alert history comes with a few limits. Each call returns up to 100 alerts, and the API stops at 20,000 results per search. Older history comes out in smaller searches, such as one month at a time. The API host also depends on where your account lives. US accounts use api.opsgenie.com and EU accounts use api.eu.opsgenie.com, and a request to the wrong host fails. Our export guide lists all ten calls with the settings for each.
What you can’t export
Integration credentials and webhook URLs don’t come out of the OpsGenie API. Chat connections stay behind too, so Slack and Microsoft Teams need to be connected again. Each person’s notification rules can be listed. The phone and SMS steps may not come back for your account, so the safe plan is to set those up again in Spike.
Our team can import your schedules and escalation policies for you. If you’d rather build them yourself, Terraform, the Spike API and the MCP server all work.
How to migrate from OpsGenie to Spike, step by step
The move to Spike comes down to three steps: get ready, set up and switch over. Each step has a free PDF in the OpsGenie migration hub.
Step 1: Get ready and export your OpsGenie data
- Create a read-only API key in OpsGenie. You’ll find it under Settings, App Settings and API Key Management, and read and configuration access is enough.
- Export your users, teams, schedules, escalation policies and routing rules. The users list returns 100 people per page and leaves out phone numbers and emails, so add the contact expand on each user.
- List every tool that sends you alerts. These are the webhooks you’ll point at Spike later.
- Use the concept mapping sheet to translate each OpsGenie term into Spike. Track your progress in the migration checklist.
The exported JSON files deserve a safe place. They stay your record of how OpsGenie was set up, even after you cancel it.
Step 2: Set up Spike
- Start a free Spike trial. It lasts 14 days and needs no credit card.
- Ask everyone on the team to verify their phone number and email, because Spike alerts only go to verified contacts.
- Build your schedules and escalation policies. Recreate each OpsGenie rotation as a layer and use slots for time restrictions. Our team can also import these for you.
- Connect Slack or Microsoft Teams.
- Add each Spike webhook URL to the matching monitoring tool. Our integration guide covers Datadog, Prometheus, AWS, Grafana, New Relic, Sentry, Azure and Google Cloud.
- If you use incoming call routing, connect your own Twilio or Plivo number. Your OpsGenie incoming-call number can’t be ported into Spike.
If you prefer code, Terraform, the Spike API and the MCP server cover the same setup. If you’d like a hand, you can write to [email protected] or book a call.
Step 3: Switch over without gaps in coverage
A parallel run is the safest way to switch. Both tools run side by side until you have covered a full on-call rotation. OpsGenie keeps alerting while Spike receives every alert, and you compare the two each day. Once they match, alerting moves to Spike in phases. You’ll find suggestions on the daily checks in our parallel run plan.
HitPath took this route. Mark Brody, their CTO, 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.
Virtually Human moved on-call schedules for 15 people across 8 time zones with zero disruption. Steven Ryder, their Engineering Manager, 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
Once you’re confident, you can turn off OpsGenie notifications and remove its webhooks from your monitoring tools. Cancelling well before April 5, 2027 leaves room to fix anything you missed. Switching OpsGenie off can’t be undone, so the export from step 1 needs to be complete before then.
What changes after you migrate from OpsGenie to Spike
Day to day, most of your setup stays the same. Teams, schedules, rotations, overrides, escalation policies, routing rules and integrations all have a direct home in Spike. That keeps the move familiar from the first shift.
A few things work a little differently:
- Notification rules: Each person sets up their own rules in Spike, including the phone and SMS steps.
- Escalations: Each integration carries its own escalation policy, and repeat escalations are set per integration.
- Webhooks: Every monitoring tool points at a new Spike webhook URL, since OpsGenie credentials don’t carry over.
- Chat: Slack and Microsoft Teams get connected again in Spike.
- Heartbeats: Spike has no heartbeat monitoring. Cronitor or Healthchecks can watch your jobs and send alerts into Spike instead.
The concept mapping sheet lists every difference row by row, and it makes a handy reference for the first few weeks.
Common OpsGenie migration mistakes and how to avoid them
- Wrong routing: Alerts reach the wrong team, or nobody at all. A test alert through every routing rule before cutover catches this early.
- Missed integrations: A quiet tool that nobody remembered stops alerting after the switch. A full list of alert sources at the start prevents this. Spike has 80+ integrations, and each one is a single webhook URL. If a tool you use isn’t on that list yet, we typically build the integration within 72 hours.
- Alerts that never ring: Phone and SMS delivery depends on the country. Spike reaches 100+ countries, and the geo permissions page shows whether yours is covered before cutover.
- Forgotten overrides: Upcoming overrides in OpsGenie, such as holiday swaps, are easy to miss when you rebuild a schedule. A last look at each OpsGenie schedule before cutover keeps those shifts covered in Spike.
- Unverified contacts: Spike alerts only go to verified contacts. A phone and email check for everyone in the first week closes that gap.
- Double alerts: People get two alerts for every issue during a parallel run. A heads-up to the team before it starts helps, and alerting can then move to Spike in phases.
If anything feels stuck during the move, Spike support is one message away at [email protected]. Our team is proactive and quick to reply, and customers notice. Vlad Ardelean, Co-Founder and CTO of SocialBee, put it this way:
The support team at Spike is incredibly responsive. We often get answers within minutes. They treat our issues with the same priority we do.
OpsGenie migration questions, answered
These are real questions from OpsGenie users on the Atlassian Community forum and Reddit. We read the past year of threads and picked the ones that keep coming up.
Will my OpsGenie alert history come with me?
It depends on where you go. If you move to JSM, Atlassian’s migration tool copies your alerts and past incidents into JSM. A forum reply notes that how far back that history goes depends on your JSM plan. For any other tool, you can export alert history through the OpsGenie API at up to 100 alerts per call. The exported files then stay your record of past alerts.
What happens to my OpsGenie phone number?
If you move to Spike, your OpsGenie incoming-call number can’t be ported. You can connect your own Twilio or Plivo number to Spike’s live call routing instead.
Do my integrations keep working after the move?
On JSM, most of them do. Atlassian’s tool moves most integrations for you, though Slack and Microsoft Teams need to be connected again. For any other tool, each monitoring tool needs a new webhook URL because OpsGenie credentials and webhook URLs can’t be exported. Our integration guide shows the change in Spike for Datadog, Prometheus, AWS, Grafana and other common tools. One Atlassian Community reply also says the opsgenie.net email domain retires “sometime in 2027”, so it’s best not to build anything new on it.
Our scripts call the OpsGenie API. What changes?
Those scripts stop working when OpsGenie shuts down. On JSM, they move to the JSM Operations REST API, and forum users report that a few OpsGenie calls have no direct match there. On Spike, the Spike API covers incidents, on-call schedules, overrides, escalation policies, integrations and services. The MCP server can also build schedules and escalation policies for you.
How do I carry over upcoming overrides, like holiday swaps?
One forum user summed it up well: “The alerting is the easy part, it’s the rota that gets you.” Upcoming overrides are the piece most likely to slip through when you rebuild a schedule. In Spike, overrides are on both plans and sit on top of each rotation layer. It helps to recreate any upcoming ones before cutover.
Who helps with an OpsGenie migration?
That varies by tool. Atlassian’s automated tool handles the move to JSM, and for hands-on help Atlassian points you to its Solution Partners. PagerDuty offers up to 80 free hours to its first 50 qualifying customers on the Operations Cloud Core plan. Spike gives free guided onboarding on every plan. You can write to [email protected] or book a call.
Do I have to license everyone if I move to JSM?
Most likely, yes. Atlassian’s migration maps OpsGenie users to JSM agents, and JSM prices by agent. Stakeholders keep a stakeholder role. One Reddit user who moved said they ended up double licensing many people. Atlassian can confirm the exact count for your account.
Start your OpsGenie migration
You have until April 5, 2027 to move off OpsGenie. An early start leaves time for a calm parallel run and a clean cutover.
OpsGenie teams get 20% off their first year on an annual Spike plan. The free 14-day trial needs no credit card, so go ahead and try it out with one schedule and one alert source. If you’d like help mapping your setup, you can book a call with our team.
If your manager needs convincing, the case for switching is a short brief on why to move, what Spike costs for your team size and what the move involves. Good luck with the move.
