...
With the Cloud Migration Tool, you can intelligently smoothly migrate Jira Server or Data Center users to the cloud by correcting missing and . It helps you fix missing or invalid email addresses and resolving resolve conflicts along during the way. After creating process. Once you create a migration, selecting select projects to migrate, and reaching reach the Analyze changes phase, you'll have the necessary tools and control of migrating to migrate the desired users to the cloud without any errors.
See how users are reported during the migration analysis phase in the screenshot below.
...
Which users are migrated to the cloud?
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 migrate will be included in the migration.
After adding projects to the migration, users referenced by linked to these projects through configuration elements associated with these projects are also included. For example, users assigned to issues in a particular project, assigned as project leads, or single users assigned to project permissions, will be included in the migration.
...
How are Jira Server/Data Center users migrated to the cloud?
When it comes to migrating Jira Server/Data Center users to the cloud, the Cloud Migration Tool covers the following scenarios:
Users who don’t have an account on the Jira Cloud site will be invited to join after the migration.
Users with emails that exist on Jira Cloud won’t be migrated and are marked as existing.
Users who either don’t have without an email address or have with an invalid email address will be reported as a problem.
In these cases, the migration can’t continue as the Cloud Migration Tool can’t determine if the user exists on the Jira Cloud site. ThereforeTo continue the migration, you first will need to resolve these errors and then continue the migration.
Customize mapping between Jira Server/Data Center and Cloud users
Users can be mapped to an account on the Jira Cloud site via custom user mapping. By uploading a custom user mapping CSV file, you can customize the Jira Server or Data Center users’ configuration to fix users without email addresses or with invalid email addresses during migrations.
In addition to these cases, you can change the email addresses of several Jira Server/Data Center user accounts to map all of them to a single account on the Jira Cloud site.
...
User mapping during a migration
After starting a migration and reaching its Analyze changes phase, you’ll be able to view all the users from the projects in the migration and customize user details if necessary.
Additionally, you’ll be notified of any errors in the user accounts, like missing and invalid email addresses. Besides correcting errors, you could map several Jira Server/Data Center users to a single Jira Cloud account if you would like to.
The Users tab on the Analyze changes phase contains all that information described above, plus the option to customize the user mapping.
How can you customize the default user mapping?
Customizing mapping allows you to change the default mapping between server and cloud users or default source user information. By uploading a CSV file with the server user usernames and email addresses, you can correct missing and invalid email addresses and map several Jira Server/Data Center users to a single Jira Cloud account.
| Info |
|---|
Users that are not customized but have the same email will be mapped to a single Jira Cloud account. |
first. The Cloud Migration Tool gives you the option to fix user problems without leaving the migration wizard.
Fix problems by customizing user mapping
The Analyze changes > Users tab reports the users in the migration and their details. It also gives you the option to edit user details without leaving the wizard. There are four user states you can observe in the Users tab on the Analyze changes pages:
User A user that doesn’t have an account in this on the Jira Cloud site and will be invited to join.Status colour Green title NEW
User A user with this email exists in this Jira Cloud site.Status colour Purple title existing
User A user who doesn’t have a valid email address and it cannot be determined if the account exists in this Jira the Jira Cloud site. The user either doesn’t have an email address or its email address is invalid.Status colour Red title unknown
User A user whose details are updated and this way it is mapped to an account in this Jira Cloud site via custom mappingthe Jira Cloud.Status colour Yellow title customized
The option to overwrite user details is accessed through the Customize mapping button in the wizard. It allows you to change the default mapping between the details of server and cloud users and default source Jira users’ details. By uploading a CSV file with usernames and email addresses, you can correct problems like missing and invalid email addresses.
With that option, you can also map multiple source users to a single Jira Cloud account. To achieve it, you need to change the email addresses of multiple Jira Server/Data Center user accounts to have the same email address. This way, the Cloud Migration Tool will map all of them to a single account on the Jira Cloud site.
| Info |
|---|
Users that are not customized but have the same email will also be mapped to a single Jira Cloud account. |
To customize the user mapping:
Start a migration.
On the Analyze changes phase, move to the Users tab.
...
Check for any users with missing or invalid email addresses.
...
To resolve any problems with unknown users or if you want to change the default user information, click Download mapping. You will get a CSV file with the default user mapping.
The downloaded file named cmt_usermapping.csv contains the server users’ email addresses and usernames.Modify the CSV file to correct missing or invalid email addresses. Also, if you would like to map several server users to a single Jira Cloud account, change their email addresses to match the email address of that Jira Cloud user.
Click Customize mapping to upload the CVS file with the user changes.
...
After the customizations are applied, you’ll return to the Users tab, where you’ll see that users with changes from the CSV file have the
tag.Status colour Yellow title customized
| Note |
|---|
Losing user mapping changes If you rerun the analysis, you’ll lose any customizations to the user mapping. So, first, resolve conflicts and errors in projects and configuration elements, and then introduce changes to users by customizing their mapping. |
...