Checked on November 3, 2026 against Atlassian’s and Spike’s docs and pricing pages.
Quick answer: Jira Service Management (JSM) is the better move if your company already runs a service desk in JSM and wants incidents as Jira work items. Spike is the better move if you want standalone incident management software like OpsGenie, without a service desk around it. For a team of 10 billed monthly, JSM costs about $269 on Standard and $616 on Premium. Spike costs $70 on Standard or $140 on Business. OpsGenie users also get 20% off their first year of Spike on an annual plan.
TL;DR
- OpsGenie shuts down on April 5, 2027. Data you haven’t moved by then is deleted.
- JSM Standard leaves out repeat escalation, heartbeats and post-incident reviews. Those start on Premium.
- Status pages come only with JSM Enterprise. Below that, Statuspage.io is a separate bill. Spike includes a status page on every plan.
- Atlassian’s migration tool carries over your schedules and escalation policies. With Spike, our team recreates them for you. You can also do it yourself with the API, Terraform provider or MCP server.
OpsGenie shuts down on April 5, 2027. Atlassian’s official replacement is Jira Service Management (JSM), an IT service management platform that now includes OpsGenie’s alerting and on-call features. Spike is standalone incident management software, like OpsGenie.
This post compares the two for an OpsGenie team. It covers alerting and escalations, incident response, on-call schedules, cost, and what carries over when you move. A table near the end maps your situation to the better fit.
I tried my best to give you a fair picture. I set up both tools and ran the same alerts and schedules through each. Plus, I re-checked every claim below against the vendors’ docs and pricing pages. Wherever JSM is the stronger choice, the post says so.
JSM vs. Spike at a glance
| Comparison criteria | JSM | Spike |
|---|---|---|
| What it is | IT service management platform with alerting and on-call bolted on | Standalone incident management software |
| Cost for 10 people (monthly) | $269 on Standard, $616 on Premium | $70 on Standard (one on-call schedule), $140 on Business (unlimited schedules) |
| Channel for each escalation step | No. Each person’s notification settings decide | Yes. Call, SMS, Slack and more per step |
| Repeat escalation | Premium and Enterprise, up to 20 repeats | Yes, up to 5 repeats |
| Status pages | Enterprise only, or Statuspage.io as a separate product | Included on every plan |
| Post-incident reviews | Built-in templates on Premium and Enterprise | Notes and incident timeline, no templates |
| Jira | Native. Incidents are Jira work items | Two-way sync of status changes and comments on Business |
| Video war rooms | Zoom and Teams on Premium and Enterprise | Google Meet in one click, or any room link, on Business |
| AI | AI alert grouping and draft reviews on Premium | AI titles and severity suggestions on every plan, plus Spike AI in Slack |
| Heartbeats | Premium and Enterprise | None native. Cronitor or Healthchecks send alerts into Spike |
| OpsGenie migration | Atlassian’s migration tool | Our team recreates your rotations and escalations. Or do it yourself with the API, Terraform or MCP server |
Many of the rows above depend on the JSM plan. Repeat escalation, heartbeats, post-incident reviews and incident work in Slack or Teams all start at Premium. So for an OpsGenie team, the fair JSM price to compare is often Premium rather than Standard. Our JSM review shows where each plan stops.
Alerting and escalations
Both tools keep the OpsGenie basics: integrations create alerts, escalation policies decide who hears about them, and people acknowledge from their phone or chat. The differences sit in how much control a policy has and which plan you need.
Escalations in JSM
JSM keeps OpsGenie’s model. An escalation policy decides who gets alerted and when. How each person is alerted comes from their own notification settings, so a policy can’t say “call first and text after”.
Free and Standard leave out a few escalation options. Atlassian’s escalation docs list repeat escalation among them, along with alerting the next or previous person in a schedule. On Premium and Enterprise, an escalation can repeat up to 20 times and close the alert when the repeats finish.
Escalations in Spike
Spike lets the policy choose the channel for each step. One policy can call at step one, send an SMS at step two and post to Slack at step three. People can still set their own rules for office hours and time off, so the policy and the person both have a say.
Repeat escalations work on any integration you mark as critical. Spike restarts the policy until someone acknowledges or resolves the incident, up to 5 times. Responders can act from any channel, which includes pressing a key during a phone alert or replying #ack or #res to an email alert.
Which fits your alerting
JSM probably suits you if your team is happy with OpsGenie’s person-by-person model and you plan to be on Premium anyway. Spike usually works best if you want one policy to set the channel at each step, or if you need repeat escalation without moving up a plan.
Incident response
Incident response in JSM
In JSM, an incident is a Jira work item. It sits next to the rest of your Jira work, so linking an incident to a bug or a change needs no extra setup.
Running incidents from Slack, Microsoft Teams or Zoom needs Premium or Enterprise. The same goes for post-incident reviews, which come with built-in templates and AI drafts.
Status pages are the bigger catch. JSM includes them only on Enterprise. Below that, JSM teams buy Statuspage.io as a separate product. Its paid public plans cost $29, $99, $399 or $1,499 a month.
Incident response in Spike
Spike automates the first minutes of an incident. Alert routing rules can route, acknowledge or resolve incidents based on what the alert says. Playbooks run a set of actions when an incident triggers. An acknowledge timeout turns an acknowledged incident back into an open, unacknowledged one if nobody resolves it in time. Spike then starts alerting again. A resolve timer closes incidents that clear up on their own.
A status page comes with every plan, along with a custom domain and subscribers. Business adds private status pages. On Business, war rooms start a Google Meet call in one click. Zoom support is on the way. Business also keeps Jira in the loop through a two-way sync, so status changes and comments move in both directions.
Spike doesn’t have post-incident review templates. After an incident, notes hold the write-up with Markdown, attachments and an edit history. The timeline and activity log show what happened and when. In Slack, you can mention @Spike to declare an incident or add an override in plain language.
Which fits your incident response
JSM is the stronger choice if you want built-in post-incident reviews and incidents that live as Jira work items. Spike fits better if you want a status page without a higher plan or a second product. It also suits engineers who coordinate in Slack or Google Meet.
On-call schedules
On-call in JSM
JSM builds schedules inside teams, the same way OpsGenie did. Each schedule has three layers. Base shows the planned rotation, Overrides shows the changes and Final shows who is actually on-call. A “Take on-call” button lets someone cover the next hour in one click.
On-call in Spike
Spike shows a live calendar preview while you build a schedule. Layer templates cover weekdays, weekends, night shifts and business hours. You can add gaps to a rotation, set a layer to start and end on fixed dates, and pick the weekday when handoffs happen.
Overrides can carry a comment that explains the change. Out of Office hands your alerts to a teammate while you’re away. Spike can also post shift starts and ends to a Slack, Teams or Discord channel and trigger a webhook on each handoff.
Which fits your on-call
JSM’s layer view will feel familiar if you liked OpsGenie’s schedules. Spike is the better fit if your rotations need gaps, holiday layers or a shared channel that shows who is on-call.
What JSM and Spike cost an OpsGenie team
JSM is priced per agent, and everyone on an on-call schedule needs an agent licence in practice. A 10-person rotation means 10 agents. Spike is priced per user, and its plans differ by how many schedules you need.
| Team size | JSM Standard | JSM Premium | Spike Standard | Spike Business |
|---|---|---|---|---|
| 10 people | $269 a month | $616 a month | $70 a month | $140 a month |
| 25 people | $605 a month | $1,461 a month | $175 a month | $350 a month |
| 50 people | $1,109 a month | $2,804 a month | $350 a month | $700 a month |
Prices are for monthly billing, read on November 2, 2026. Spike Standard covers one on-call schedule and 100 phone and SMS alerts a month. Business removes both limits.
Atlassian starts usage-based billing on December 3, 2026 for automation runs and AI credits beyond each plan’s allowance. Our JSM pricing breakdown covers every JSM plan and these extra costs in detail.
What carries over from OpsGenie
Moving to JSM
Atlassian’s migration tool carries over users, schedules, escalation policies and alerts. Slack and Teams need fresh authentication. Actions and incident rules don’t carry over, so you rebuild them in Jira Automation. Scripts that call the OpsGenie API also need new endpoints and Atlassian authentication.
OpsGenie stays open for 120 days after your migration date and then turns off. Our OpsGenie to JSM migration guide walks through each step.
Moving to Spike
Our team recreates your OpsGenie rotations and escalation policies for you. If you’d rather do it yourself, the API, Terraform provider and MCP server let you script the whole setup. Each integration is a webhook URL, so pointing a monitoring tool at Spike is a small change.
OpsGenie keeps running while you set up Spike, so you can run both until a full rotation has passed. Heartbeats are the one gap. Spike has no native heartbeat monitoring, so Cronitor or Healthchecks can watch your jobs and send alerts into Spike. Our OpsGenie migration guide and migration kit cover the full move.
Which should you pick?
It comes down to three questions. How much of your company already runs on Jira? What do you use OpsGenie for? How many people are on-call?
| If this sounds like you | Better fit |
|---|---|
| Your company already runs IT or customer requests in JSM | JSM |
| You want incidents as Jira work items with built-in post-incident reviews | JSM Premium |
| You want Atlassian’s own migration tool and Premium fits your budget | JSM |
| Your engineers track work in Jira, and OpsGenie only handles alerts and on-call | Spike |
| You need repeat escalation or a channel per step without a higher plan | Spike |
| You want a status page without JSM Enterprise or Statuspage.io | Spike |
| You have 25 or more people on-call and a fixed budget | Spike |
| You rely on native heartbeat monitoring | JSM Premium, or Spike with Cronitor |
Using Jira for project work doesn’t mean you need JSM. Jira and JSM are separate products with separate licences. On Spike Business, a two-way sync keeps incidents and Jira tickets in sync without extra JSM seats. Our list of JSM alternatives for teams that keep Jira compares the Jira sync in other on-call tools too.
JSM vs. Spike: feature checklist
Both tools cover the OpsGenie basics: team and individual alert control, deduplication and grouping, time-based routing and incidents from email. The checklist below shows where they differ. When a feature needs a higher plan, the cell names it.
| Checklist item | JSM | Spike |
|---|---|---|
| Price for 10 people (monthly) | $269 on Standard, $616 on Premium | $70 on Standard, $140 on Business |
| Channel for each escalation step | ❌ | ✅ |
| Built-in post-incident review templates | ✅ Premium and up | ❌ |
| Repeat escalations on every plan | ❌ Premium and up | ✅ |
| Jira sync | ✅ Native | ✅ Two-way, on Business |
| Native heartbeat monitoring | ✅ Premium and up | ❌ |
| Status page on every plan | ❌ Enterprise only | ✅ |
| Video war room from the incident | ✅ Zoom or Teams, Premium and up | ✅ Google Meet, on Business |
| Service desk and change management | ✅ | ❌ |
| AI without usage-based billing | ❌ | ✅ |
What stands out in Spike
Spike is standalone incident management software, like OpsGenie. Alerts, on-call schedules, escalations, phone and SMS alerts and status pages come in one product, with no service desk around them.
AI writes a readable title for each alert and suggests severity and priority on every plan. In Slack, Spike AI handles incidents, overrides and on-call questions in plain language. A remote MCP server lets AI assistants read and act on your incidents too.
Moving over comes with dedicated migration support from our team. OpsGenie users also get 20% off their first year on an annual plan. HitPath ran OpsGenie and Spike side by side before switching. Its CTO Mark Brody said:
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.
FAQs
Is JSM different from Jira?
Yes. Jira plans and tracks project work, while JSM handles service requests, incidents and on-call. They’re separate products with separate licences. Our guide on what JSM is explains the difference in more detail.
Do on-call responders need a JSM licence?
In practice, yes. Two Atlassian Community Champions explained in June 2026 that OpsGenie-only users became JSM agents to stay on on-call schedules. Premium and Enterprise add a free stakeholder role for people who only need updates. It’s worth confirming your own case with Atlassian Support.
Does Spike sync with Jira both ways?
Yes, on the Business plan. Spike creates a Jira ticket from an incident, and status changes and comments sync in both directions. Business can also create tickets in Linear, ClickUp and Shortcut.
Does JSM include a status page?
Only on the Enterprise plan. Below Enterprise, JSM teams buy Statuspage.io as a separate product. Its paid public plans cost $29, $99, $399 or $1,499 a month. Every Spike plan includes a status page.
Is JSM better than Spike?
It depends on what you need around incident management. JSM is better if your company wants a service desk, change management and incidents in one Atlassian product. Spike is better if you want OpsGenie-style alerting and on-call as a standalone tool. It also gives you a status page and repeat escalation on every plan.
Making the call
If your company already lives in JSM, the official path is the better move. If OpsGenie was your standalone alerting and on-call tool, Spike is the better move. You keep that setup without paying for a service desk around it.
A trial next to OpsGenie is a low-risk first step. You can start a Spike trial and run it alongside OpsGenie, or book a demo with our team. Good luck with the move.
