Get started with Opsgenie migration as an admin
The Opsgenie owner (who is also a site admin) initiates and schedules the migration and Opsgenie admins handle most of the migration tasks. As an Opsgenie Owner or an Opsgenie admin — or Global operations admin in your new site — your role is to ensure a smooth transition for your team by making the decision to the correct path, configuring settings, managing user roles, and preparing your teams.
Review how roles are changing with Opsgenie’s transition
Opsgenie user roles are mapped to new roles in Jira Service Management and Compass. Familiarize yourself with the changes:
Opsgenie Role | Jira Service Management Role | Compass Role |
---|---|---|
ユーザー | エージェント | フル ユーザー |
Owners (without site admin access) | Product admins or Operations global admins | 製品管理者 |
Owners (with site admin access) | サイト管理者 | サイト管理者 |
管理者 | Operations global admins | Operations global admins |
Custom roles (without incident management usage) | カスタム ロール | カスタム ロール |
ステークホルダー | ステークホルダー | なし |
What’s expected from admins in Opsgenie migration?
チームの準備
Before the migration date, ensure that your users, team admins, admins, and owners understand the transition and are prepared for the changes.
Users should know when the migration is happening and where to find alerts, schedules, and notifications in Jira Service Management or Compass.
Team admins should review integrations, policies, and on-call settings to ensure everything is configured properly.
Opsgenie admins should check API endpoints, update any legacy configurations, and monitor billing approval.
Owners are responsible for overseeing the migration, working with the billing admin, and keeping teams informed.
Taking these steps will help ensure a smooth transition for everyone.
Prepare for data migration after scheduling your migration date.
Use the migration guide
Once your migration is complete, you’ll have 120 days to review and complete tasks using the Migration Guide in Jira Service Management or Compass. We strongly recommend reviewing these tasks, as they are specifically designed to help you replicate your existing Opsgenie workflows in your new product.
Even after Opsgenie is shut down, you’ll still be able to complete most tasks in the Migration Guide, such as setting up integrations or configuring chat tools. However, you won’t have access to your Opsgenie settings to compare them with your new setup. For example, if an integration wasn’t migrated due to version deprecation, you won’t be able to check its original Incoming rules in Opsgenie—but you can still manually recreate the integration and set the necessary rules in your new product.
To ensure a smooth transition, it’s best to complete these tasks while Opsgenie is still active. Work closely with your teams to finalize configuration updates using the Migration Guide.
Read more about the migration guide.
Monitor migration progress
Track your migration status under Settings > Migrate Opsgenie. If billing approval is required, ensure your billing admin completes this step in time.
If you're working with an Atlassian partner, billing is automatically approved, but coordinate with your partner to understand how they support post-migration tasks.
If you're migrating to an existing Jira Service Management or Compass site, collaborate with your teams to determine how new users from Opsgenie will be managed and how your workflows may be affected.
If your destination site is on a monthly subscription, billing is also approved automatically. Inform your billing admin about any new users added from Opsgenie to ensure smooth account management.
Once billing is approved, your migration will proceed automatically on the scheduled date.
Read more about the billing approval.
Turn off Opsgenie after migration
As the Opsgenie Owner and Admin who is not a site admin, you have the sole responsibility to turn off Opsgenie once your migration is complete. Before doing so, ensure that:
All REST API endpoints have been updated.
Your Terraform provider is switched to Atlassian Operations Terraform Provider.
Incoming call numbers have been ported.
All automation and integrations are properly configured in the new product.
Mobile users have downloaded the Jira mobile app (Opsgenie mobile app will no longer be available).
All users have completed their migration tasks in the Migration Guide.
Once these steps are complete, you can turn off Opsgenie permanently. After this, Atlassian will notify all users that Opsgenie has been shut down.
Read what happens when Opsgenie is turned off.
Atlassian notifications are limited to billing approval and 24-hour pre-migration alerts, so admins must communicate regularly.
この内容はお役に立ちましたか?