Skip to content
IncidentBot

Opsgenie shutdown on April 5 2027 and the migration plan for your on-call team

Opsgenie shuts down on April 5, 2027. Atlassian stopped selling it on June 4, 2025, existing contracts run to their term or to the end of support date, whichever comes first, and any data not moved by April 5 is deleted. If your team pages through Opsgenie today, you need a replacement live and tested before that date, with schedules, escalation policies and integrations recreated.

This page gives the dates as Atlassian states them, the three routes teams actually take, a month by month plan counted back from April 5 and the monthly cost of each route for 10 and 25 responders. It is written for the person who owns the rota and the renewal, not for a general reader.

What is the Opsgenie shutdown date and what happens before it?

Atlassian's Opsgenie migration page lists three milestones. The dates below come from that page and the Opsgenie support notice, checked in November 2026.

DateWhat happens
June 4, 2025End of sale. No new Opsgenie customers, and existing customers can no longer change edition (for example Essentials to Standard).
Until your term endsYour current subscription is honored for its remaining term, or until end of support, whichever is earlier.
April 5, 2027End of support. Opsgenie is switched off, the product is no longer accessible and data that has not been moved is deleted.

Atlassian says you can still download your Opsgenie data directly if you decide not to move it, but alert routing, on-call notifications and integrations stop. For a rota that wakes people up, that is the part that matters. Read the official Atlassian migration notice and check the exact end date on your own contract, because a renewal signed in 2026 may end earlier than April 5.

What stops working on April 5?

Everything that runs through Opsgenie: alert intake from monitoring tools, schedules and overrides, escalation policies, mobile push, SMS and voice, heartbeat monitoring and the Slack or Teams actions your responders use. Calendars you exported keep existing, but nothing pages anyone. Teams that find this out on April 6 learn it from a missed alert, so treat April 5 as the day the new tool must already be carrying real traffic.

Your three options after Opsgenie

On-call engineers reviewing an escalation plan together at a shared desk

Move to Jira Service Management. Atlassian's own path. Opsgenie capabilities are merged into Jira Service Management, and a migration assistant under Settings and "Plan your move" copies teams, schedules and policies. It suits teams that already run their service desk in Jira and want one vendor and one invoice. Premium, which holds the AIOps features, is about 55 USD per agent a month on the monthly toggle, and Standard about 21.50 USD. Our Jira Service Management pricing post breaks down what each tier includes.

Move to an independent on-call tool. PagerDuty, ilert, Zenduty, Squadcast, Spike and others import Opsgenie schedules or offer a migration helper. You buy only what you use, and you are no longer tied to Atlassian's roadmap. The tradeoff is rebuilding integrations and training the team once more. Our Opsgenie alternative page compares the options and lists what each import covers.

Move to a tool that adds the incident workflow. IncidentBot pages the right engineer, runs the incident in a Slack channel with roles, publishes the status page and drafts the postmortem. It imports schedules and escalation policies, and read-only viewers are free. This route fits teams that used Opsgenie only for paging and now want the response process in the same tool. Teams on Jira can still keep tickets there, see the Opsgenie replacement for Jira teams.

Honest limit: IncidentBot has no live call routing and no native mobile app (it installs as a web app with push), so a rota that depends on a phone tree should look at PagerDuty or OnPage first.

A month by month migration plan before April 5, 2027

Count backward from the shutdown date. Four months is enough for a team of 10 to 40, but it is not enough if you leave the decision to March.

  • November and December 2026. Decide and inventory. Export the list of teams, schedules, escalation policies, routing rules, integrations and heartbeats. Check your contract end date. Pick the route and take a trial.
  • January 2027. Rebuild and run in parallel. Recreate schedules and escalation policies in the new tool, point a second webhook from your monitoring at it and let both tools receive the same alerts for two weeks. Compare who was paged and how fast.
  • February 2027. Move the real rota. Make the new tool the primary for one team, then the rest. Keep Opsgenie as the fallback until each team has had at least one real page in the new tool.
  • March 2027. Cut over and clean up. Remove Opsgenie webhooks from monitoring, export historical alert data you want to keep and cancel the renewal.
  • Before April 5. Confirm. Send a test alert at 3 a.m. local time to the new tool and make sure it reaches the on-call person.

Put the integration inventory first. The most common slip is a forgotten webhook from a backup job or a certificate monitor that quietly stops paging.

What does replacing Opsgenie cost for 10 and 25 responders?

Monthly cost at list prices with every responder on a seat, annual billing where the vendor lists it. Opsgenie is shown for reference because you can no longer buy it.

Route10 responders25 respondersIncludes
Opsgenie Standard (reference)199.50 USD498.75 USDAlerting, schedules, escalation
Jira Service Management Standard215 USD537.50 USDService desk plus alerts and on-call
Jira Service Management Premium552.80 USD1,382 USDAdds AIOps and advanced incident features
IncidentBot Starter240 USD600 USDPaging, 3 schedules, Slack channel, 1 status page
IncidentBot Team490 USD1,225 USDUnlimited schedules, 3 status pages, postmortem drafts, Jira sync

Jira prices use the monthly toggle on Atlassian's pricing page, checked in October 2026, and Atlassian says annual billing saves up to 17 percent. A like for like swap from Opsgenie Standard costs about 8 percent more on Jira Standard and 20 percent more on IncidentBot Starter. What you get for that is the thing Opsgenie never included, a status page and an incident channel, so check what you pay for those today before comparing. The full IncidentBot price list is on the pricing page.

Worked example of a 12 person team

A 12 engineer team pays 239.40 USD a month on Opsgenie Standard. On IncidentBot Team with 12 responders on annual billing it is 588 USD a month, and support, success and leadership follow incidents as free viewers. If the team also pays 79 USD for a separate status page tool, the real gap is closer to 270 USD than 350 USD, and the status page, channel roles and postmortem draft come in the same bill.

What to move so nothing pages into a void

  • Schedules, including recurring overrides and holiday cover.
  • Escalation policies with their timeouts and the order of notification methods.
  • Routing rules that send alerts to different teams by tag or priority.
  • Every integration URL in monitoring, CI and cloud tools, not only the main ones.
  • Heartbeats for cron jobs and backups.
  • Mobile app logins and notification rules for each person, since they must be set again in the new tool.
  • Reports you use in reviews. Export them before the data is deleted.

When does Opsgenie shut down?

Opsgenie is shut down on April 5, 2027, according to Atlassian. End of sale was June 4, 2025. After April 5 the product is not accessible and data that was not moved is deleted, so alerting and on-call schedules need a replacement live before that date.

Can I still buy Opsgenie?

No. Atlassian ended sales on June 4, 2025, and existing customers can no longer upgrade or downgrade their edition. Current subscriptions are honored for their term or until end of support, whichever comes first, so check the end date on your contract.

Do I have to move to Jira Service Management?

No. Jira Service Management is Atlassian's suggested route and it has a migration assistant, but you can move to any on-call tool. Teams that do not use a Jira service desk often pick an independent product to avoid paying for the full suite.

How long does an Opsgenie migration take?

A team of 10 to 40 people needs two to four weeks of hands on work, plus two weeks of running the old and new tool in parallel. Plan four months in total counted back from April 5, so the decision falls before the end of 2026.

What happens to my Opsgenie data after April 5?

Data that has not been moved is deleted. Atlassian says you can still download your Opsgenie data directly. Export schedules, policies, alert history and reports before the shutdown if you want to keep them.

Move your Opsgenie rota before the April deadline

Create your account, import the schedules and escalation policies and send a test page to the engineer on call today.

See pricing

More guides

Incident response automation tools compared by what they automate and what they cost

the five steps worth automating, a minute by minute SEV2 example and the monthly cost of seven tools for 10 responders.

PagerDuty vs Datadog On-Call pricing and cost per responder for 5, 15 and 40 people

seat rules, the bundle trap and where a status page changes the bill

Splunk On-Call vs PagerDuty pricing and cost per responder for on-call teams

5 USD a seat up to 10 users against 21 USD Professional, the seat 11 cliff worked through and the monthly bill for 5, 15 and 40 responders