How to change user information in Cloud to Server migration
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
The content on this page relates to platforms that are not supported by JIRA applications. Consequently, Atlassian can not guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done at your own risk.
Problem
When migrating Jira projects from cloud to on-premise, usernames, user Full Names, or e-mails can be modified to match the company's user guidelines.
For example, cloud usernames are set in unique long strings, and Full Name and email are retrieved as mail providers, as the image below:
Depending on the company user guideline, the data can be modified to match, as example, a LDAP naming convention.
Steps for the change
Similarly to how to migrate user contributions to a new username the Jira Administrator shall edit the xml files from Cloud backup. With the steps:
| Action | Example |
|---|---|
| Create a Cloud backup as seen here |
|
| Find the usernames to be modified in the entities.xml file present in the backup zip. |
|
After mapping the username from entities.xml to the name to be used, use text substitution tools to modify both entities.xml and activeobjects.xml into new files, to be zipped. (note from this procedure you can also modify e-mail, names, etc) | Example using unix sed to modify user string 606b70aea23f99007526df25 to dalves: |
| Transfer the new zip files, with modified data, to Jira import folder (jira-home/import) and proceed with the data restore. |
|
