Currently, both the Jira and Confluence Cloud Migration Assistants will insist on having users with invalid email address or duplicate usernames with the same email address fixed prior to proceeding with the migration (exception is when No users & groups is selected with the Confluence Cloud Migration Assistant).

For various reasons, some admins do not need / want to fix these and clear the blocking pre-flight checks. Examples may be.

• When users have left the company, it no longer makes sense to have to fix their email address and have them created in Cloud
• There are thousands of user preflight checks and the time / effort to fix these is high but data loss is likely to be very low to nil.
• Users are not relevant to the migration as they come from external directories.

This feature would be providing an option for the blocking pre-flight check to be converted in to a softer pre-flight check, where the user could dismiss the invalid/duplicate user preflights. These users would then be migrated as anonymous users.

Suggested workaround for Jira

We have shipped a feature in the Jira Cloud Migration Assistant that automatically scopes referenced users for the projects selected. As this feature more accurately scopes users relevant to the selected projects, it should reduce the number of preflight checks on users who don't need to be migrated with the selected projects.

For instructions on this see https://jira.atlassian.com/browse/MIG-141