/
Best practices for Cloud to Cloud migration using Configuration Manager for Jira Cloud

Best practices for Cloud to Cloud migration using Configuration Manager for Jira Cloud

Owned by Sudhir Kv
Last updated: Nov 29, 2023
4 min read

Overview

This article explains the best practices for migrating Jira from one Cloud instance to another using the Configuration Manager for Jira (CMJ) Cloud app.

Best Practices

Installation

  • You can use Configuration Manager for Jira (CMJ) Cloud to deploy configurations between Jira Cloud sites. For this, you must install the app on both the source and the destination Jira Cloud sites. For more information, refer to this document Installation guide

  • To deploy project configurations between two Jira Cloud sites, you need to:

    • Install Configuration Manager for Jira (CMJ) Cloud on both sites.

    • Provide a separate license token for CMJ Cloud in each Jira Cloud site.

Licensing

  • You must have the Standard, Enterprise, or Premium cloud plan on both Jira Cloud sites. Trial or paid licenses of these three types are supported. Migrations and configuration deployments to Jira Cloud on the Free plan are not supported. Learn more on Jira Cloud plans.

  • You should have a paid license for the CMJ Cloud app on the destination Jira Cloud site and a development license or a trial license for CMJ Cloud on the source Jira Cloud site/sandbox.

  • To use CMJ Cloud, you need two license tokens:

    • one for the source Jira Cloud site, and

    • another for the destination site.

  • Appfire will provide you with these tokens upon purchase of the licenses.

Prerequisites

  • It is recommended that the user must have Site admin or Organization admin permissions on both Jira Cloud sites to deploy configurations on them. The user must be added to both Jira Cloud sites' site-admins or org-admins groups to create a deployment. You can learn more about the different admin roles in Atlassian’s documentation.

  • You need to have an Atlassian API token for your Atlassian account. Learn why you need an API token and how to get one.

  • CMJ Cloud uses the API token to authorize you to the source and the target Jira Cloud sites when deploying configuration. To create a configuration deployment in CMJ Cloud, you must provide your Atlassian account's API token.

  • Make sure CMJ Cloud supports the configuration elements you want to upload to the destination Jira site along with your projects. See the Supported Configuration Elements document.

  • You must have the same third-party apps installed on both the Jira Cloud sites. Any apps configuring objects in the source Jira Cloud site/sandbox must also be installed on the destination Jira Cloud site.

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

Users

  • With CMJ Cloud’s deployments, the users associated with the deployed configuration will be automatically included in the deployment. We recommend reviewing the users after creating a deployment, selecting projects to deploy, and reaching the Analyze changes phase.

  • It is to be noted that Jira users, groups, and roles are integral to the project configuration - permissions, notifications, workflows, etc. Therefore, any users, groups, and roles used in the project you are attempting to deploy will be included in the deployment.

  • How are source Jira Cloud users deployed?

    • Users who don’t have an account on the destination Jira Cloud site will be invited to join after the deployment.

    • Users with emails on the destination Jira Cloud site won’t be deployed and are marked as existing.

    • Users who don’t have an email address or an invalid one will be reported as a problem. These inactive users are deleted or deactivated by the Jira administrator. In these cases, the deployment can’t continue as CMJ Cloud does not determine if the user exists on the destination Jira Cloud site. Therefore, you first need to resolve these problems and then start the migration from the beginning. For more information, refer to this document https://appfire.atlassian.net/wiki/spaces/CMJC/pages/193594083/Deploy+Users#Deploying-users

Review and Analyze Changes

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

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

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

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

Support

More information

  • Please check the road map https://appfire.atlassian.net/wiki/spaces/CMJC/pages/560890337, as we will update it periodically to reflect the features in development and the features planned for the future.

  • It is recommended to check the release notes, which have the latest release versions, highlights, updates, and resolved Issues that were encountered by the previous versions)Release notes

  • Refer to the following document for more information on the CMJ(Configuration Manager for jira) app Overview

 

Related content