On this page:
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 checks all the configuration elements and issues of a project.
The analysis report contains information about the following:
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
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
The Projects tab shows you the projects that will be added to the destination Jira Cloud site. In addition, it displays the name, key, type, lead, and issue count of each project.
The Addition tag next to each project name indicates that the migration will add the projects to your Jira Cloud. You can click on the project name to see the project information on the current (source) Jira.
If there are conflicts between projects on the current Jira and Jira Cloud, you can use the Conflicts filter to easily find and manage these errors.
Configuration elements being migrated
The Configuration tab lists the configuration elements that will be added or modified on the Jira Cloud site. The report there 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 shows the migration status of all users from the migrated projects. The users can be either existing on the Jira Cloud site, new users that will be added to the cloud, or unknown users with an undetermined status.
You also have the powerful option to change how a user will be migrated. Users with changed migration details are marked as customized.
The Users tab on the Analyze changes phase contains all the information about the migration status of your users, plus the option to customize their user mapping. With custom user mapping, you can map a source user to a different cloud account and resolve user errors like missing or invalid email addresses.
The users in a migration can be:
New: User who 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.
Check out our complete User Mapping tutorial, which introduces the different options you have to successfully manage your users during a migration and ultimately transport 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 in case the analysis detects any error or conflict between current Jira and Jira Cloud configurations, you need to take care of it and fix it before you can complete the migration.
We advise you to carefully read through the texts of the problems and follow the resolution procedures if any are provided.
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 and workflow schemes
rename project filters
Learn more about transforming configuration elements during a migration.
Rerun analysis when problems are detected
To create migrations to Jira Cloud sites:
Start a migration as described in the Migrations tutorial.
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.
On the Analyze changes step, review if any configuration problems are detected.
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.
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.
After resolving all errors and rerunning the analysis, click the Migrate button to run and complete the migration.