Assistance Needed: Migrating Data with New Domain Emails After Company Rebranding

Namrata Tahilramani

Hello Atlassian Community,

Our company is rebranding. As part of this process, we will be updating our domain and email addresses. We want to ensure that all our data currently hosted on Atlassian (Jira, Confluence, Bit Bucket etc.) remains readily accessible under our new domain and email IDs associated with it.

Could you please guide us on any steps we need to take to migrate our data seamlessly? If specific documents, permissions, or details are required to facilitate this migration, we’d be grateful for the information. Also want to know how much time this will take? 

Thank you for your help!

Tomislav Tobijas

Hi @Namrata Tahilramani ,

I just did this the other day so I can share the following - it really depends on how everything is set up on your end. Like:

• Have you verified your current (old) domain in the Atlassian Admin Hub?
• If so, have you claimed all accounts under that domain?
• Are you using IdP to sync users from another application such as Entra ID or Okta?

If you're using IdP and a connector from that IdP to Atlassian Guard, you'll want to check how the mappings of attributes have been set up.

In cases where you manage current accounts (so you've verified the current domain and claimed accounts), the first thing you would want to do is to verify new domain. With that being done, you'll be able to see if there are any existing accounts under that domain and decide what do to with them (if it's a completely new domain, there probably won't be any Atlassian Cloud accounts under it).

Secondly, once verification is successful, if you're managing everything locally, you would need to manually change all emails from name.lastname@domain1 to name.lastname@domain2. You could potentially make some custom automatizations for it.

Lastly, if you're using SSO for authentication (that is if you have IdP connected), you would want to check that too - the best thing is to test everything out with one test account to see how it will work.

From my experience, the most important part is verifying all domains you have and which you will use for 'transferring' accounts/changing email addresses. This is mostly to avoid duplication/creation of new Atlassian Cloud accounts. After that, you can update all data necessary and update mappings for sync if necessary.

In cases where you don't manage any accounts, meaning you didn't claim the current domain, users would need to change their account email address manually by visiting their Manage profile page (but I guess no organization wants that).

Hope this helps.

Cheers,
Tom