Change email domain in Atlassian Cloud: How admins can make the switch without losing data

A rebranding, a company merger or a new IT structure - there are many reasons to change a company's email domain. But in Atlassian Cloud, this change brings with it special challenges:

• Users should retain their access and account history.
• There must be no duplicate or new accounts.
• The changeover must be seamless and secure .

Without careful preparation, a domain change can lead to login problems, duplicate accounts and data loss. In this guide, we will show you how to change your email domain in Atlassian Cloud in a structured and risk-free way.

Requirements for a successful domain migration

Before you start, make sure that the following conditions are met:

Preparing a second Identity Provider (IdP)

• The new domain (e.g. @newdomain.com) should be verified in your Atlassian organization.
• The second IdP should be configured and ready to authenticate users with the new domain.

Rename existing accounts in the new IdP

• If there are already users with @newdomain.com addresses in the new IdP, temporarily rename them to something like old_name@newdomain.com .
• This prevents e-mail conflicts when updating existing users in the current (old) IdP.

How to change email addresses in Atlassian Cloud

Once everything is prepared, you have three optionsfor changing email addresses in the current (old) IdP.

Option 1: Manual update in the Admin Hub

Suitable for small user groups: Admins change the e-mail addresses manually directly in the user administration under admin.atlassian.com.

Option 2: Automated update via REST API

Ideal for larger numbers of users with technical access:

Endpoint: PUT /users/{account_id}/manage/email

Use this endpoint to update specific e-mail addresses based on the account ID.

Option 3: Request Atlassian support to perform the change

For large-scale changes or if you prefer support assistance.

To do this, you must have a CSV file with two columns:

Current e-mail	New e-mail
max@olddomain.com	max@newdomain.com

What happens after the changeover?

As soon as the e-mail addresses have been updated, the users authenticate themselves via the new IdP (e.g. with @newdomain.com). All projects, access rights and account histories are retained.

Important note from our Atlassian expert:

"Logins with the old address can lead to Accidental new accounts lead. Clear communication is crucial here! We provide our customers with a structured E-mail template which is intended to reduce such additional administrative work and guide end users through the changeover in the best possible way."

Dawn Janáček, Atlassian Key Account Manager at XALT

---

Example: Email template for user information

Subject: Important: Your Atlassian login address will change soon

Hello team member,

on [INSERT DATE] your Atlassian e-mail address will be from @olddomain.com to @newdomain.com .

Example: jane.doe@olddomain.com → jane.doe@newdomain.com

What do you need to do?
Nothing. The transition will happen automatically.

As of [effective date]:

• Use your new e-mail address @newdomain.com to the login
• Update any saved access data or bookmarks
• If you use SSO (Single Sign-On), continue to access Atlassian through your regular portal

Will this affect my work?
No interruption to your workflow is to be expected. All your projects, permissions, and settings will remain intact. The only change is the email domain you'll use to log in.

Any questions?
If you have any questions or encounter problems after the changeover, please contact the IT support team at [support e-mail/contact information].

Thank you for your attention to this update. We look forward to continuing our journey as your company!

Best regards
[Name, Position]

---

Advantages of a clean domain migration

• Seamless transition: Users retain access without interruption
• Central user management: Uniform domain structure in the IdP
• No duplicates: Avoidance of accidentally created new accounts
• Secure access: Login remains fully controllable via SSO or SCIM
• Professional appearance: Standardised external and internal communication

Conclusion: A well-planned domain migration prevents chaos and data loss

Switching an email domain to Atlassian Cloud is complex - but with the right preparation, it can be done without any problems. The most important thing is:

• Technical cleanliness in the IdP
• Consistent communication with users
• The right method for account conversion

Those who take a structured approach benefit from a modern, secure and brand-compliant Atlassian environment.