...
\uD83D\uDCD8 Best Practices
Perform an Integrity check on the source server/DC and fix the errors before the migration.
We recommend having the It is recommended to have the latest version of the CMJ Configuration Manager Cloud Migration Tool installed on the source which will have the latest features and bug fixes.
Make sure all the 3rd party apps/plugins have the latest versions.
The 3rd party apps (compatible with the cloud) that are installed on the source Jira Server/Data Center instance should also installed on the target Jira Cloud site.
Always perform migration on test instances before migrating to production instances.
Please check Note that 3rd party apps, even if they are available for Cloud and Server/Data Center, will work differently in most cases. Please get in touch with the 3rd party app vendor regarding the migration procedure of the app data.
One must have either 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.
Perform an Integrity Check Integrity Check on the source Server/Data Center and fix the errors before the migration.
It is recommended to perform a test migration before the actual production migration.
Create a migration runbook that includes things like each step in the process, any instructions needed 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.
Please check and understand what configuration elements are supported: Supported Configuration Elements.
Make sure the Jira Server/Data Center has Internet access. If the Jira Server/Data Center has limited access to the Internet, one 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/
One should have Jira System Administrator or Org Admin permissions on Jira Server/Data Center and Jira Cloud.
One should have an Atlassian API token for one’s Atlassian account. Check API Token about why need an API token and how to get one.
Review the report of the changes introduced to the cloud in the Analyze changes phase Analyze Changes. The Analyze Changes UI shows the projects, configuration elements, and users that will be migrated to the Cloud site.
Go through 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.
Note that 3rd party apps, even if they are available for Cloud and Server/Data Center, will work differently in most cases. Please get in touch with the 3rd party app vendor regarding the migration procedure of the app data.
Make sure users have a valid email address on the source otherwise, it will be reported as a problem during migration. One must have either 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 supportedSee User Mapping for more information.
After successful migration, review the migration report Detailed Reports of Successful Migrations to check all the migrated configuration elements and any encountered warnings and errors
After migration, validate and review your Cloud site data and conduct User Acceptance Testing (UAT) to make sure that everything is working as expected.
Please check the road map Product Roadmap: Server-to-Cloud Migration Use Case as we will update it periodically to reflect the features in development and the features planned for the future.
...