Opsgenie is shutting down: what happens to your DORA metrics?
Atlassian is sunsetting Opsgenie on April 5, 2027. Here's what engineering teams need to do now to preserve MTTR data, escalation policies, and on-call schedules — and how Koalr's migration wizard makes it painless.
Opsgenie end-of-life: April 5, 2027
Atlassian has officially announced Opsgenie will be shut down and fully deprecated. All Opsgenie data will be deleted on this date. Teams should begin migration now.
What Opsgenie shutting down means for engineering teams
For thousands of engineering teams, Opsgenie has been the backbone of on-call management for years. Rotation schedules, escalation policies, alert routing rules, runbook links, and years of incident history — all of it lives in Opsgenie. Starting April 5, 2027, all of that is gone unless you act.
Atlassian's decision to consolidate around Jira Service Management for IT and Jira Ops for developers means Opsgenie customers must choose: migrate to incident.io, PagerDuty, or Atlassian's own Jira-native incident management. Each path has different implications for your DORA metrics tracking.
Your MTTR data is at risk
Mean Time to Recovery (MTTR) is one of the four core DORA metrics, and it requires historical incident data to calculate meaningfully. If you're tracking DORA today using Opsgenie as your incident source, losing that history means losing the ability to show improvement trends — precisely the narrative most engineering leaders use to justify investment in reliability practices.
Platforms like Koalr pull incident data from Opsgenie to calculate MTTR, MTTD (mean time to detect), and on-call load metrics. When Opsgenie shuts down, those data streams end. Teams that don't migrate and preserve their incident history will effectively start from zero on their DORA MTTR charts.
Beyond MTTR, on-call rotation data matters for measuring alert fatigue, after-hours load distribution, and responder burnout — all metrics that affect both reliability and retention.
The migration path: incident.io or PagerDuty
There are two clear winners for Opsgenie migrations, each with a different profile:
incident.io is the modern choice. Purpose-built for software engineering teams with Slack-native incident declaration, timeline reconstruction, and postmortem tooling that no legacy vendor can match. incident.io has native API export tooling for Opsgenie rotation and escalation policy migration. If your team is on Slack and uses GitHub, incident.io is the natural fit.
PagerDuty is the established enterprise choice. With a decade of market presence and the most extensive integration library in the space, PagerDuty is the safe bet for teams with complex multi-region escalation hierarchies and compliance requirements. PagerDuty also offers a formal Opsgenie migration program.
What neither migration tool does: automatically reconnect your historical incident data to the metrics platform you use for engineering analytics. That's the gap Koalr fills.
How Koalr's migration wizard works
Koalr has built a first-party Opsgenie Migration Wizard, available in Settings for all customers. Here is what it does:
- Export and archive your Opsgenie incident history — pull the last 24 months of incidents, alert timelines, and acknowledgment data into Koalr's platform before the shutdown date.
- Map your escalation policies — Koalr reads your current Opsgenie schedules and escalation chains, and generates a migration manifest you can import into either incident.io or PagerDuty with one click.
- Reconnect to your new incident platform — after migration, Koalr automatically re-wires your MTTR and on-call metrics to pull from incident.io or PagerDuty, with no gap in your trend data.
The result: your engineering leadership dashboard shows uninterrupted MTTR trends through the migration. No data loss, no chart gaps, no awkward explanations to the CTO about why reliability metrics disappeared for a month.
Start your migration now
April 2027 sounds far away. It is not. Complex on-call configurations with hundreds of escalation policies, multiple team rotations, and years of incident history take time to validate after migration. Teams that start in Q3 2026 will have time to run both systems in parallel, validate alert routing, and confirm their DORA metrics are intact before the shutdown.
Teams that wait until Q1 2027 will be doing emergency migrations during a high-risk window — exactly the scenario Koalr's deploy risk model flags as dangerous.
Start your Opsgenie migration — free for all Koalr customers
The migration wizard is available now in Settings. Connect your Opsgenie account, archive your incident history, and generate your migration manifest in under 10 minutes.