What to expect from Opsgenie migration?

As part of Atlassian’s vision to unify operations across IT and development teams, creating a more connected, AI-powered incident and alerting experience, Opsgenie is being phased out. To support a seamless transition, we’ve built an in-app migration tool that allows you to move to Jira Service Management or Compass. Read the announcement

Migrating ensures that your alerts, on-call schedules, escalation policies, and integrations continue functioning without disruption in your chosen Atlassian product.

How Opsgenie migration works

The migration tool in Opsgenie helps you transition your Opsgenie data to Jira Service Management or Compass, following a structured process to ensure a smooth migration. Opsgenie owners can access to migration tool from Settings > Migrate Opsgenie. This process follows a structured flow:

Step 1: Review the recommended plan and select your new path to manage your IT Operations

On the Migrate Opsgenie page, you’ll find a recommended migration plan based on your current Opsgenie subscription. This recommendation ensures you retain feature parity in your new product, making the transition smoother.

You can also explore alternative migration options to compare plans and products before making a decision.

Choosing between Jira Service Management and Compass

At a high level, your migration destination depends on your team’s focus:

• Jira Service Management is ideal for teams needing a complete IT service management (ITSM) solution, including advanced alerting capabilities like incoming call routing, automations, incident, change, and problem management,

• Compass is designed for development-focused teams looking to track components, manage on-call schedules, and receive real-time alerts.

Review feature changes and deprecations in Jira Service Management.

Review feature changes and deprecations in Compass

Some Opsgenie features may not be available in Jira Service Management or Compass, so it's essential to evaluate how these changes could impact your workflows.

Demo the migration in trial accounts

To better understand how migration works, you can create a 14-day migration demo in trial accounts and test the migration flow before making a final decision.

The trial accounts don’t contain any Opsgenie data. You can manually add alerts, schedules, integrations, and other configurations to see how they function in Jira Service Management or Compass. This helps you verify how key features operate in the new product without affecting your live environment.

Migrating Opsgenie to your existing Jira Service Management or Compass

If you need to move Opsgenie data to an existing Jira Service Management or Compass site, ensure that:

• Your data residency aligns with your target site.

• Your organization is prepared for licensing and billing changes.

• You’ve reviewed potential feature changes based on the selected plan.

Once you’ve selected the best path for your migration, you can proceed with scheduling your migration.

Step 2: Schedule the automated data migration date

To schedule a migration, you must be an Opsgenie Owner and a site admin on your Atlassian site. The migration date must be set at least seven days in the future and can be scheduled up until April 5, 2027. Once scheduled, you can only reschedule the migration date once.

If circumstances change and you need to reschedule again, you can cancel your migration before billing approval. However, cancellations must be made at least 24 hours before the scheduled migration date.

Best practices for scheduling

• For monthly Opsgenie plans – Schedule near your renewal date to avoid duplicate billing.

• For annual Opsgenie plans – Schedule anytime.

• Prepare your team – Notify users, configure necessary settings, and check feature availability in your destination product. Read how to prepare your team for the migration.

Step 3: Billing approval and data migration

Once the billing admin approves the migration, the process is confirmed, and the selected product—either Jira Service Management or Compass—is provisioned. Your migration will then run automatically in the background on the scheduled date. Read how to review and approve billing for Opsgenie migration

Your team can continue working in Opsgenie during and after the migration without interruptions. When the migration is complete, you can track the status from the Migrate Opsgenie page. At this point, Opsgenie data begins syncing to the new platform, ensuring all alerts, schedules, and configurations are transferred.

Read more about what to do if Opsgenie migration billing is rejected or expired.

Step 4: Review configurations and complete migration

Once your data migration is complete, you’ll notice some changes in Opsgenie, as well as tasks to complete in your new product.

Changes in Opsgenie

After migration, you’ll have 120 days before Opsgenie is permanently shut down. You can manually turn it off anytime before the shutdown date when you're ready.

To help your team transition smoothly, you’ll see callouts at the top of each Opsgenie screen, informing you about the status of key features and providing direct links to your new product. These links make it easier for your team to get familiar with their new working environment.

Additionally, a banner on your Opsgenie account will remind you and your team of the shutdown timeline, unless you manually turn off Opsgenie beforehand.

Changes in your Jira Service Management or Compass

As soon as your migration is complete, you’ll gain access to a personalized Migration Guide in your new product. This guide is dynamically generated based on your Opsgenie account usage and highlights critical action items and significant changes to your IT operations workflows. What is the migration guide and how to use it?

While Opsgenie Admins and Owners can view all action items, users might have limited visibility. To ensure a smooth transition, we recommend completing all tasks so your new product configuration matches your existing capabilities in Opsgenie.

Step 5: Turn off Opsgenie

Opsgenie will automatically shut down 120 days after migration, but you can manually turn it off sooner once all post-migration tasks are complete.

Turning off Opsgenie is a permanent action, irreversible and removes access to all unsynced data, including any unsynced alerts, on-call schedules, and integrations. Be sure your team is fully transitioned before proceeding. Read what happens when Opsgenie is turned off.

Who’s involved in migration?

Several key roles play a part in the Opsgenie migration process, each with distinct responsibilities.

Opsgenie owner (and site admin)

Opsgenie owner is responsible for planning the migration, selecting the destination product, and scheduling the migration. If the Opsgenie owner is not a site admin, they can still assist in decision-making but don’t have the necessary permissions to schedule the migration themselves.

Responsibilities of the Opsgenie owner

Before migration:

• Review and select the migration destination product.

• Compare feature availability and pricing to determine the best plan.

• Schedule the migration date.

• Ensure all necessary stakeholders are informed.

After migration:

• Confirm all migrated data is accessible in the new product.

• Ensure users can access Jira Service Management or Compass.

• Monitor and resolve any configuration issues.

• Turn off Opsgenie once migration is fully completed.

Opsgenie admins 

Your Admins play a crucial role in configuring integrations and supporting the migration planning process, ensuring a smooth transition. Meanwhile, users must familiarize themselves with the changes, review how their workflows will be impacted, and adapt accordingly.

Responsibilities of Opsgenie admins

Before migration:

• Review and document current Opsgenie configurations.

• Verify integrations and workflows that may be impacted.

• Prepare users for migration.

After migration:

• Reconfigure integrations in Jira Service Management or Compass.

• Ensure on-call schedules, escalations, and alert policies are set up correctly.

• Support users in adapting to new workflows.

Atlassian billing admin

The Atlassian billing admin is responsible for approving billing changes and ensuring the new product is provisioned correctly. Their approval is required before the migration can proceed.

Responsibilities of the Atlassian billing admin

Before migration:

• Review and approve the selected plan and billing changes.

• Ensure licensing and billing align with the organization's needs.

After migration:

• Confirm that new product billing is accurately reflected.

• Assist in resolving any billing-related issues.

ユーザー

Users play an essential role in the migration process by adapting to the new workflows in Jira Service Management or Compass. Once migration is complete, they should review changes to alerts, on-call schedules, and incident management processes in the new product. Users can access the Migration Guide to understand how their daily operations are affected and ensure a smooth transition.

Responsibilities of users

Before migration:

• Familiarize themselves with how the migration will impact their daily workflows.

• Review training materials and Migration Guide content.

After migration:

• Adapt to the new platform and its workflows.

• Ensure they can access and manage alerts, schedules, and incidents.

• Report any issues to Opsgenie admins.

ステークホルダー

For teams migrating to Jira Service Management Premium or Enterprise, stakeholders are included in the migration. However, stakeholders aren’t migrated if the team moves to Jira Service Management Standard, Free, or any Compass plan.

Responsibilities of stakeholders

Before migration:

• Ensure communication with the migration team about changes.

• Understand how stakeholder management will function in the new product.

After migration:

• Adjust to any changes in alerting and notification workflows.

• Stay informed about the status of incidents and operational updates.