Prepare for data migration after scheduling your date

During the automated data migration most of your alerts, schedules, and policies will migrate automatically, but some manual steps are required for certain configurations. Once your migration is complete, a Migration Guide will appear in Jira Service Management or Compass to help your team transition and complete those configuration. This guide will be available for 120 days after migration.

What happens after scheduling the migration?

• Billing approval: If your migration requires billing approval, your billing admin must approve the plan before migration begins. Keep track of approval progress and ensure all users are informed.

• Automated vs. manual tasks: Most features and data will migrate automatically. However, certain deprecated features, integrations, and policies may require manual updates before or after migration.

Tasks to complete before migration

Migration is the perfect opportunity to review and clean up outdated configurations, streamline your setup, and prepare your team for upcoming changes. Most of your alerts, schedules, and policies will migrate automatically, but certain deprecated features and integrations may require manual updates before or after migration. 

Each group has different responsibilities. Here’s what you can prepare your teams for the migration:

Tasks for your users

• Tell them what’s changing: Inform your end users about the upcoming migration and the Migration Guide available in Jira Service Management or Compass. We recommend sharing with your users our guide to the migration guide and how to use it. We’ll notify your users about the migration 7 days and 1 day before it happens but consider giving frequent updates to users about the progress of migration depending on your internal workflows.

• Be aware of feature changes: If you’re moving to a lower plan, certain features may be unavailable after migration. Explain them about feature changes and deprecations based on your destination product.

Feature changes and deprecations in Jira Service Management

Feature changes and deprecations in Compass

• Familiarize them with the new product: Users don’t need to take action for the migration, but they should review Jira Service Management or Compass documentation to understand where to find alerts, schedules, and incident response features. 

Get started with Operations in Jira Service Management

Get started with Operations in Compass

Tasks for your team admins

• Review your integrations and policies: Certain deprecated integrations won’t be migrated. You can update these before migration. If you have notification policies in the older version, you’ll need to update them too.

• Update notification and action policies: If your team uses an older version of notification policies you’ll need to update them to the newer version. When you switch to the new notification policies, existing rules will start popping up under each team’s notification policies. Read alert actions and policies after migration. Similarly, if your team has action policies, ask your team admins to start exploring Jira Service Management Automation to replicate similar functionality. 

Tasks for Opsgenie admins

• Update deprecated features and integrations: If your organization still uses deprecated (global) integrations, Heartbeats V1, Groups, or Policies V1, consider upgrading them to their latest versions before migration for a smoother data migration.

• Review user roles and permissions: Ensure that team and user assignments are correct, as this is what will be migrated to Jira Service Management or Compass.

• Check key configurations: Ensure that your API endpoints, Terraform configurations, and custom scripts are updated and compatible with Jira Service Management or Compass. Work with your technical team to make necessary adjustments.

• Monitor billing approval progress: Share regular updates with your teams to ensure they’re aware of migration status and any changes.

Tasks for Opsgenie owners

• Work with your billing admin: If your migration requires billing approval, stay in close contact with your billing admin to ensure it’s approved on time.

• Keep your teams informed: Share updates with team admins and users. If you reschedule the migration date, Opsgenie will notify admins and owners via in-product banners.

• Plan for potential changes: If you decide to cancel migration, Opsgenie will notify all admins of the cancellation. Ensure users are aware of any status changes.