Reached limit of email aliases for a single user during user migration

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Learn what to do when your user migration fails with "Reached limit of email aliases for a single user during".

Overview

User accounts are created in Atlassian's Cloud based on their email address during the user migration.

For security reasons, Atlassian rate-limit the creation of users with canonical emails, like the below example:

1 2 john.doe+business@gmail.com john.doe+personal@gmail.com

As the email address is the primary user identifier in the cloud (also for billing purposes), it's recommended that each user has a unique and valid email address.

Solution

Use the migration assistant's built-in tool to identify and fix invalid email addresses before the migration:

Updated on April 17, 2025

Still need help?

The Atlassian Community is here for you.