# Opsgenie shutdown: what happens to your integrations, API and alert data

URL: https://rootly.com/on-call-software/opsgenie-shutdown-integrations-and-data
Pillar: On-Call Operations
Bundle: https://rootly.com/llms/on-call-software.txt

> What happens to Opsgenie REST APIs, monitoring and chat integrations, and alert history when Opsgenie is turned off, what to export first, and how to move Datadog and Prometheus alerts without a gap in paging.

**Opsgenie support ends on April 5, 2027. When Opsgenie is turned off, its configuration APIs stop answering, integrations that only work with Opsgenie stop, and its data can no longer be retrieved.** Teams that migrate to Jira Service Management lose Opsgenie automatically 120 days after their migration date, or sooner if an admin turns it off manually, and turning it off can't be undone. What has to happen first depends on where you go. If you migrate to Jira Service Management, reconnect chat, replace the integrations that don't migrate, and update anything that uses the configuration APIs. If you move to another platform, repoint every monitoring integration, update every script that calls the Opsgenie API, and export the alert and incident history you want to keep.

This guide covers what happens to each part of an Opsgenie setup, what changes for teams that migrate to Jira Service Management, what to export, and how to move Datadog and Prometheus alerts. [Rootly On-Call](https://rootly.com/on-call) imports Opsgenie users, schedules, teams and routing rules, and Rootly runs the migration for you.

## Key takeaways

- Teams that migrate to Jira Service Management lose Opsgenie 120 days after their migration date. Configuration APIs stop then; alert, heartbeat and integration event APIs keep working in Jira Service Management.
- Chat integrations, incoming call integrations on Opsgenie numbers and integrations past end of support don't carry over.
- Turning Opsgenie off is permanent: users can't log in or retrieve data. Export what you need before Opsgenie support ends on April 5, 2027, or before your own turn-off date if it comes first.
- Move monitoring integrations one team at a time, and keep the Opsgenie route until the team passes its paging checks and a full rotation.

## What happens to each part of Opsgenie

Based on Atlassian's [shutdown](https://support.atlassian.com/opsgenie/docs/what-happens-when-opsgenie-is-turned-off/) and [integration](https://support.atlassian.com/opsgenie/docs/integrations-after-migration/) documentation:

| Part of Opsgenie | What happens | What to do |
| --- | --- | --- |
| REST API and API keys | Configuration APIs stop when Opsgenie is turned off; teams migrated to Jira Service Management keep the alert, heartbeat and integration event APIs | Moving elsewhere: repoint every script, CI job and tool that calls the API. Moving to Jira Service Management: update anything that uses the configuration APIs |
| Monitoring integrations (Datadog, Prometheus, CloudWatch and others) | Integrations that only work with Opsgenie stop; integrations migrated to Jira Service Management keep working there | Moving elsewhere: repoint each source before shutdown. Moving to Jira Service Management: confirm each integration migrated and still delivers |
| Incoming call integrations using Opsgenie-provided numbers | Stop when Opsgenie is turned off | Set up voice alerting in the new platform |
| Chat integrations (Slack, Microsoft Teams) | Not migrated automatically to Jira Service Management | Reconnect chat in the new platform |
| Older integration versions, and Flowdock, HP Service Manager, Snyk and Jira Server (Beta) | Keep working in Opsgenie until it is turned off, with no new instances | Replace them before shutdown |
| Opsgenie actions, incident rules, deprecated notification policies | Permanently unavailable after shutdown | Rebuild what you still need as workflows in the new platform |
| Alert and incident history | Can't be retrieved after shutdown; only data migrated to Jira Service Management stays there | Export it through the REST API before shutdown |
| Users, teams, schedules, routing | Lost with Opsgenie unless migrated | Import them into the new platform |

## If you migrate to Jira Service Management

Atlassian's [shutdown](https://support.atlassian.com/opsgenie/docs/what-happens-when-opsgenie-is-turned-off/) and [integration](https://support.atlassian.com/opsgenie/docs/integrations-after-migration/) documentation sets out what changes for teams that move to Jira Service Management:

- **Turn-off date.** Opsgenie turns off automatically 120 days after your migration date, unless an admin turns it off manually first. Turning it off is permanent and can't be undone, and Opsgenie support ends on April 5, 2027 either way.
- **APIs.** Configuration REST APIs stop working when Opsgenie is turned off. Alert, heartbeat and integration event APIs keep working.
- **Integrations that keep working.** Most Opsgenie integrations are synced to Jira Service Management automatically, and existing `*.opsgenie.net` email integrations and migrated endpoints keep working after turn-off.
- **Integrations to reconnect or replace.** Chat integrations such as Slack and Microsoft Teams aren't migrated automatically: reconnect them, then copy the integrations over, which start switched off. Incoming call integrations that use Opsgenie-provided numbers stop. CA Flowdock (Inbox), HP Service Manager, Snyk and Jira Server (Beta) are past end of support and keep working only until Opsgenie is turned off. Existing PagerDuty Integration API, PingdomEmail, ZyrionEmail and FirebaseCrashlytics instances don't move.
- **Features left behind.** Opsgenie actions, incident rules and deprecated notification policies become permanently unavailable, so set up their replacements in Jira Service Management before turn-off.

## What to export before Opsgenie is turned off

Decide what you will need after the move, then pull it through the Opsgenie REST API while it still works:

- **Alert and incident history** for the period your audits, SLA reports and trend reviews cover.
- **Schedules and overrides**, including future overrides already agreed with responders.
- **Integration and routing configuration**, so you can check that every alert source has a new home.
- **Opsgenie actions and incident rules**, so you can rebuild the ones you still use.

If you move to Rootly, users, teams, routing rules, schedules with overrides, services and notification settings are imported for you, so the export is mainly history you want to keep for reference.

## Moving Datadog alerts

In Rootly, Datadog monitors send alerts through Datadog's Webhooks integration:

1. Create a Rootly webhook in Datadog with Rootly's webhook secret as a custom header.
2. Add `@webhook-<name>` to a pilot team's monitors, next to the existing Opsgenie handle, so both platforms receive alerts during the parallel run. Agree which system pages responders and takes acknowledgments: receiving the same alert in both doesn't share acknowledgment state.
3. Choose who gets paged: a user, a team, an escalation policy or a service, set in the webhook payload or with an alert workflow in Rootly.
4. Test notifications from Datadog and confirm the page arrives. Remove the Opsgenie handle only after the team passes its paging checks and a full on-call rotation.

By default Rootly pages for Datadog alerts in the CRITICAL state, so warnings are recorded without waking anyone. See the [Datadog integration](https://rootly.com/integrations/datadog).

## Moving Prometheus Alertmanager alerts

Rootly receives Prometheus alerts as an [Alertmanager alert source](https://docs.rootly.com/integrations/alertmanager):

1. In Rootly, add an Alertmanager alert source and copy its webhook URL and bearer token.
2. Add a Rootly receiver to `alertmanager.yml` with that URL and token, alongside the existing Opsgenie receiver, and route a pilot team's alerts to both during the parallel run, with one system agreed as the one responders acknowledge in.
3. Set `send_resolved: true` on the receiver. Rootly ingests firing alerts, resolves them automatically when Alertmanager sends a resolved notification, and can page on-call targets set by webhook URL or Prometheus rule annotations.
4. Remove the Opsgenie receiver only after the team passes its paging checks and a full on-call rotation.

For other tools, Rootly has native alert sources for many monitoring platforms and a [generic webhook alert source](https://docs.rootly.com/integrations/generic-webhook-alert-source/generic-webhook-alert-source) for the rest.

## Cutting over

Rootly's [Opsgenie migration](https://docs.rootly.com/switch/opsgenie-migration) imports users, teams, routing rules, schedules with overrides, services and notification settings with read-only Opsgenie API access, and the [Opsgenie integration](https://docs.rootly.com/integrations/opsgenie) lets incidents run in Rootly while paging stays in Opsgenie. For the parallel run, paging checks, go/no-go criteria and rollback, follow the cutover checklist in the [Opsgenie migration guide](https://rootly.com/blog/opsgenie-migration-to-rootly-complete-step-by-step-guide-for-a-smooth-transition-2026#how-to-validate-paging-and-cut-over-without-losing-coverage).

Rootly runs Opsgenie migrations for you, and a first incident runs in about 15 minutes with starter templates and defaults. For choosing a replacement, see [alternatives to your paging system](https://rootly.com/on-call-software/replace-paging-system) and [on-call tools](https://rootly.com/on-call-software/tools).

## Frequently asked questions

### What happens to Opsgenie API integrations after April 2027?

Opsgenie support ends on April 5, 2027. Once Opsgenie is turned off, Atlassian says its configuration REST APIs stop working and integrations that only work with Opsgenie stop. Teams that migrated to Jira Service Management keep the alert, heartbeat and integration event APIs there. If you are moving to another platform, update every script, webhook and tool that calls the Opsgenie API before Opsgenie is turned off, and point monitoring tools at your new on-call platform.

### What happens to our alert history and incident data when Opsgenie shuts down?

Once Opsgenie is turned off, users can't log in to Opsgenie or retrieve data from it, and Atlassian says turning it off is permanent and can't be undone. Opsgenie support ends on April 5, 2027. Only data migrated to Jira Service Management stays available there. If you are moving to another platform, export the alert and incident history you need for audits and trend reporting through the Opsgenie REST API before Opsgenie is turned off.

### How do we migrate Datadog and Prometheus alert integrations from Opsgenie?

Move one team at a time, and decide which system pages responders and takes acknowledgments while both receive alerts, because acknowledging in one doesn't stop an escalation in the other. In Rootly, Datadog monitors send alerts through a Datadog webhook referenced in the monitor message, and Prometheus Alertmanager sends alerts to a Rootly receiver in alertmanager.yml; with send_resolved set to true, resolved notifications close the Rootly alert automatically. Remove the Opsgenie routes only after the team passes its paging checks and a full on-call rotation. Opsgenie support ends on April 5, 2027, so finish the move before then.

### When does Opsgenie shut down if we migrate to Jira Service Management?

Atlassian turns Opsgenie off automatically 120 days after your migration date, unless an admin turns it off manually first. Opsgenie support ends on April 5, 2027. Chat integrations such as Slack and Microsoft Teams are not migrated automatically, and some outdated integration versions don't move to Jira Service Management.
