What Breaks When Opsgenie Shuts Down: An On-Call Cutover Checklist

A paging tool rarely fails loudly. When an alert path breaks during a migration, nothing throws an error. The phone simply does not ring, and a missing page looks exactly like a quiet night.

Atlassian stopped selling Opsgenie on June 4, 2025, and ends support on April 5, 2027. Teams that use Atlassian's migration tool lose it sooner: Atlassian says Opsgenie shuts down automatically 120 days after your migration date. Its migration documentation also lists Opsgenie configuration that does not carry over to Jira Service Management, plus features that carry over only on certain Jira plans.

Short answer: according to Atlassian's documentation, the pieces at risk are Opsgenie actions and incident rules, Slack and Microsoft Teams chat integrations, heartbeats with no assigned team, incoming call routing on Atlassian-provided numbers, Opsgenie single sign-on, older integrations such as Crashlytics, and any feature that needs a Premium or Enterprise Jira plan. Each one is an alert path to rebuild and test before Opsgenie shuts down.

To test a replacement while Opsgenie keeps running, start the JAMS Incident Management trial: 14 days, no credit card.

Or hear what a page sounds like first: anyone can trigger a sample alert call without signing up. Voice calls use US, UK, and Australian numbers.

Two Deadlines, and You Set One of Them

Atlassian documents two shutdown dates for Opsgenie.

April 5, 2027 is the hard stop. Atlassian says that on that date it shuts off access and deletes any data that was not migrated, and that renewals are allowed only for terms that end before then.

The earlier deadline applies to every team that uses Atlassian's migration tool. Atlassian states that Opsgenie shuts down automatically 120 days after your migration date, unless you turn it off sooner, and that the shutdown cannot be undone.

The same Atlassian page says users then cannot log in, the Opsgenie mobile app is deactivated, and remaining Opsgenie-based integrations stop working. The Opsgenie REST APIs keep working until April 5, 2027, and Atlassian recommends updating API endpoints before Opsgenie is turned off.

That makes your scheduled migration date the real planning date. Choose it after your replacement has paged a real person.

What the Migration Tool Leaves Behind

Atlassian says its migration tool syncs users and roles, and that alerts, on-call schedules, and escalation policies remain available in Jira Service Management. Atlassian also documents these exceptions.

Check heartbeats first. A lost heartbeat hides exactly the outages it was set up to catch.

What Depends on Your Jira Plan

Atlassian's migration documentation lists Opsgenie capabilities that carry over only on Jira Service Management Premium or Enterprise:

• Heartbeat monitoring is not available on the Free and Standard plans, and Atlassian caps a site at 2,000 heartbeats.

• Bidirectional integrations require Premium or Enterprise, and Atlassian notes that teams moving to Free and Standard may lose the outgoing part of their integrations.

• Global custom roles and role-based notifications are not available on Free and Standard.

Atlassian also states that the migration tool supports only Jira Service Management Cloud, not Data Center.

Before you schedule a migration date, list every heartbeat, two-way integration, and role-based notification you use today. Then check each one against the plan you will land on.

The Cutover Checklist

Every alert path that pages someone today should still page someone on the day Opsgenie shuts down. These steps work whether the destination is Jira Service Management or a different tool.

• Inventory the configuration. List every integration, heartbeat, action, incident rule, chat integration, and incoming call routing number in Opsgenie. Note the team that owns each heartbeat, since Atlassian's documentation says a heartbeat with no team will not move.

• Inventory the sources. For each monitoring tool, scheduler, and ITSM system, record how it sends alerts (an API key, an email address, or a webhook URL) and who can change that setting.

• Check the destination plan. Compare the inventory with the plan you will land on, using the plan-dependent items under "What Depends on Your Jira Plan." Anything that needs Premium or Enterprise needs a decision now, not after the move.

• Rebuild the highest-severity path first. Set up its on-call schedule and escalation policy in the new tool, and connect the one source that matters most.

• Fire a real alert and let it escalate. Have the first responder ignore it on purpose. Confirm the page reaches the second responder by phone. If your destination supports two-way updates, confirm that an acknowledgment from the phone updates the source system.

• Run both tools side by side for a week. Point a copy of those alerts at the new tool while Opsgenie keeps paging. Compare what each one delivered.

• Move the remaining sources one at a time. Test each path the same way before you move the next.

• Set the migration date last. Schedule it, or turn Opsgenie off, only after every path has paged a real person. Then update any scripts or integrations that still point to Opsgenie endpoints.

Where JAMS Incident Management Fits

If your service desk already runs on Jira Service Management, migrating there may be the shortest path. Teams that want on-call alerting without a service-management suite have other options, and JAMS Incident Management is one of them. "We built JAMS Incident Management for people like us," said Peter Hegland, chief executive officer of JAMS Software, in the launch announcement.

It pages the right person by voice, SMS, WhatsApp, push, email, Microsoft Teams, or Slack until they acknowledge. It works without JAMS Scheduler. Alerts arrive by email or through each flow's own webhook URL, and an API monitor can check an endpoint on a schedule and fire when the response matches a condition. On Professional and up, Azure Monitor, ServiceNow, and Zendesk connect both ways, so an acknowledgment in JAMS Incident Management updates the source. Professional also adds a Jira integration. When a JAMS Scheduler job fails, responders can acknowledge, restart the job, or continue or cancel its sequence from the alert.

Know these limits before a trial. Voice and SMS use numbers in the United States, the United Kingdom, and Australia, with other regions on request. The Free plan covers up to five users with one flow, one on-call schedule, 5 SMS or WhatsApp messages per user per month, no voice calls, and no escalation policies. A parallel run with real escalation therefore uses Starter, which is $6 per user a month billed annually and adds voice calling and escalation policies.

The 14-day trial includes every feature, 50 messages, and 10 voice calls, with no credit card. Rebuild your highest-severity escalation policy, send one real page through it, and pick your migration date after that.

Frequently Asked Questions

When Does Opsgenie Stop Working?

Atlassian ends Opsgenie support on April 5, 2027. On that date access is shut off and data that was not migrated is deleted. Teams that use Atlassian's migration tool lose Opsgenie earlier, because it shuts down automatically 120 days after the migration date unless the team turns it off sooner.

When Does the 120-Day Countdown Start?

Atlassian counts the 120 days from your migration date. Opsgenie then shuts down automatically unless you turn it off sooner, and the shutdown cannot be undone. Set the date after your replacement has been tested.

What Does the Opsgenie Migration Tool Not Move?

Atlassian documents that Opsgenie actions, incident rules, and heartbeats with no assigned team do not move, and that Slack and Microsoft Teams chat integrations must be reconnected by hand. Incoming call routing on Atlassian-provided numbers is disabled when the merge completes.

Do I Need a Premium Jira Service Management Plan to Keep Heartbeats?

According to Atlassian, yes. Heartbeat monitoring is not available on Free or Standard, and bidirectional integrations require Premium or Enterprise. Teams moving to Free or Standard may also lose the outgoing part of their integrations, so check each heartbeat and two-way integration against your destination plan.

How Do I Test a Replacement Before Opsgenie Shuts Down?

Rebuild your highest-severity on-call schedule and escalation policy in the new tool, connect its most important alert source, and fire a real alert. Let the first responder ignore it so the escalation reaches the second person by phone. Then run both tools side by side for a week before you set a migration date.

Sources

• Atlassian, What happens when Opsgenie is turned off?

• Atlassian, Evolution of IT operations

• Atlassian, Opsgenie licensing

• Atlassian, Start moving from Opsgenie to Jira Service Management

• Atlassian, Understanding Opsgenie integration changes

• Atlassian, Integrations after migration

• Atlassian, Merge Opsgenie with Jira Service Management

• Atlassian, Advanced alert configurations after migration

• Atlassian, How Opsgenie features change after migration

• Atlassian, Schedule an Opsgenie migration