Fix invalid email addresses in simple experience

This page shows options available in the migration assistant to automatically fix invalid email addresses.

Before you begin

Check this information before you start.

Users from external directories

If you have an external directory, we recommend that you update important users manually, and then apply the Migrate invalid users as Former users option to the remaining users. Treating users with invalid emails as former users and migrating them as such helps you avoid problems after you sync the directory to cloud.

Choose an option to automatically fix users during migration

Choose one of the automatic options to fix the remaining users during migration.

• The changes will be applied to users created in Cloud, not your original users.

• The changes won’t be applied right away, but only after you start a migration.

Do nothing

We won’t make any changes. Your migration will be blocked unless you update users in your user directory.

Migrate invalid users as Former users

Users will be migrated as Former user in Cloud. A former user:

• Is deactivated, can’t log in, and can’t be restored

• Doesn’t consume a license

• Has every activity, such as comments or history, preserved but displayed under the name ‘Former user’

• It’s a container that groups activity from all former users, for example deleted users

Migrate invalid users as Former users up to a certain date (Jira only)

Users who last logged in before the chosen date or who never logged in:

• Are migrated as Former user in Cloud. For more info, see the Migrate invalid users as Former users above.

Users who logged in after the chosen date:

• Receive pre-generated email addresses and are migrated as active users. For more info, see the Create new emails option below.

Create new emails for invalid users

Users get pre-generated email addresses that unblock the migration, because they’re valid. Users with such emails:

• Are migrated as active users

• Consume the license if they’re migrated into a group with product access

• Have every activity, such as comments or history, preserved and correctly displayed under their name

• Can’t log in, because they don’t have access to the email address

This option isn’t used to preserve access for users, but to preserve their identity. The email address is based on userID and a domain most common in your user directory.

Update users based on a CSV file (Jira only)

Use the CSV file to apply to fixes to your users in a more granular way, for example by migrating most of them as Former users and only selecting just a few that should get new email addresses.

Learn how to use the CSV file

Next steps

If the assessment also identified duplicated email addresses, see Fix duplicated email addresses in simple experience. If not, select Review changes where you can apply the changes to your migrations.