Best practices for migrating Jira Server/Data Center to Cloud using Configuration Manager for Jira

Owned by Sandeep Saluru, created
Last updated: Nov 28, 2023
3 min read

This article explains the best practices for migrating Jira from Server/Data Center to Cloud using the Configuration Manager for Jira (CMJ) app

Best Practices

Installation and License

  1. To perform migrations to the Cloud from Server/ Data Center, you must install the Cloud Migration Tool on the Jira Server or Data Center instance and Configuration Manager on your Jira Cloud site.

  2. It is recommended to have the latest version of the Configuration Manager Cloud Migration Tool installed on the source Server/Datacenter so that it has the latest features and bug fixes. You can check the latest compatible versions from the following link:https://marketplace.atlassian.com/apps/1224900/configuration-manager-cloud-migration-tool/version-history. Visit the installation instructions.

  3. You must have the Standard, Enterprise, or Premium cloud plan on the destination Jira Cloud site. Trial or paid licenses of these three types are supported. Migrations to Jira Cloud on the free plan are not supported.

Pre-migration checks

  1. Performing the Jira Integrity Check and fixing the errors on your instance before the migration is recommended. Please refer to https://confluence.atlassian.com/adminjiraserver/using-the-database-integrity-checker-938847667.html

  2. If you have the CMJ’s Integrity Check for Jira app https://marketplace.atlassian.com/apps/1212168/integrity-check-for-jira?hosting=datacenter&tab=overview installed in your source instance, it is recommended to run the Integrity Check on the source Server/Data Center and fix the errors before migration. You can install a trial version of the app.

  3. It is recommended to perform a test migration before the production migration to capture likely issues in your instance.

  4. Create a migration runbook that includes each step in the process, instructions for those steps, who will complete them, and how long they’re expected to take. It will help production migration run smoothly and according to the plan.

  5. Please check and understand what configuration elements are supported: .

  6. Make sure the Jira Server/Data Center has Internet access. If the Jira Server/Data Center has limited access to the Internet, you must allow it to access the Cloud API https://private-api.cmj.botronsoftcloud.com/ and file storage https://prod-cmjc-snapshot-upload.s3-accelerate.amazonaws.com/

  7. Ensure no scheduled jobs are set to run on the instance during the planned deployment period.

  8. Please check/monitor the network firewall to see if it is causing performance limitations that may slow/block the deployment process.

  9. Always perform the deployment process during non-business hours when there is minimal or no user activity to ensure optimal functionality.

  10. Ensure users have a valid email address on the source; otherwise, it will be reported as a problem during migration. See for more information.

Access and Permissions

  1. You should have Jira System Administrator or Org Admin permissions on Jira Server/Data Center and Jira Cloud to create connections and perform migrations.

  2. You should have an Atlassian API token for your Atlassian account. Check about why you need an API token and how to get one.

Review and Analyze Changes

  1. Review the report of the changes introduced to the cloud in the Analyze changes phase . The Analyze Changes UI shows the projects, configuration elements, and users that will be migrated to the Cloud site.

  2. Review any warnings, errors, or conflicts between the server and cloud configurations detected by the analysis. Remember that warnings don't block migrations, but conflicts and errors do. Therefore, one needs to resolve any detected conflicts.

  3. After successful migration, review the migration report to check all the migrated configuration elements and any warnings and errors encountered.

  4. After migration, validate and review your Cloud site data and conduct User Acceptance Testing (UAT) to ensure everything works as expected.

Support

  1. If the migration fails, please collect the Deployment ID and provide it to us by opening a support ticket in the Support Portal. Refer to our article .

  2. Also, we advise you to download a 'Support Zip' (which contains information and logs from your Jira system and Cloud Migration Tool) and attach it to the support request. Refer to .

More Information

  1. Please check the road map , as we will update it periodically to reflect the features in development and the features planned for the future.

  2. For more information, refer to our documentation:
    Configuration Manager Cloud Migration Tool:
    Configuration Manager for Jira Cloud: