What’s it handy for?
- Jira server-to-Cloud migrations
- Jira Cloud-to-Cloud deployments (i.e. between sandbox and production)
CMJ Cloud offers precise control over mapping projects, configurations, and users from source to target. Resolve migration conflicts through custom renaming and rematching options, including:
- Mapping source configurations (e.g., custom fields, workflows, schemes, contexts) to specific target configurations
- Renaming elements (projects, workflows, custom fields, users, etc.)
- Changing project keys and user emails
CMJ's transformations feature drastically reduces post-migration cleanup work.
Why CMJ for configuration mapping?
- Choose between inline editing or an editable JSON file for mapping preferences
- Use the detailed pre-migration analysis to understand and then modify your migration from the same screen
- Gain total control over mapping configurations, a feature not available with Jira Cloud Migration Assistant (JCMA) alone
- Minimize manual cleanup and reduce duplicate configurations common in migrations
- Ensure repeatability by configuring all transformations in a single mapping file during testing, then migrate in phases to production with the same file
To get started*:
- Install Configuration Manager Cloud Migration Tool on your source Jira Server or Data Center.
- Install and license Configuration Manager for Jira (CMJ) on your target Jira Cloud application.
- Connect the instances through the Cloud Migration Tool UI on your source instance and initiate a migration.
- Add projects with desired data and configurations.
- Use the inline editor to rename projects, project keys, and workflows.
- Select “Download mapping” to get a JSON mapping file of all configurations within the migration scope. Open it in a source code editor like Visual Studio Code.
- Refer to the documentation (Guidelines to Customize the Configuration Mapping) for detailed instructions on making changes.
- Save and upload the file by choosing “Customize mapping” from the analysis screen.
- Re-analyze and migrate when everything is mapped as desired.
*This process is for server-to-cloud migrations. For cloud-to-cloud deployments, install CMJ Cloud on both your source and target. The UI and process will be very similar to the process outlined above.
More details can be found at the product documentation links below:
