JIRA - Email Migration

[Vamshi Krishna Kaveti]

JIRA - Email Migration
changing users email from domain.com to domain.org for project 1 but unable to do it as users have already created domain.org and got accesses to few repositories from different project 2.
What is the best solution?

[Marc -Devoteam-]

Hi @Vamshi Krishna Kaveti 

Please elaborate your request, what is the relation on the mail address within Jira to a Repository in spaces?

To help you out more infromation is needed on what seems to be your request or issue

[Vamshi Krishna Kaveti]

Hi @Marc -Devoteam-  project1 jira (domain.com) has bitbucket project access as well. and project 2 doesnt have jira but have few bitbucket repositories on my second email atlassian account (domain.org).

[Marc -Devoteam-]

Hi @Vamshi Krishna Kaveti 

But what is your question, what do you want to achieve?

If you use Bitbucket cloud solution, this is an open public application.

If you have or use different accounts there, you would need to reach out to Atlassian Support to se if they can be combined to one

[migration expert]

This is a common issue when managing domain transitions. What you are running into is an Atlassian account conflict. Because Atlassian uses a unified identity system across Jira and Bitbucket, you cannot change the Project 1 @domain.com emails to @domain.org if those @domain.org addresses are already registered and "taken" by the Bitbucket access in Project 2.

Since Atlassian doesn't have a native "merge accounts" feature for end-users, you have to use an "Email Swap Workaround" to free up the target addresses.

Here is how to resolve it:

The Email Swap Workaround:

Free up the Target Email: Have the user log into their existing Bitbucket account (@domain.org). Ask them to change their email address to a temporary dummy alias (e.g., user+temp@domain.org). This immediately frees up their actual @domain.org address in Atlassian's system.

Update the Main Account: Log into the original Jira account (@domain.com) and change the email address to the newly freed @domain.org address.

Consolidate Access: This updated account now holds the Jira history. You will just need to invite this updated @domain.org account to the Bitbucket repositories in Project 2. The temporary account can then be deactivated or deleted.

(Note: If you have Atlassian Access and both domains are verified, this can be managed centrally by an Org Admin, but the swap logic remains largely the same).

A Note on the Broader Migration: Since this is part of a larger corporate domain migration (domain.com to domain.org), handling accounts manually can be tedious. If your IT team is also migrating the actual user mailboxes across platforms (like Google Workspace or Microsoft 365), it is highly recommended to use a dedicated tool like SysTools Email Migration software. It automates the backend heavy lifting of moving the actual inbox data seamlessly during a domain change, freeing up your time to manually sort out these specific SaaS access conflicts.

Hope this helps get the users properly synced up!