# Opsgenie End of Life: What to Export and Decide Before April 5, 2027

> Opsgenie is shutting down. Here's how to back up schedules, escalations and alert history and pick a successor before the deadline.

Source: https://uptimeify.io/blog/opsgenie-end-of-life-migration

**Atlassian shuts Opsgenie down on April 5, 2027, and everything that hasn't been migrated to Jira Service Management (JSM) by then is deleted.** You have two routes: Atlassian's built-in move to JSM with 120 days of parallel access, or a switch to another tool. Either way, back up your schedules, escalations, integrations and alert history first, because JSM doesn't carry everything over and, depending on the plan, keeps data for a shorter time.

- **Deadline:** On April 5, 2027 Opsgenie goes offline, and unmigrated data is deleted.
- **Route 1, JSM:** You start the move in the product under Settings, Plan your move, with 120 days of parallel access. For the full 120 days, set the date by December 6, 2026.
- **What's missing:** Incident rules, Opsgenie actions, chat integrations and several reports don't carry over. MSP sub-accounts become free accounts.
- **Route 2, another tool:** Back up data via API and Terraform, rebuild the configuration, run both in parallel, switch before the deadline.

## When does Opsgenie shut down?

Opsgenie shuts down on **April 5, 2027**. Atlassian announced the end on March 4, 2025 and stopped sales on June 4, 2025. Since then there are no new customers, no plan changes and no additional sites.

| Date | What happens |
| --- | --- |
| March 4, 2025 | Atlassian announces the end of Opsgenie. |
| June 4, 2025 | End of sale: no new purchases, no upgrades or downgrades. |
| until April 5, 2027 | Existing contracts continue. Renewals work if the term ends before the deadline. Extra seats can still be bought. |
| Migration date plus 120 days | After the move to JSM, Opsgenie turns itself off automatically. |
| April 5, 2027 | End: no more access, unmigrated data is deleted. The Opsgenie app is shut down too. |

Source: atlassian.com/licensing/opsgenie and support.atlassian.com, retrieved November 12, 2026.

You pick your migration date yourself, at least seven days ahead and no later than April 5, 2027. That leads to a calculation many teams miss: if you move in March, you won't get 120 days of parallel access, because April 5 is the end for everyone. For the full period, your date has to be set by **December 6, 2026**.

April 5, 2027 is the end, not your migration date. If you move to JSM and want 120 days to test, plan for December 6, 2026.

## What does Atlassian carry over to Jira Service Management?

When you move to JSM, Atlassian syncs most of your Opsgenie configuration automatically: alerts, teams and users, all schedules and escalations, routing rules, notification rules, incoming integrations, heartbeats, incidents and post-incident reviews. Alerts stay in sync across both products until Opsgenie is turned off.

Which features you keep depends on the JSM plan. Atlassian recommends:

| Your Opsgenie plan | Recommended JSM plan |
| --- | --- |
| Free | JSM Free or any paid plan |
| Essentials | JSM Standard |
| Standard | JSM Premium |
| Enterprise | JSM Premium or Enterprise |

In JSM, heartbeats, global integrations, roles, stakeholders, analytics and voice calls are limited to Premium and Enterprise. Atlassian shows the price for your recommended plan only inside the product under **Settings, Plan your move**.

Check your retention needs too: JSM keeps alert data for one month on Free, one year on Standard, three years on Premium and five years on Enterprise. Opsgenie Enterprise kept it indefinitely. Atlassian itself advises exporting critical alert data before you migrate.

Older Atlassian pages also listed Compass as a destination for developer teams. The current migration pages only mention Jira Service Management (as of November 12, 2026).

## What do you lose when you move to JSM?

Some Opsgenie features don't make the move and have to be rebuilt or disappear:

| Opsgenie | What happens on migration |
| --- | --- |
| Incident rules, Opsgenie actions | Not carried over, rebuild them as Jira Automation. |
| Slack, Teams, Zoom | Reconnect chat integrations. |
| Incident Command Center, response roles, incident templates | Removed or replaced by incident configurations. |
| MSP sub-accounts | Become free accounts with their own migration path. |
| Opsgenie app | Shut down, recreate notification rules in the Jira app. |
| Reports such as postmortem, service health, API usage | Removed, historical data from these reports isn't migrated. |
| API keys | Replaced by Atlassian authentication, scripts need updating. |
| Your own numbers for incoming call routing | Must be ported to Twilio first. |

Source: support.atlassian.com, Feature changes and deprecations, retrieved November 12, 2026.

For agencies and MSPs, the sub-account row matters most: if you run client accounts as MSP sub-accounts in Opsgenie, each one needs its own plan.

## Which data should you export before April 5, 2027?

Export everything you need for evidence, reporting or rebuilding, no matter where you're headed. Atlassian has no official backup checklist for leaving its platform, but the Opsgenie REST API covers all key data with read endpoints:

| Data | Endpoint | Note |
| --- | --- | --- |
| Schedules | `GET /v2/schedules` and `/v2/schedules/{id}.ics` | also exportable as a calendar file |
| Rotations and overrides | `GET /v2/schedules/{id}/rotations`, `/overrides` | |
| Escalations | `GET /v2/escalations` | |
| Teams and routing rules | `GET /v2/teams`, `/v2/teams/{id}/routing-rules` | |
| Users and contact methods | `GET /v2/users`, `/v2/users/{id}/contacts`, `/notification-rules` | |
| Integrations | `GET /v2/integrations` | |
| Heartbeats | `GET /v2/heartbeats` | |
| Alerts | `GET /v2/alerts` plus `/logs` and `/notes` per alert | max. 20,000 per query window |
| Incidents | `GET /v1/incidents` plus `/logs` and `/notes` | |
| Activity logs | `GET /v2/logs/list/{marker}` | Enterprise plan only |

EU accounts use the base URL `https://api.eu.opsgenie.com`, all others `https://api.opsgenie.com`.

If you already manage Opsgenie with Terraform, you're ahead: the `opsgenie/opsgenie` provider (version 0.6.40) can pull existing teams, schedules, escalations, users and heartbeats into state with `terraform import`. Overrides have no resource, so get them through the API. Report dashboards can be downloaded as PDF or CSV in the interface.

Before you move, back up at least your schedules as .ics, escalations, routing rules, integrations and the alert history you need as evidence.

## JSM or another tool: how do you decide?

Moving to JSM is the shortest path if your team already works in Jira. Atlassian carries the configuration over automatically, and you get 120 days to test in parallel. That's a real advantage.

Another tool is worth the effort if one of these applies to you:

- **You don't otherwise use Jira.** With JSM you'd be buying a service desk platform just to deliver alerts.
- **The recommended JSM plan costs more than your Opsgenie plan.** Check under Settings, Plan your move before you commit.
- **You serve clients as an MSP.** Sub-accounts get set up from scratch anyway, so you're rebuilding either way.
- **You want monitoring and alerting in one place.** Many teams run a monitoring tool that reports into Opsgenie. The migration is the moment to consolidate.
- **Where your incident data lives matters.** Alerts contain names, phone numbers and outage details. Check the subprocessor list to see which providers can access that data and where they're based.

Whatever you choose, treat the migration as a project with a date, not a task for March.

## How does a switch to another tool work?

Leaving Atlassian breaks down into five steps:

1. **Take inventory.** List all teams, schedules, escalations, integrations and heartbeats. Mark what you still need. A migration is the best chance to drop orphaned rules.
2. **Back up the data.** Export configuration and history through the API, schedules additionally as .ics. Store the alert history where you'll find it again for audits.
3. **Build the target, ideally as code.** Create teams, schedules and escalation chains in the new tool. If you use Terraform, translate the Opsgenie resources into the new vendor's provider. There's no automatic converter, but the structure is very similar.
4. **Run both in parallel.** Point your alert sources at the new tool and keep Opsgenie running for a few weeks. Check that every alert reaches the right person, including at night and on weekends.
5. **Switch over and clean up.** Cancel Opsgenie at the end of your term, remove old integrations and walk your team through the new app and contact methods.

Allow at least two full rotation cycles for step 4. Only then will you see whether handovers, overrides and escalations really hold.

## What does a move to Uptimeify look like?

Uptimeify is a white-label monitoring platform with built-in incident management for your team. Your own checks are an alert source out of the box: a confirmed outage becomes an incident for whoever is on call.

Here's how the five steps work with Uptimeify:

- **Switch your alert sources.** There are presets for Zabbix, Datadog, Grafana, Prometheus Alertmanager, Sentry and Beszel. Anything else connects through a webhook with your own mapping, by email or through the events API. There's no Opsgenie-compatible endpoint, so you move sources one by one.
- **Rebuild schedules and escalation.** Rotations with time zones, overrides and multi-step escalation with repeats. A dry run shows who would be paged when and on which channel, without sending anything. On-call schedules, overrides, and acknowledgement and timeline are currently in beta.
- **Test in parallel.** Uptimeify can forward incidents to Opsgenie as an outbound integration. Your old setup keeps running during the test phase, and you turn it off once everything holds.
- **Manage it as code.** The Terraform and OpenTofu provider `uptimeify/uptimeify` manages teams, schedules, escalation tiers, alert sources and routing rules.
- **Replace heartbeats.** Monitor cron jobs and backups with heartbeat monitoring right inside your monitoring.

Uptimeify currently has no automatic Opsgenie import, so archive your Opsgenie alert history yourself as described above.

Hosted in the EU, with no US subprocessors for your incident data. SMS and calls go through German providers. Only the optional in-app push technically runs through Apple and Google, encrypted: they carry a block they can't read. If you're subject to reporting duties, you get NIS2-ready exports for incidents, and you file the report.

See how schedules, overrides and escalation chains work together in Uptimeify.

For more on escalation logic, read our post on [escalation policies and on-call routing](/blog/escalation-on-call-routing), and for heartbeats, [monitoring cron jobs and backups](/blog/monitoring-cron-jobs-and-backups). Why data location matters is covered in [monitoring without US sub-processors](/blog/monitoring-without-us-subprocessors). Terms like [on-call](/resources/platform-and-support/glossary/on-call) and [escalation policy](/resources/platform-and-support/glossary/escalation-policy) are in the glossary.

## What should you do this week?

Open **Settings, Plan your move** in Opsgenie and note the recommended JSM plan and its price. Export your schedules as .ics and pull a list of your integrations. With those three things you can decide whether to move to JSM or switch, and still have enough time for a real parallel run.
