Opsgenie End of Support in April 2027: Migration Options for On-Call Teams

13 min read
Mitch Radhuber

by Mitch Radhuber

Engineer checking a phone alert in a dark room

Opsgenie customers should evaluate Jira Service Management, Atlassian’s current migration destination, or assess external platforms against their operational requirements. By April 5, 2027, Opsgenie will reach end of support and shut down: product access ends and unmigrated customer data will be deleted. This guide covers destination selection and migration validation, then explains where Corelayer can add an optional AI investigation layer alongside your new paging platform. Corelayer does not replace paging or on-call scheduling.

What Does an Opsgenie Migration Need to Replace?

An Opsgenie migration must preserve operational continuity: alerts must reach the right engineers through on-call schedules, escalation policies, notification channels, and integrations. Corelayer complements these primitives as an AI investigation platform, not a paging or scheduling destination. We reason across code, databases, deployments, and observability to investigate production issues for internal engineering teams in complex, regulated environments, not customer support or a help desk.

Define configuration migration and historical preservation as separate workstreams. Inventory teams, schedules, escalation rules, integrations, API dependencies, and Terraform configuration. Separately, identify required incident records and audit evidence, then verify what remains accessible before disabling Opsgenie. Atlassian states that only migrated data remains available in Jira Service Management after shutdown, and leftover Opsgenie integrations stop working. Do not assume configuration migration preserves every historical record.

Choosing the paging destination to maintain alert delivery and escalation workflows is separate from evaluating investigation capabilities. Keeping those decisions distinct prevents optional AI improvements from obscuring migration acceptance checks. Validate acknowledgement, escalation, and recovery workflows in the destination before treating the migration as complete.

Why Opsgenie Migration Planning Matters Before April 2027

As of the October 23, 2026 research context, Opsgenie has passed its June 4, 2025 end-of-sale milestone. New purchases, edition upgrades and downgrades, and additional Opsgenie sites are no longer available. Existing customers can purchase additional seats until April 5, 2027, but that does not extend the service’s operating life.

April 5, 2027 is a shutdown deadline, not merely the end of technical assistance. Opsgenie will become inaccessible, and customer data that has not been migrated will be deleted. Plan backward from that date, allowing time for procurement, configuration work, and validation of the replacement.

Atlassian requires scheduling the migration date at least seven days ahead; this scheduling is not a substitute for preparation or testing. We recommend completing migration with a buffer before April 5, 2027, rather than targeting the deadline itself. This buffer is editorial planning guidance, not an Atlassian guarantee.

The migration-specific shutdown window is separate. Atlassian says Opsgenie will automatically shut down 120 days after the migration date if not manually disabled, but this does not extend the global April 5, 2027 deadline.

Keep the paging replacement decision separate from any AI investigation evaluation. Corelayer sits alongside paging and scheduling; it does not replace them. Optional Corelayer evaluation should not delay procurement, configuration, or validation of the paging platform.

Common Opsgenie Migration Challenges and How to Address Them

Most alerts, schedules, and policies migrate automatically to Jira Service Management, but that does not establish account-level compatibility. Deprecated configuration and integrations can require manual updates. Treat automated transfer as one part of migration, not proof that paging workflows and historical records are ready for cutover.

Key Problems Encountered During Opsgenie Migration

  1. Outdated destination guidance. Earlier Atlassian materials listed both Jira Service Management and Compass as destinations. Current guidance directs Compass alerts and on-call capabilities to Jira Service Management. DX receives Compass catalog and scorecard functionality, but does not support alerts and operations. Check current guidance before committing to a destination; avoid older comparisons as a basis for migration.
  2. Unsupported legacy configuration. Review notification policies, deprecated global integrations, Heartbeats V1, Groups, and Policies V1. Do not assume behavior carries across unchanged. Action-policy behavior may need recreation with Jira Service Management Automation. Inventory actual usage and identify what requires manual remediation.
  3. Integration and workflow changes. Replace Opsgenie Groups with Teams so affected schedules migrate properly. In alert workflows, assignees replace owners, and teams become responders rather than owner teams. Verify roles, user assignments, API endpoints, Terraform configurations, and custom scripts accordingly. Automated synchronization does not remove the need to verify workflows and integration configuration.
  4. Historical-data verification before shutdown. After Opsgenie is disabled, only migrated data remains in Jira Service Management, and leftover Opsgenie integrations stop working. Before disabling, verify required historical records and audit evidence are available in the destination. Establish requirements from your inventory; do not assume all needed records transfer automatically.

Paging destination tooling and manual remediation remain your responsibility. Corelayer complements those primitives as an AI investigation layer, not a replacement. Keep investigation decisions separate from migration tasks; Corelayer does not perform configuration updates, data transfer, or validation.

What to Look for in an Opsgenie Migration Destination

Evaluate two decisions separately: where paging and escalation will run, and whether an additional investigation layer will assist engineers. A paging destination must preserve your on-call operating model. Investigation layers require separate evaluation of evidence quality, integration depth, autonomy, and human approval. Corelayer sits alongside paging and scheduling; it does not replace them.

Must-Have Features for Paging Continuity and Optional AI Investigation

  • Paging and escalation fit: Validate schedules, escalation behavior, alert ownership, and responder assignments against your workflows. Jira Service Management provides these features across plans, but alert assignees replace owners, and teams become responders rather than owner teams. Test these differences rather than assuming operational parity.
  • Importer coverage: Ask which configurations migrate, which require conversion, and which need manual rebuilding. Atlassian documents automatic schedule synchronization but unsupported Opsgenie Groups. Replace Groups with Teams to migrate properly. Use your actual configuration inventory to assess coverage.
  • Integration compatibility: Verify each monitoring source and downstream workflow against destination integrations. Test alert creation, responder assignment, and lifecycle updates. For investigation layers, assess depth of production context access, not only connector availability. Corelayer lists PagerDuty and incident.io integrations but does not guarantee compatibility with all workflows.
  • Plan and billing fit: Jira Service Management offers Free, Standard, Premium, and Enterprise plans. Advanced AI-driven alert grouping, incident workflows, and automation are tied to Premium and Enterprise. Confirm entitlements, user counts, licensing, and billing impacts. Do not assume current arrangements carry over unchanged.
  • Historical-evidence availability: Ask what alert history and investigation evidence remain accessible, where, and how engineers retrieve it. Require documented answers and retrieval tests. Configuration migration alone is not proof of evidence availability.
  • Deployment and inference controls for optional investigation: Evaluate system production context, BYOC or on-prem deployment, and flexible inference options together. Corelayer supports deployment in customer cloud or on-prem, and integrates with own LLM gateways or licensed models. Assess these choices collectively to define sensitive-data boundaries. Verify which agents act autonomously, evidence supporting conclusions, and where engineers approve changes. Corelayer produces cited root-cause analyses and PR suggestions; engineers decide what to merge.

Compare paging destinations on documented capabilities and plans. Compare investigation layers on evidence quality, integration depth, autonomy, and engineer control. Keep these evaluations separate so investigation does not substitute for validated paging continuity. For a fuller set of evaluation criteria, see our guide on how to choose an AI on-call platform.

How On-Call Teams Can Choose an Opsgenie Migration Path

Treat paging migration and investigation tooling as separate decisions. First, establish which destination meets operational requirements and what the migration transfers. Then evaluate whether investigation capabilities meet your needs or if a separate layer such as Corelayer fits alongside. The following planning scenarios illustrate options.

  1. Use Atlassian’s Jira Service Management migration tool
    • Team need: Move from Opsgenie using Atlassian’s migration workflow.
    • Platform or capability: Inspect Settings > Plan your move for recommended Jira Service Management plan. Alerts, schedules, and policies migrate automatically.
    • Validation: Assign an Opsgenie Owner who is also a site admin to schedule and review user counts and billing. Verify transferred configuration prior to acceptance.
  2. Scope an incident.io migration
    • Team need: Evaluate phased, team-by-team transition.
    • Platform: incident.io’s Rescue Program offers schedule, escalation-policy, and user imports. Investigations connect telemetry, code changes, and incident history.
    • Validation: Confirm import coverage as documentation varies. Evaluate investigation separately, noting pull requests require human review.
  3. Evaluate PagerDuty against requirements
    • Team need: Assess alternative on-call destination.
    • Platform: PagerDuty’s SRE Agent develops root-cause hypotheses querying logs and metrics. If you are weighing newer options alongside it, compare AI-native PagerDuty alternatives for on-call against the same requirements.
    • Validation: Establish importer coverage, data handling, pricing, and migration steps directly. Test investigation independently.
  4. Resolve a Jira Service Management Data Center constraint
    • Team need: Plan destination for Jira Service Management Data Center.
    • Platform: Atlassian’s tool supports Cloud destinations only. Options include moving to Cloud site or migrating Data Center to Cloud first.
    • Validation: Decide feasible Cloud path prior to scheduling. Corelayer does not alter this limitation.
  5. Preserve historical evidence before shutdown
    • Team need: Retain required historical and audit records.
    • Platform: Jira Service Management migration preserves only migrated data; leftover integrations stop.
    • Validation: Verify record availability before disabling Opsgenie.
  6. Add optional Corelayer investigation after paging choice
    • Team need: Evaluate production-context investigation alongside paging.
    • Platform: Corelayer lists PagerDuty and incident.io integrations, supports cloud or on-prem deployment with PII masking and zero data retention.
    • Validation: Assess integration, deployment, and inference configuration together. Define data boundaries and evaluate investigation independently.

Corelayer adds whole-system investigation spanning code, infrastructure, deployments, and observability, learning from failures and feedback. Its deployment and inference options offer configuration flexibility for sensitive environments. Evaluate these capabilities alongside the paging platform’s own investigation features, without assuming competitors lack them.

Best Practices for Testing and Completing an Opsgenie Migration

Use the following sequence as an editorial synthesis of Atlassian’s migration documentation to define acceptance checks before cutover.

  1. Inventory configuration and retained history. Record teams, schedules, escalation rules, notification channels, integrations, API dependencies, Terraform configuration, and retained history. Use as baseline for migration verification.
  2. Choose the destination and assign owners. Confirm destination and licensing. Assign owners for migration, workflow validation, and acceptance. Schedule migration at least seven days ahead. Allow buffer before April 5, 2027.
  3. Pilot migration with a team. Validate importer coverage against inventory. Identify transferred and missing items, and manual configuration needs. Define pilot duration and acceptance criteria.
  4. Test paging workflows in the destination. Validate acknowledgement, escalation, and recovery workflows. Keep optional Corelayer investigation pilot separate as investigation results do not prove paging readiness.
  5. Complete technical cutover checks. For Jira Service Management, update REST API endpoints, switch Terraform to Atlassian Operations provider, port call numbers, configure automations and integrations, and migrate users to Jira app. Treat as explicit acceptance checks.
  6. Review evidence and accept shutdown before disabling Opsgenie. Verify historical records and audit evidence. Communicate cutover and disable Opsgenie only after acceptance. Leftover Opsgenie integrations stop after shutdown; only migrated data remains available. Disabling is irreversible. The 120-day automatic shutdown window after migration does not extend the April 5, 2027 deadline.

Benefits of a Validated Opsgenie Migration and Separate AI Investigation

Validated migration establishes that your destination supports required on-call workflows. AI investigation addresses understanding production failures. Acceptance criteria for migration readiness and investigation capability should remain distinct.

1. Operational continuity. Confirm alerts reach intended responders, schedules assign coverage correctly, and escalation behaves as expected. Pilots should exercise acknowledgement, escalation, and recovery before disabling Opsgenie. Comparing MTTA and MTTR incident response metrics before and after cutover shows whether response times held. These checks establish readiness, not guarantee zero downtime.

2. Visibility into configuration and plan gaps. Validate destination licensing and features; do not assume parity. Atlassian associates advanced alert grouping, incident workflows, and automation with higher-tier Jira Service Management plans. Identify manual remediation needs before acceptance.

3. Evidence preservation checks. Verify that required historical and audit evidence is available before source access ends. After Opsgenie shutdown, only migrated data remains available, and integrations stop working. Workflow tests alone do not confirm evidence preservation.

4. Whole-system investigation context. Corelayer’s production context graph spans code, infrastructure, deployments, and observability, learning from failure patterns and feedback. Alongside validated paging, it provides a separate investigation layer, distinct from alert delivery or root-cause identification.

5. Engineer-controlled changes in sensitive environments. Corelayer agents produce cited root-cause analyses and PR suggestions. Engineers decide what to merge, making human approval explicit without implying autonomous production changes.

How Corelayer Adds AI Investigation Alongside Your New Paging Platform

Corelayer builds a production context graph integrating code, infrastructure, deployments, and observability. Corelayer’s production support agents use that context to investigate production issues in complex, regulated environments. Corelayer adds an investigation layer alongside your paging platform, not a replacement for paging or scheduling.

We describe learning from failure patterns and engineer feedback as capabilities supporting investigation and prevention, without guarantees of incident prevention. Agents produce cited root-cause analyses and PR suggestions reviewed by engineers, who decide production changes.

Corelayer supports deployment in your cloud via Bring Your Own Cloud (BYOC) or on-premises, with custom PII masking and zero data retention by default. Flexible inference options integrate with your own LLM gateway or licensed model providers. Evaluate deployment and inference together against your sensitive-data needs; deployment location alone is not a data boundary guarantee.

Corelayer integrates with PagerDuty and incident.io. Maintain responsibility for paging and scheduling in the migration destination, and evaluate Corelayer separately for evidence quality, integration depth, and deployment requirements. Broader AI on-call platform evaluations cover this category distinctly from Opsgenie migration.

Final Thoughts: Choose Your Destination and Validate Before April 5, 2027

Jira Service Management is Atlassian’s current migration path. External paging platforms are separately scoped alternatives with their own migration and validation workflows. Choose your destination, inventory dependencies, pilot a team, and test acknowledgement, escalation, and recovery workflows. Complete cutover with a buffer before April 5, 2027, when Opsgenie becomes inaccessible and unmigrated data is deleted. Disable Opsgenie only after acceptance checks pass.

Keep paging migration and optional AI investigation decisions distinct. Corelayer can complement your selected paging platform for investigation without replacing paging or scheduling. To evaluate Corelayer’s investigation layer, book a demo while continuing migration planning and validation.

Frequently Asked Questions

What is an Opsgenie migration destination?

An Opsgenie migration destination is the platform that assumes your team’s operational functions after Opsgenie shuts down: alert intake, on-call schedules, escalation policies, notifications, and response workflows. Define the destination by these requirements, not solely by configuration import capability. Inventory integrations, API dependencies, Terraform, and historical records before choosing it. Corelayer provides an optional investigation layer but does not replace paging and scheduling. Keep paging and investigation decisions separate.

Why do on-call teams need to migrate before April 5, 2027?

April 5, 2027 is the Opsgenie shutdown date, not just end of technical support. Opsgenie becomes inaccessible and unmigrated data is deleted. Teams must complete migration and validate required records before this date. Allow a completion buffer for testing and correction. Corelayer can support investigation alongside your replacement paging platform but does not remove migration obligations.

What are the best migration options for Opsgenie customers?

Jira Service Management is Atlassian’s current migration path, with a built-in tool migrating alerts, schedules, and policies. Alternatives include incident.io, which offers phased rollouts and imports (verify coverage), and PagerDuty, which offers investigation capabilities via its SRE Agent. No universal winner is established. Choose based on your operational needs and evaluate Corelayer separately for investigation.

Is Compass still a suitable Opsgenie migration destination?

A fresh migration to Compass is not recommended. Atlassian now directs Compass alerts and on-call functions to Jira Service Management as part of Service Collection. Compass operations migration must start before the customer’s Compass contract ends or December 31, 2027, whichever is earlier. DX transitions catalog and scorecard functions but does not support alerts. Corelayer remains a separate investigation option, not a paging replacement.

How do you migrate from Opsgenie to Jira Service Management?

Start in Opsgenie under Settings > Plan your move to review the recommended Jira Service Management plan. Scheduling requires an Opsgenie Owner who is also a site admin. Select the plan, review user counts and billing, and schedule migration at least seven days ahead. The tool migrates alerts, schedules, and policies, but workflows and integrations must be validated before turning off Opsgenie. Corelayer provides a separate investigation layer, not migration tooling.

Can Opsgenie migrate to Jira Service Management Data Center?

No, Atlassian’s built-in migration tool supports Cloud destinations only. Data Center customers may migrate to a Jira Service Management Cloud site or migrate their Data Center instance to Cloud first. Review options against your needs before scheduling. Corelayer does not change this limitation; its role is investigation alongside paging.

Which migration checks are required before turning off Opsgenie?

Validate paging, acknowledgement, escalation, and recovery workflows. For Jira Service Management cutovers, update REST API endpoints, switch Terraform to Atlassian Operations provider, port call numbers, configure automations and integrations, and migrate users to the Jira app. Communicate cutover and disable Opsgenie only after acceptance. Leftover Opsgenie integrations stop after shutdown; only migrated data remains. Corelayer investigation does not replace these operational checks.

Does Corelayer replace Opsgenie’s paging and on-call scheduling?

No. Corelayer does not replace paging or scheduling; it complements those functions. It builds a production context graph spanning code, infrastructure, deployments, and observability for investigation. Corelayer learns from failure patterns and engineer feedback, supports flexible inference with your own LLM gateway or licensed providers, and produces cited root-cause analyses and PR suggestions. Engineers decide what changes to merge. Choose and validate your paging replacement first, then consider Corelayer for investigation separately.

Put this into production.

Explore how Corelayer connects to your stack, estimates support savings, and helps teams debug production issues faster.

Related Guides