Opsgenie replacement for Jira teams that stay off Jira Service Management

If your engineers plan work in Jira Software and used Opsgenie only for on-call and alerting, you do not have to buy Jira Service Management to keep paging after April 5, 2027. IncidentBot imports your Opsgenie schedules and escalation policies, pages the on-call engineer by push, SMS and voice, runs the incident in Slack and sends every postmortem action item to your Jira Cloud project as an issue. It costs 24 USD per responder a month on Starter and 49 USD on Team, billed annually.

People who only read incidents and status pages are free, so product managers and support leads in Jira do not need a seat.

Run a sample incident

Why Jira Software teams are stuck with the Opsgenie shutdown

Technician at a desk testing a page on a phone while rebuilding escalation rules

Atlassian stopped selling Opsgenie on June 4, 2025 and switches it off on April 5, 2027. Data that has not been migrated by then is deleted. The two paths Atlassian offers both assume a product you may not run today.

Teams that run engineering in Jira Software usually want three things from a replacement: the same rotations and escalations, issues landing in the Jira project they already use, and no new ITSM product to administer.

Jira Service Management is a service desk. Its alerting and on-call features are licensed per agent, and Atlassian's own page lists Standard at 21.50 USD and Premium at 55.28 USD per agent a month (monthly billing, October 2026), broken down in our Jira Service Management pricing guide. A 15 person rotation that never touches a customer ticket pays for a help desk anyway.
Compass is a developer portal. On-call schedules and alerts are on Standard at 7.67 USD per user, but escalation policies, voice notifications and heartbeats need Premium at 23.96 USD, and Compass is billed monthly only.
Neither path gives you a public status page or a Slack incident channel with roles, which is where most of the work in a real outage happens.

Who this page is for

Engineering managers who own the on-call rotation and the Opsgenie renewal.
Platform and SRE leads with 5 to 60 engineers on call and a Jira Cloud site for planning.
IT leaders who were told by Atlassian that the recommended plan is JSM, and who do not run a service desk.

From an Opsgenie alert to a Jira issue

Engineer checking a test notification on a phone during an on-call setup

Import: paste a read-only Opsgenie API key (US or EU instance). IncidentBot reads schedules with their layers, the overrides already on the calendar and the escalation policies, matches people by email and never stores the key.
Alerts: point Datadog, Prometheus Alertmanager, Grafana, CloudWatch, Sentry or any JSON webhook or email source at the service's alert address. The integrations that fed Opsgenie can send to IncidentBot instead.
Paging: the escalation policy pages the person on call by mobile push, SMS, voice call and email, and moves to the next tier when nobody acknowledges.
Incident: /incident in Slack or the web app opens a channel with a severity, a commander and a timeline that records every page and acknowledgement.
Jira: on Team and above, each action item from the incident or the postmortem is created as an issue in the Jira Cloud project you choose, with a link back to the incident. IncidentBot reads the issue status back, so the postmortem shows which follow-ups are done.

What carries over and what does not

Opsgenie	IncidentBot	Notes
Schedules, rotations, layers	Schedules with layers	Imported, overrides on the calendar included
Escalation policies	Escalation policies	Imported, tiers and timeouts kept
Teams and services	Services with owners	Created during setup, one alert address per service
Alert integrations	Native parsers, webhook and email intake	Re-pointed at the new address, no data loss
Heartbeats	Not a separate feature	Use your monitoring tool's no-data alert instead
Opsgenie phone number	Not transferable	Opsgenie numbers stay with Atlassian
Jira issue from an alert	Jira issue from an action item	Issues are created from incidents and postmortems, not from every alert
Incident status updates	Public and private status pages	1 public page on Starter, 3 public or private on Team

Jira sync works with Jira Cloud sites on atlassian.net. Jira Data Center and Server are not supported, so self-hosted Jira teams should read the Opsgenie alternative page for the general migration plan instead.

Opsgenie replacement cost for a 15 person rotation

Monthly cost for 15 engineers who can be on call. Opsgenie, Compass and IncidentBot prices are from the vendors' pricing pages, checked in October 2026. JSM is not priced per seat on Atlassian's site any more and is sold in the Service Collection bundle, so the figures are ranges reported by independent pricing trackers. Get a written quote before you compare.

Option	Price per user a month	15 users a month	What you still have to buy
Opsgenie Standard (renewal only, ends April 2027)	19.95 USD	299 USD	A replacement within 18 months
Compass Premium (monthly billing only)	23.96 USD	359 USD	Status page, Slack incident workflow
JSM Standard (reported)	about 20 to 25 USD	about 300 to 375 USD	Status page, a service desk you may not use
JSM Premium (reported)	about 51 to 57 USD	about 765 to 860 USD	Nothing major, but you administer an ITSM product
IncidentBot Starter	24 USD	360 USD	Jira sync and private pages need Team
IncidentBot Team	49 USD	735 USD	Nothing for paging, Slack incidents, status pages and Jira action items

Read the table honestly. If your team only needs paging and escalation, Compass Premium is the cheapest Atlassian path and keeps you on one vendor. IncidentBot Team costs more per seat than Compass and less than JSM Premium. It wins when you also pay for a status page (Atlassian Statuspage starts at 29 USD a month and Business is 399 USD) and an incident tool on top of the pager. The full Opsgenie plan list, renewal rules and the same math for 5 and 40 users are in our Opsgenie pricing guide.

See pricing

Move off Opsgenie in four weeks without a gap in paging

Running both tools in parallel for a week costs one extra month of seats and removes the risk of a silent night. Scheduling patterns that work for engineering teams are on the on call scheduling software page, and the paging rules are on incident alerting.

Week 1: create your account, import schedules and policies from Opsgenie, and ask every engineer to install the app and confirm a test page.
Week 2: connect Slack and your Jira Cloud project, then point one low-risk service's alerts at IncidentBot while Opsgenie still pages for it.
Week 3: compare which tool paged first and fix any routing gaps, then move the remaining services in groups.
Week 4: switch off the Opsgenie integrations, export what you want to keep from Opsgenie and close the renewal before April 5, 2027.

What Jira teams get that the Atlassian path leaves out

Teams comparing the other common switch can read PagerDuty vs Opsgenie, which prices PagerDuty for 10 and 40 responders.

One seat price for on-call, Slack incidents, status pages and postmortems, with viewers free.
Postmortem action items in the Jira project your team already plans in, with the status read back.
MTTA, MTTR and on-call load reports on Team, so the cost of nights on call is visible in the sprint review.
A published price for every plan, so a 15 person team can buy without a sales cycle.
No ITSM product to set up. A team that never used JSM does not have to learn request types and queues to keep its pager.

What is replacing Opsgenie?

Atlassian is moving Opsgenie's alerting and on-call features into Jira Service Management and Compass, and Opsgenie stops working on April 5, 2027. Teams that use Jira Software rather than a service desk often move to a standalone tool such as IncidentBot, PagerDuty or incident.io and keep Jira for planning.

Do I need Jira Service Management to keep on-call after Opsgenie?

No. Jira Service Management is one of two Atlassian paths, the other is Compass, and any third-party on-call tool works with Jira Software. IncidentBot imports Opsgenie schedules and escalation policies and creates postmortem action items as issues in your Jira Cloud project, with no JSM license.

Can I use Jira Software for on-call alerts?

Jira Software has no paging, schedules or escalation of its own. Atlassian moved those features to Jira Service Management and Compass. With a separate on-call tool, alerts page the engineer on duty and the follow-up work lands in Jira Software as issues.

Is Compass cheaper than Jira Service Management for on-call?

Usually yes. Compass Standard is 7.67 USD per user a month with schedules and alerts, and Premium is 23.96 USD with escalation policies and voice calls, both billed monthly. JSM is reported at about 20 to 25 USD per agent on Standard and 51 to 57 USD on Premium.

Does IncidentBot create Jira issues from alerts?

IncidentBot creates Jira issues from incident and postmortem action items on Team and above, not from every alert. That keeps noise out of your backlog. It works with Jira Cloud sites on atlassian.net and reads the issue status back into the postmortem.

Can I import my Opsgenie schedules?

Yes. Paste a read-only Opsgenie API key from the US or EU instance and IncidentBot imports schedules with their layers, overrides already on the calendar and escalation policies. People are matched by email. The key is used once and is not stored.

What happens to Opsgenie data after April 5, 2027?

Atlassian says access to Opsgenie is shut off on that date and any data not migrated to Jira Service Management or Compass is deleted. Export alert history and reports you need for audits before you cancel.

Keep Jira, replace the pager

Import your Opsgenie schedules, connect your Jira Cloud project and send a test page today.