Skip to end of banner
Go to start of banner

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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This article explains the best practices for Server/Data Center to Cloud migration using Configuration Manager for Jira.

\uD83D\uDCD8 Best Practices

  1. Perform an Integrity check on the source server/DC and fix the errors.

  2. We recommend having the latest version of the Cloud Migration Tool on the source.

  3. Make sure all the 3rd party apps/plugins are up to date.

  4. You need to have the 3rd party apps installed on your Jira Server/Data Center instance also installed on your Jira Cloud site

  5. Always perform migration on your test instance before migrating to production instances.

  6. 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.

  7. Please check what configuration elements are supported: Supported Configuration Elements

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

  9. You need to have Jira System Administrators permissions on Jira Server/Data Center and Jira Cloud.

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

  11. 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, you first need to resolve any detected conflicts.

  12. 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.

  13. Make sure users have a valid email address on the source otherwise, it will be reported as a problem during migration.

  14. You 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

  • No labels