Download and customize the configuration mapping

Change how projects, configuration elements, and users get migrated

What makes the Cloud Migration Tool a distinct admin tool is its ability to change how Jira Server/Data Center configurations are migrated to the Cloud. You can decide how your projects, configurations, and users will be migrated to your Jira Cloud instance.

We've built a powerful feature in the Cloud Migration Tool allowing you to:

• fix problems mid-migration with Jira Server/Data Center configuration elements like projects, custom fields, contexts, workflows, users, and more, and,

• transform the Jira Server/Data Center configuration in the scope the way you need it migrated to Jira Cloud.

This feature is called Customize mapping, and it’s an extended version of the inline transformations available in the UI. While there are limitations on where you can use certain inline transformations, you can apply custom mapping to any project, configuration element, or user within the migration scope. You can even make changes to custom field contexts.

With Customize mapping, you can rename just about any configuration element and change the destination element it is mapped to. We're also giving you the option to download the current configuration mapping built by the analysis process with the Download mapping option. Keep in mind that the current mapping is always the latest mapping, and it will include any previous transformations you applied to the configuration.

Open

Download and customize the default configuration mapping

Once you add projects to a migration and reach the analysis phase, you'll have the Download mapping and Customize mapping buttons. You'll spot them at the top right of the Analyze changes page. For the exact locations of the Download mapping and Customize mapping buttons, watch the gif below.

Open

With the Download mapping button, you'll get a JSON file listing the details of the migrated configuration elements and how they'll be migrated. Review the following example file for a better idea of what to expect. The file contains all elements in the migration scope no matter their type - projects, users, custom fields, workflows, schemes, etc.

You can take this file and make changes to it or construct your own mapping file similarly and apply it to the configuration. For this purpose, you need to upload a mapping file with transformations to the Customize mapping action. Learn how to add transformations to the JSON mapping file.

Step-by-step guide for downloading and customizing configuration mapping

To customize the default configuration mapping:

1. Start a migration.

2. On the Analyze changes page, click the Download mapping button on the top right.
   You will get a JSON file with the default mapping for all projects, configuration elements, and users in the migration scope.

3. Modify the JSON file to correct problems or change the migration option of an element. Check the guidelines about customizing mapping.

4. Click Customize mapping to upload the JSON file with the changes.

5. Review the number of changed elements in the dialog. If there are no elements with problems reported, click Confirm to apply the transformations from the file.
   The video below shows how to upload and apply custom configuration mapping.

6. Once you're done with the transformations, click Migrate to move on with the migration. When the migration is done, the transformations applied through the JSON file will be tracked in the migration report.