Atlassian is moving every Opsgenie customer to Jira Service Management (JSM) before Opsgenie's end of support on April 5, 2027. JSM now covers Opsgenie's alerting, schedules and escalations on every plan, Free included. What changes is the product around them (a service desk), the price (per agent, about 2.4 times Opsgenie Essentials for a 10-person team) and what you lose: the dedicated mobile app, heartbeats below Premium, and any status page below Enterprise. Facts and prices below were checked on Atlassian's pages in October 2026.
Key takeaways
- Opsgenie: end of sale June 4, 2025; end of support April 5, 2027, when access is shut off and un-migrated data is deleted.
- JSM includes on-call schedules and escalation policies on every plan. Heartbeats need Premium; status pages need Enterprise.
- A 10-person team pays $2,700 a year on JSM Standard (annual billing) against $1,134 on Opsgenie Essentials.
- JSM has no uptime, SSL or browser checks. You still need a monitoring tool.
- Teams that only used Opsgenie for paging should compare the main Opsgenie alternatives before defaulting to JSM.
The Atlassian timeline
| Date | What happens |
|---|---|
| March 4, 2025 | Atlassian announces the end of Opsgenie |
| June 4, 2025 | End of sale: no new sign-ups, no plan changes. Existing customers can still add seats and renew if the term ends before April 5, 2027 |
| Your migration date + 120 days | After an in-app migration to JSM, Opsgenie shuts down automatically unless you turn it off first |
| April 5, 2027 | End of support: access off, REST APIs stop, un-migrated data deleted, mobile app deactivated |
Sources: the FAQ of Atlassian's Opsgenie pricing page and the support article What happens when Opsgenie is turned off?. Atlassian's old process for merging Opsgenie into JSM was replaced by an in-app migration tool (Settings, then Migrate Opsgenie), which moves most data automatically.
What maps from Opsgenie to JSM
| Feature | Opsgenie | JSM (October 2026) |
|---|---|---|
| On-call schedules | All plans | All plans, Free included |
| Escalation policies and routing rules | All plans (1 routing rule on Free and Essentials) | All plans; advanced escalation and routing from Standard |
| SMS and voice notifications | Quotas on Free and Essentials | 200 SMS a month, no voice, on Free; included from Standard |
| Heartbeat monitoring | Standard and Enterprise | Premium and Enterprise |
| Stakeholder communication | Free stakeholder users on Enterprise | Premium and Enterprise |
| Status pages | Internal service status pages, no public page | Enterprise only |
| Alert history kept | 3 months (Free) to no limit (Enterprise) | 1 month (Free), 1 year (Standard), 3 years (Premium), 5 years (Enterprise) |
| Mobile app | Dedicated Opsgenie app | Jira mobile app |
| Uptime, SSL or browser checks | No | No |
| Service desk, change and asset management | No | Yes |
| Pricing model | Per responder user | Per agent |
Two features need attention during the move. If you used heartbeats to watch cron jobs and backups on Opsgenie Standard, the JSM equivalent is Premium, the most expensive self-serve plan. And if you want a status page in the same product, JSM only offers it on Enterprise, so most teams keep paying for Statuspage or another tool.
JSM pricing vs Opsgenie pricing
JSM is now sold in Atlassian's Service Collection. The per-agent price drops as the team grows: Standard is $26.90 per agent per month at 10 agents and $21.50 at 75 agents, billed monthly. The figures below come from Atlassian's pricing calculator on October 29, 2026.
| Plan | 10 agents, monthly billing | 10 agents, annual billing | 20 agents, monthly billing |
|---|---|---|---|
| JSM Free | Not available (3 agents max) | Not available | Not available |
| JSM Standard | $26.90/agent ($269/mo) | $2,700/yr | $25.21/agent ($504/mo) |
| JSM Premium | $61.60/agent ($616/mo) | $6,200/yr | $59.63/agent ($1,193/mo) |
| JSM Enterprise | Annual only, sales quote | Sales quote | Sales quote |
| Opsgenie Essentials (existing customers, list price) | $11.55/user ($115.50/mo) | $1,134/yr | $231/mo |
| Opsgenie Standard (existing customers, list price) | $24.15/user ($241.50/mo) | $2,394/yr | $483/mo |
For a 10-person team on annual billing, moving from Opsgenie Essentials to JSM Standard takes the bill from $1,134 to $2,700 a year. Moving from Opsgenie Standard with heartbeats to JSM Premium takes it from $2,394 to $6,200. Neither JSM plan adds uptime monitoring, and only Enterprise adds a status page.
Every person who acknowledges alerts needs an agent license. Some teams respond by limiting who gets one, which is the opposite of what you want at 3 a.m.
What JSM does well
JSM is a strong product for teams that need more than paging.
- Jira and Confluence are native. Incidents link to tickets, epics and deployments, and runbooks and post-incident reviews live next to them.
- ITSM is included. Request management and asset management come with Standard; change management with AI risk assessment comes with Premium.
- Automation is deep. 3,000 automation steps per user per month on Standard and 6,500 on Premium, with triggers across Atlassian products.
- AIOps on Premium. Alert grouping, AI incident creation and post-incident review drafts.
- One vendor. Procurement, SSO and audit logs stay inside the Atlassian contract you already have.
Where JSM falls short for on-call teams
No checks of its own
JSM routes alerts from monitoring tools; it does not run checks. Opsgenie never did either, but its heartbeats covered cron jobs on Standard. On JSM those heartbeats need Premium. Uptime, SSL and browser checks still come from another product.
The mobile app changes
Opsgenie's app did one job: acknowledge, escalate and check who is on call. When Opsgenie turns off, that app is deactivated, and responders move to the Jira mobile app, where on-call sits beside projects, boards and service requests.
More to configure
Opsgenie was a focused tool. JSM brings service desks, request types, workflows, queues and SLAs along with the on-call features. Atlassian's in-app migration moves most data automatically, but teams that only need paging still have a larger product to administer.
Status pages move to Enterprise
Status pages are part of JSM Enterprise only. Below it, a public status page means Statuspage or another tool, with its own bill.
Opsgenie vs JSM vs Hyperping
For teams evaluating options beyond Atlassian, here is how the three compare as of October 2026:
| Feature | Opsgenie (ends April 5, 2027) | JSM Standard | Hyperping |
|---|---|---|---|
| On-call schedules and escalation policies | Yes | Yes | Yes, from Essentials |
| Uptime, SSL, DNS and port checks | No | No | Yes |
| Browser checks (Playwright) | No | No | Yes |
| Cron job monitoring | Heartbeats (Standard and Enterprise) | Heartbeats on Premium | Healthchecks on every plan |
| Status page | Internal service status pages only | Enterprise only | Yes, custom domain from Essentials |
| Phone call and SMS alerts | Yes, quotas by plan | Yes | Yes, phone calls from Essentials |
| Dedicated mobile app | Yes | Jira mobile app | No (phone, SMS, email, Slack, Teams) |
| Service desk and change management | No | Yes | No |
| Jira integration | Yes | Native | Creates and closes JSM alerts |
| Pricing, 10 people | $1,134/yr (Essentials) | $2,700/yr | $890/yr (Pro, 10 seats included) |
Hyperping covers the paging part of Opsgenie and adds the monitoring and status page that JSM leaves out. It does not replace a service desk. Two differences to plan for: acknowledging an outage on Hyperping stops its repeat alerts but not the escalation, and a missed healthcheck alerts every channel at once rather than following the on-call schedule.
You can also combine them. Teams that keep JSM for their service desk can use Hyperping for checks and the status page, and let Hyperping open and close JSM alerts when a monitor goes down and recovers.
Who should move to JSM
Move to JSM if:
- Your team already uses Jira and Confluence daily
- You need request management, change approvals or asset management
- Procurement wants a single Atlassian contract and Atlassian Guard for SSO
- You can budget per-agent licenses for every responder
Who should look elsewhere
Engineering teams that used Opsgenie for paging only. You pay for a service desk you will not use, and you still buy monitoring separately.
Teams that relied on heartbeats or a public status page. On JSM those mean Premium and Enterprise.
Small teams past 3 responders. JSM Free stops at 3 agents, and the per-agent price is highest for small teams.
For these teams, start with our guide to Opsgenie alternatives and migration, which compares Hyperping, PagerDuty, incident.io and Better Stack with October 2026 prices. If PagerDuty is on your list, read Opsgenie vs PagerDuty.
How to move off Opsgenie without JSM
Hyperping migrates Opsgenie customers for free on any paid plan: send your export, and within 48 hours the team rebuilds your monitors, escalation policies, on-call schedules, alert channels, heartbeats and status page, then hands it over in a 30-minute call. Book the free migration, or follow the Opsgenie migration guide to do it yourself. The 14-step migration checklist covers the project plan and the parallel run.
Whatever you choose, start before the deadline. Exports, a parallel run and team training take longer than they look, and after April 5, 2027 there is nothing left to export.
FAQ
Is JSM better than Opsgenie? ▼
For a team that only does alerting and on-call, no. JSM covers the same schedules, escalations and routing, but inside a service desk product billed per agent, and Opsgenie's dedicated mobile app is replaced by the Jira app. JSM is better when you also need request management, change approvals or asset management in Jira.
Does Jira Service Management include on-call? ▼
Yes, on every plan as of October 2026. JSM Free includes alerts, on-call schedules and escalation policies for up to 3 agents, with 200 SMS a month and no voice calls. Standard adds advanced escalation and routing, SMS and voice. Heartbeat monitoring and stakeholder communication need Premium, and status pages need Enterprise.
How much does JSM cost compared to Opsgenie? ▼
As of October 2026, JSM Standard is $26.90 per agent per month for 10 agents billed monthly, or $2,700 a year for 10 agents billed annually. Premium is $61.60 per agent per month, or $6,200 a year. Opsgenie was $9.45 per user per month on Essentials and $19.95 on Standard, billed annually, so a 10-person team on Opsgenie Essentials paid $1,134 a year.
Do I have to move to JSM from Opsgenie? ▼
No. Atlassian offers an in-app migration to JSM or Compass, but you can move to any on-call tool before Opsgenie's end of support on April 5, 2027. Hyperping, PagerDuty, incident.io and Better Stack are the common alternatives. Hyperping migrates Opsgenie customers for free on any paid plan.
When does Opsgenie stop working? ▼
On April 5, 2027, Atlassian shuts off access and deletes un-migrated data. New sales ended on June 4, 2025. If you use the in-app migration to JSM, Opsgenie also shuts down automatically 120 days after your migration date unless you turn it off sooner.
What happens to the Opsgenie mobile app? ▼
It is deactivated when Opsgenie is turned off. Atlassian tells responders to switch to the Jira mobile app before shutdown, where on-call actions sit next to projects, boards and service requests.
What does JSM Premium add over Standard? ▼
As of October 2026, Premium adds heartbeat monitoring, major incident escalation, stakeholder communication, AI alert grouping and post-incident review generation, change management, a virtual service agent, 3 years of alert history instead of 1, a 99.9% uptime SLA and 6,500 automation steps per user per month instead of 3,000.
