Customize your users in advanced experience

The advanced experience allows you to apply individual actions to any user, also the ones whose email addresses are correct.

The actions you can take include:

• Changing individual email addresses

• Merging any users together, including the ones that aren’t duplicates

• Migrating users as former users, deactivating them in cloud

In the advanced experience, you edit your users in a CSV file that includes all users and customers found in your user directory.

Access the advanced experience

Before you can choose the advanced experience, you need to run a user assessment in Jira Cloud Migration Assistant.

Learn how to run the user assessment

Download and edit the CSV file

Once you’ve selected the advanced experience, you’ll be able to download a CSV with all users and customers found in your user directory.

Sample data in a CSV file

Here’s a sample from an actual CSV file.

What the columns mean:

• UserKey: User key. For users created in earlier Jira versions, it should be the same as the username.

• UserName: Username, the primary identifier in your self-managed instance.

• ErrorType: Problem with the email address, either invalid, duplicated, or none if the user’s email address is correct.

• OldEmail: Current email address.

• NewEmail (editable): For users with invalid or duplicated emails, it’s a pre-generated email address that is valid and unblocks the migration. For users with correct emails, it’s their original email address.

• Tombstone (editable): Controls whether a user should be migrated as Former user. The values are True or False. This value takes precedence over assigning a new email – when set to true, the users always gets migrated as Former user.

• AccountType: User type, either a regular user or a customer from Jira Service Management. For Confluence, it always shows ‘user’.

Sorting and order

The users in the CSV file are sorted based on the following criteria, starting from the top:

1. Users with invalid and duplicated emails.

2. Customers with invalid and duplicated emails.

3. Users with correct emails.

4. Customers with correct emails.

Within each category, users or customers are sorted alphabetically.

How to edit users in the CSV file

Here’s a summary of all actions you can apply in the file, with details on how each action affects a user.

Upload and validate the CSV file

When you upload the CSV file, we’ll check that it meets the following conditions:

• The file must have the same format and structure as the original file

• All users with invalid or duplicated emails must be resolved

• All email addresses must be valid

• All users present in the file must exist in Jira

• The file must include the same number of users as the original file

Reviewing and confirming the changes

When reviewing the changes, you’ll see a summary of actions applied across your users, with a count for each of them.

To review in more detail, select List of changed users. This downloads a CSV file that includes only the users that will be modified during the migration.

Re-assessing users and finding new invalid or duplicated emails

It might happen that your user base changes over time. If you re-run the assessment in the future, we’ll check if you have any new users with invalid or duplicated email addresses.

To re-assess your users:

1. In the Assess and prepare your users card on the migration assistant home screen, select View results. You’ll see the results of the previous assessment.

2. Select Assess again. If we identify new users with invalid or duplicated email addresses, you’ll see a warning message asking you to update them.

3. Select Change CSV file in the error message. You’ll be moved to the screen where you can download it.

4. Select Download CSV file to download the default CSV file with all users from your directory.

5. Re-apply the same changes to old users, and update the new users to resolve problems with invalid and duplicated emails.

How to re-apply the same actions to previously modified users

If you don’t have access to the CSV file with previous changes, you can download a file with changed users from the Changes will be applied to users screen. You’ll have to manually copy these users to the main CSV file (with all users and customers) described above.