Page Comparison

...

...

• Correct user problems
  The Customize mapping feature allows you to correct user problems like missing and invalid email addresses when mapping users during a server-to-cloud deployment. You can also remap server and cloud users this way.

• Merge user accounts
  You can also use the transformations to 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 be the same. This way, the Cloud Migration Tool will map all of them to a single Jira Cloud account.

• Map to a chosen destination user
  You can also apply a transformation to map a source user to a destination user of your choice. You just need to provide the destination user’s ID.

How to apply transformations to users?

...

To apply transformations to users:

1. Start a migration.

2. On the Analyze changes phase, move to the Users tab. Read more about migrating users.

3. Check for any users with missing or invalid email addresses.

4. To resolve any problems with unknown users or if you want to change the default user information, click the Download mappingbutton at the top right. You will get a JSON file with the default mapping of all configuration elements in the migration, including users.

   Image RemovedImage Added

5. Modify the JSON 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. Check the guidelines about customizing mapping.

6. Click Customize mapping, upload the JSON file with the changes, and click Confirm.
   After the customizations are applied, return to the Users tab to see that users with changes from the JSON file have the

   Status
   colour Yellow title CUSTOMIZED

   tag. The video below shows how to upload and apply transformations from a JSON file.
   CMT-customize-mapping.mp4

7. After you’re done making changes to the user mapping, click Migrate to move on with the migration.

...

Guidelines for creating JSON user transformations

In the migration wizard, you can download a file that contains all the information about the users and how they’ll be migrated to the cloud. Then, you can either make changes to that file to include your desired user transformations or you can construct your own file and apply either of the files to the configuration.

The applied file must always must be in JSON format. Also, there are some requirements on how to list the intended transformations in it. Check the guide we’ve prepared to quickly get you started on building your transformations.

For users, the transformation you can apply is changing an email address. This wayWith the Customize mapping option in the migration wizard, you can apply two types of transformations to users being migrated:

• Change email address

• Map to a destination user by ID

By changing the email address, you can create new users, merge multiple users into a single account, and remap source and destination users.

The important thing to note is that we refer to source and destination users are matched by their names. What this means is that you always need to provide the source user’s name in the JSON file in order to apply a transformation to it.

Let’s look at the examples below to make it clearer.

Required JSON records to transform users

You can construct your own JSON file with user transformations and apply it to the configuration being migrated. The examples below show you the records you need to have in the file to change a user’s email address or to map it to a destination user.

Required JSON records to change the user’s email address

The example below shows the specific records required to change a user’s email address.

{
    "users": [
        {
            "source": {
                "id": "invalidEmail@demo",
            },
   "name": "usernameInvalidEmail",         "transformation": {
                "email": "validEmail@demo.com"
            }
        }
    ]
}         

Required JSON records to map a source user to a destination user by ID

The example below shows the specific records required to map a source user to a destination user by ID.

{
    "users": [
        {
            "source": {
                "emailid": "invalidEmail@demo",
            },
            "transformation": {
                "emailID": "validEmail@demo.com5da444878f33800c416f30ed"
            }
        }
    ]
}         

Editing a user in a downloaded JSON file

You can achieve apply the same transformations from above by downloading the current mapping file and editing it. If this is the case, the For more details about editing or constructing a mapping file, check this guide. The examples below show you how the user records will look in the downloaded file and the additional transformation record you need to add.

Transformation to change the user’s email address

When you download a mapping file, the source and destination records for the user most probably will look like this:in the example below. You only need to add a transformation record with the new email address without changing the default source and destination user records. After applying the edited file, the user being migrated will have a new email address.

{
    "users": [
        {
            "source": {
                "id": "invalidEmail@demo",
                "name": "usernameInvalidEmail",
                "email": "invalidEmail@demo"
            },
            "destination": {
                "newObject": true
            },
            "transformation": {
                "email": "validEmail@demo.com"
            }
        }
    ]
}                    

...

Transformation to map a source user to a destination user by ID

When you download a mapping file, the source and destination records for the user will look like in the example below. You only need to add a transformation record with the destination user’s ID without changing the default source and destination user records in . After applying the downloaded file. For more details about editing or constructing a mapping file, check this guide.edited file, the source user will be mapped to that destination user.

{
    "users": [
        {
            "source": {
                "id": "sourceUser@demo.com",
                "name": "sourceUser",
                "email": "sourceUser@demo.com"
            },
            "destination": {
                "newObject": true
            },
            "transformation": {
                "email": "5da444878f33800c416f30ed"
            }
        }
    ]
}