How does user assessment work?

Learn about the details of how you can assess and prepare your users for the migration.

What is assessing and preparing users?

User management between Server and Cloud has some differences, with email addresses being one of the main ones:

• In Server, users are identified by usernames – that’s why many users didn’t use correct email addresses as they were never validated.

• In Cloud, users are identified by email addresses – that’s why every email must be valid and unique.

Because of this difference, incorrect email addresses are a migration blocker. Without the right emails, we simply can’t create your users in Atlassian Cloud.

To solve this problem, we built the user assessment to help you quickly scan your entire user base to find users with invalid or duplicated emails that would block your migration. We also added some automatic options or customization in the CSV file to allow you to fix your user in bulk.

You can access the user assessment in the migration assistants, under the Assess and prepare your users card on the home screen:

How and what we assess?

We assess your entire user base. This includes users and Jira Service Management customers from the internal directory and any active directories connected to Jira or Confluence. We assess the copies of users made in Jira or Confluence after syncing with such directories, not the directories themselves.

Below, you can see sample results of the user assessment, with a number of invalid and duplicated emails:

Which experience to choose: Simple vs. advanced

You can choose how to solve problems with user emails by either following the simple or advanced experience. The choice here mostly depends on what level of customization you need: a quick fix or more granular customization with individual actions for every user.

Here are the main differences:

How changes are applied to users

We won’t change your original users. The changes you’ve made will be applied during the migration – to users that we create in Atlassian Cloud. That’s why important users (who will actually work in Jira or Confluence after the migration) should be updated in your original user directory.

Our intention behind user assessment is to give you more insights into problems with your user base, and a way to fix old or unimportant accounts in bulk.

Limitations and differences between Jira and Confluence

You can assess users both in the Jira and Confluence migration assistant, with the following differences:

• Simple experience: A CSV file option is available only for Jira.

• Simple experience: Choosing a different option based on user creation date (for example, creating new emails for new accounts, and deactivating older accounts) is available only for Jira.

Get started with assessing and preparing users

To get started, open the migration assistant and run the user assessment.

Assess your users to find invalid and duplicated emails