Opsgenie alternative and Opsgenie replacement for teams migrating before 2027

Atlassian stopped selling Opsgenie to new customers on June 4, 2025, and Opsgenie support ends on April 5, 2027, after which unmigrated data is deleted. Atlassian is moving customers to Jira Service Management and Compass. If your team uses Opsgenie for on-call and alerting, you now choose between the Atlassian path and a different tool. This page explains how a move to IncidentBot works, what carries over, and how to run it without a gap in paging.

Run a sample incident

Three ways forward from Opsgenie

Every team migrating off Opsgenie ends up in one of three places, and each is a reasonable choice for somebody.

IncidentBot is the third option. If your team also evaluated Splunk On-Call as a replacement, the Splunk On-Call alternative page compares it side by side, and teams that also shortlisted the German vendor ilert can read the ilert alternative comparison. If you are weighing all three, our guide to the best incident management software lists the criteria that separate them.

Jira Service Management: a good fit if your incident process is part of a service desk, with requests, change management and an asset database.
Compass: a good fit if you want a developer portal and component catalog from Atlassian with on-call attached.
A dedicated incident management tool: a good fit if what you used Opsgenie for is alerting, on-call and escalation, and you want coordination, status pages and postmortems in the same place.

From Opsgenie concepts to IncidentBot

The building blocks of on-call are the same everywhere. This is how they map.

In Opsgenie	In IncidentBot
Teams	Teams, with members, services and owners
Schedules and rotations	On call scheduling: rotations, overrides, swaps, follow-the-sun, calendar sync
Escalation policies	Escalation policies with tiers, timeouts and repeats
Integrations	Alert sources: Datadog, Prometheus Alertmanager, Grafana, CloudWatch, Sentry, email, webhook
Alert rules and deduplication	Routing, grouping, deduplication and maintenance windows
Notification rules	Personal paging preferences: push, SMS, voice, email, Slack

What you gain on top: /incident in Slack with a dedicated channel and roles, a hosted status page in every plan, and postmortem drafts built from the captured timeline.

Opsgenie migration in five steps

The order below keeps paging safe at every point, because the old tool keeps working until the last step.

On Enterprise, onboarding and migration are done together with your dedicated success manager. The general setup is described on how it works.

Export: take your teams, schedules, escalation policies and integration list out of Opsgenie while you still have full access.
Import schedules and escalation policies: IncidentBot imports them from Opsgenie, including overrides that are already on the calendar. Each engineer checks their own shifts and paging preferences before anything goes live.
Re-point integrations: add IncidentBot as the destination in each monitoring tool, service by service, starting with the least critical.
Run in parallel: both tools receive the same alerts for a period you choose. Compare who was paged and when. Differences are usually a timeout or a rotation hand-off time, and they are fixed before cut-over.
Cut over: remove Opsgenie as a destination per service once the parallel run matches, then retire the old schedules.

Plan the move before it is forced

Migrating on-call is safest when nobody is in a hurry. Leave room for the parallel run, avoid cutting over during a release freeze or a holiday rotation, and make sure every engineer has installed the mobile app and confirmed a test page before the old tool stops. A calm migration takes a few weeks of calendar time and very little effort per week.

What the switch costs

IncidentBot is priced per responder seat, monthly or annually, and every plan includes a status page. Stakeholders who only follow incidents are read-only viewers, included and not billed, so you do not pay for the support team that watches the channel. Starter covers small teams starting on-call, Team adds unlimited schedules and escalation policies with unlimited SMS and voice paging (fair use), and Enterprise adds migration support. See the pricing page for the numbers, and our Opsgenie pricing per user breakdown for what your current plan, Compass and Jira Service Management cost for 5, 15 and 40 users.

Can IncidentBot import directly from Opsgenie?

Yes. Schedules and escalation policies import from Opsgenie. Integrations are re-pointed in each monitoring tool, which also gives you a clean list of what actually sends alerts.

Do our alerts keep the same routing?

Routing rules are recreated per service, with grouping and deduplication on Team and above. The parallel run is where you confirm that routing matches.

Is there a period where nobody gets paged?

No, if you follow the steps. Opsgenie keeps paging until you remove it per service, and IncidentBot is already paging by then.

We use Jira. Do we lose that link?

No. Postmortem action items sync to Jira and Linear on Team and above.

Can we see it working first?

Yes. The incident simulator runs a sample incident in your browser: an alert from a monitoring tool, escalation through your policy, a Slack channel, a status page draft and a postmortem skeleton.

Start the migration while Opsgenie still runs

Create your account, import your schedules and run both side by side.