Opsgenie is going away. The migration should not be a fire drill.

Opsgenie support ends on 5 April 2027. For teams still relying on Opsgenie for alerting, on-call schedules, escalation policies, and incident response, the deadline is fixed. But the real challenge is not simply moving data from one Atlassian product to another.

It is making sure the incident management operation your teams depend on continues to work when the switch happens.

Atlassian has confirmed that Opsgenie will no longer be accessible after 5 April 2027, and customer data that has not been migrated will be deleted. Atlassian is moving Opsgenie's capabilities into Jira Service Management and, for some DevOps use cases, Compass.

That makes migration a technology decision, but it is also an operational one.

An Opsgenie environment is rarely just a collection of alerts.

Over time, teams build alert routing, on-call rotations, escalation policies, integrations, notification preferences, and incident workflows around it. Those configurations become part of how the organization responds when something goes wrong.

A successful migration therefore needs to answer more than:

It needs to answer:

Atlassian's own migration documentation distinguishes between features that migrate automatically, features that require configuration, and features that have been deprecated or replaced.

That distinction matters.

A migration can technically complete while still leaving operational gaps.

Before deciding how to migrate, understand what is actually running today.

That means auditing the current Opsgenie environment, including alert routing, on-call rotations, escalation policies, integrations, notification methods, and the way teams use incident management.

This gives you a baseline for the migration rather than forcing your team to discover missing pieces after the cutover.

For teams using Jira Service Management Data Center, there is an additional consideration. Atlassian's current migration guidance requires a move to Jira Service Management Cloud before Opsgenie can be migrated through the available migration path.

The right destination therefore depends on your existing Atlassian environment, not simply on the fact that Opsgenie is being retired.

The safest migration is not one where the new environment is configured on the day the old one disappears.

It is one where the new environment has already been tested.

That means rebuilding integrations, validating alert routing, checking escalation behaviour, testing notifications, and making sure the people responsible for incident response understand the new environment.

Atlassian recommends preparing stakeholders and reviewing post-migration tasks before the scheduled migration date. Migrations can be scheduled at least seven days ahead, giving teams a defined window to prepare.

For more complex environments, we would go further.

We recommend a structured migration with a clear testing period, rollback planning, and a controlled transition so that teams are not discovering problems during a live incident.

There is a temptation to treat April 2027 as the project start date because Opsgenie continues to work until then.

That is the wrong way to think about the deadline.

The deadline is the latest point by which the migration needs to be complete, not the date when planning should begin.

The earlier you understand your environment, the more time you have to identify dependencies, resolve configuration gaps, test integrations, train teams, and deal with anything that does not migrate cleanly.

There is also a data consideration. After Opsgenie is shut down, only migrated data will remain available in Jira Service Management, while data that has not been migrated will be permanently deleted.

At Alluvium, we treat an Opsgenie migration as an operational transition rather than a simple product replacement.

Our approach covers:

5 April 2027 may sound far away, but complex service environments take time to understand and test properly.

If you are still running Opsgenie, now is a good time to establish what needs to move, what needs to change, and how long the transition will realistically take.