You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi Atlassian Community,
With the Jira Cloud Migration Assistant 1.7.7, we’re bringing a new feature that helps you resolve problems with invalid and duplicated emails that block your migration.
You can use it to:
Assess your whole user base to find invalid and duplicated email addresses
View users and their details to identify important accounts that should be fixed in your user directory
Automatically bulk-fix remaining accounts during migration, for example by merging duplicates, creating new emails, or deactivating users who are no longer needed
All these options should make your migration easier and help you avoid making hundreds of manual updates.
In Server or Data Center, username is the primary identifier, that’s why many users never paid attention to providing valid emails. But, it’s different in Cloud. An email address being the primary identifier must be both valid and unique.
Any email that doesn’t meet these requirements will block your migration.
We recommend that you first use the new feature to identify important accounts, ‘the actual users’, and update them in your user directory.
The automatic fixes in the assistant should be applied to all the remaining users (old, bot, unimportant, or any you choose) whose number is too high to be fixed manually.
Here’s an overview of what you can do in the assistant, with some screenshots:
|Invalid email addresses||Duplicated email addresses|
We can’t fix your users in the source, so any fixes will be applied to the users created in Cloud as you migrate. The final result depends on the option:
Migrate users as Former users: Preserves the activity of a user (comments, history), but the user is deactivated and anonymized – they’re displayed under the name ‘Former user’, everywhere. Users don’t consume the license, can’t log in, and can’t be restored.
Merge duplicated users: All users that share an email address are merged into a single account in Cloud. Permissions and activity (comments, history) are also merged into this account. Whoever has access to the email address can log in.
Create new emails: Replaces the current email with a new one, either pre-generated based on userID or entered by you in the CSV file. Users keep their identity (Charlie Atlassian, and not Former user) and activity. They consume the license, and can log in if they have access to the email address (it needs to be entered by you, not pre-generated).
If you’d like to learn more, see Assess and prepare users for migration.
We’re not stopping at Jira. If you’re also looking to migrate Confluence, we’re planning to add this feature to the Confluence Cloud Migration Assistant soon.
If you have feedback or questions about fixing invalid and duplicated emails, let us know in the comments.