Analyze changes

Analysis of configuration changes to Jira Cloud

After analyzing the projects that will be migrated, Cloud Migration Tool presents users with a detailed report of the changes that will be introduced. The analysis process checks all the configuration elements and issues of the projects in the migration scope. Not only that, the app allows you to make transformations to the configuration in the migration scope before moving them to the cloud.

The analysis phase provides you with the following information and data:

• Counters summarizing the number of migrated configuration elements and the problems encountered. Learn more

• Projects that are being migrated. Learn more

• Configuration elements that are being migrated. Learn more

• Users in the migration. Learn more

Open

Configuration counters

On the Analyze changes page, the configuration element reports display the number of elements of each type that will be added, modified, or have problems on the cloud.

The first section of the Analyze changes page contains quick reports representing each configuration element type in the migration. Each report shows:

• how many elements of this type will be added to the destination Jira Cloud’s configuration,

• how many elements of this type will be modified on the destination Jira Cloud’s configuration, and

• the number of problems detected with configuration elements of a given type.

The numbers in these quick reports serve as filters, showing you the refined results in the Projects, Configuration, and Users tabs underneath.

For example, if you want to view all the workflows the deployment will add, click on the + icon in the Workflows summary report. Then, in the Configuration tab, you will see information about each workflow the deployment will add to your Jira Cloud site.

Learn more about the information displayed in the Configuration tab for each configuration element.

Projects being migrated

Cloud Migration Tool is able to add a source project as а new one to the destination site. Also, it can migrate the source project configuration and issues to an existing destination project that doesn’t contain issues.

The Analyze changes > Projects tab lists the projects that will be added to or modified on the destination Jira Cloud site. In addition, it displays the name, key, type, lead, and issue count of each project.

In the tab, there is a tag next to each project indicating the change type:

• addition - the migration will add the project to the Jira Cloud site.

• modification - a source project’s configuration and issues will be added to a project on the Jira Cloud site. The destination project must not contain any issues.

You can click on the project name in the Analyze changes > Projects list to see the source project information in the current Jira instance’s UI. Also, if there are conflicts between projects on the current Jira and the destination Jira Cloud, you can use the Conflicts filter to easily find and manage these errors.

In case the destination project mapped to the source project contains issues, you’ll see an error like the one in the screenshot below:

Open

Configuration elements being migrated

The Configuration tab lists the configuration elements that will be added or modified on the Jira Cloud site. The report contains each configuration element's name, type, and problems, if any are detected.

If you have the Power Admin app installed on your Jira Server/Data Center, a link will show up in the Usage column. That link redirects you to a Power Admin page showing where and how the configuration element is used across the Jira Server/Data Center instance. Learn more about the Power Admin app

In the Configuration tab, there is a tag next to each configuration element name indicating its change type:

• addition - the migration will add the element to your Jira Cloud.

• modification - an element from the current Jira will modify its matching element on Jira Cloud.

The filters you can use here to find specific configuration changes quickly are:

• Type - filters the elements based on their type.

• Addition - shows only the elements that will be added.

• Modification - displays only the elements that will be modified.

• Problems - shows the problems detected.

Users in the migration

The Users tab on the Analyze changes phase contains all the information about the migration status of your users. The Analyze changes page also offers a powerful feature to customize the user details. It's called Customize mapping and allows you to edit user details to:

• map a Server/Data Center user to a different Cloud account and

• resolve user errors like missing or invalid email addresses.

Users with changed migration details are marked as customized.

The migration status of a user can be:

• New: User doesn’t have an account in the Jira Cloud site and will be invited to join

• Existing: User with this email exists on this Jira Cloud site.

• Unknown: User doesn’t have a valid email address, and it cannot be determined if the account exists on the Jira Cloud site. The user either doesn’t have an email address, or its email address is invalid.

• Customized: User is mapped to an account on the Jira Cloud site via custom mapping.

Learn more about migrating users in the User Management and User Transformations documents. Read about the different options available to successfully manage your users and ultimately migrate them safely to the Cloud.

View the detected problems

Cloud Migration Tool detects essential problems and conflicts in the configuration during the Analyze phase of a migration.

The detected problems are two types: warnings and errors. Warnings do not stop you from finishing your migrations, but errors do. So if analysis detects any errors or conflicts between the current Jira and Jira Cloud configurations, you need to take care of them and fix them. Otherwise, you won’t be able to continue and complete the migration.

Make changes to the source configuration in the migration & resolve errors

The analysis phase of the migration does not only report the changes required to blend the source and destination configurations, but it also allows you to make changes to the configuration before migrating it.

On the Analyze changes page, you’ll have the following tools at your disposal:

• Inline transformations of projects and some configuration element types. Read more about these transformations.

• Resolve action suggested for some of the errors detected by the analysis. Read more about this action.

• Download mapping file with the information on how the source projects, configuration elements, and users will be migrated to Jira Cloud. For example, if a new configuration element will be created or an existing one will be updated on the cloud (the so-called mappings between the source and destination elements). This includes the mappings between the source and destination configuration elements.

• Customize mapping - allows you to apply transformation to projects, configuration elements, and users in the migration scope, including the mappings between source and destination configuration elements.

Resolve the detected problems

You can resolve the detected conflicts without leaving the migration wizard. To achieve that, Cloud Migration Tool allows you to:

• change project name and key

• rename workflows, workflow schemes, and issue type schemes, and

• rename project filters

Learn more about transforming configuration elements during a migration.

Rerun analysis after resolving problems outside the migration wizard

To create migrations to Jira Cloud sites:

1. Start a migration as described in the Migrations tutorial.

2. Review what will be added to and modified on the cloud on the Analyze step. If the migration detects any problems or conflicts between the server and cloud projects, the analysis will alert you and show you the details of each problem.

3. On the Analyze changes step, review if any configuration problems are detected.

4. If you have configuration errors or conflicts, you need to resolve them before migrating. Otherwise, you won’t be able to proceed with the migration.

5. Click the Rerun analysis button to check if you have successfully resolved the errors. The gif below illustrates how to rerun the analysis after fixing the detected errors.

6. After resolving all errors and rerunning the analysis, click the Migrate button to run and complete the migration.