# Changing Your Email Domain in Atlassian Cloud: A Loss-Free Migration for Admins > A step-by-step guide for admins on how to change the email domain in Atlassian Cloud without data loss or duplicate accounts. Source: https://www.xalt.de/en/blog/domain-migration-in-atlassian-cloud/ TEAM XALT Atlassian Platinum Partner · 10 June 2025 · 6 min A rebranding, a company merger, or a new IT structure – there are many reasons to change a company's email domain. However, in Atlassian Cloud, this change comes with specific challenges: - Users should **retain their access and account history** - **No duplicate or new accounts should be created** - The transition must be **seamless and secure** Without careful preparation, a domain change can lead to login issues, duplicate accounts, and data loss. In this guide, we show you how to change your email domain in Atlassian Cloud **in a structured and risk-free manner**. ## Prerequisites 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. **Renaming existing accounts in the new IdP** - If users with @newdomain.com addresses already exist in the new IdP, temporarily rename them to something like **old\_name@newdomain.com**. - This prevents email 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 options** to update the email addresses of users in the original IdP: ### 1. Option: Manual update in the Admin Hub Suitable for small user groups: Admins manually change the email addresses directly in user management under [**admin.atlassian.com**](https://admin.atlassian.com/). ### 2. Option: 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 specifically update email addresses based on the account ID. ### 3. Option: Support from Atlassian Support Recommended for very large teams or if you wish to have support guidance. To do this, you must provide a **CSV file** with two columns: | Aktuelle E-Mail | Neue E-Mail | | --- | --- | | max@olddomain.com | max@newdomain.com | ## What happens after the switch? Once the email addresses have been updated, users authenticate 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**. Clear communication is key here! We provide our customers with a structured **email template** to reduce such administrative overhead and guide end-users through the transition as best as possible."* ## Example: Email template for user information ``` Subject: Important: Your Atlassian login address is changing soon Hello team member, on [INSERT DATE] your Atlassian email address will be changed from @olddomain.com to @newdomain.com. Example: jane.doe@olddomain.com → jane.doe@newdomain.com What do you need to do? Nothing. The switch happens automatically. From [effective date]: Use your new email address @newdomain.com to log in Update any saved credentials or bookmarks if necessary If you use SSO (Single Sign-On), access it as usual via the Atlassian portal Will this affect my work? No disruption to your workflow is expected. All your projects, permissions, and settings will be retained. The only change is the email domain you will use to log in. Any further questions? If you have any questions or encounter issues after the transition, please contact the IT support team at [Support email/contact details]. Thank you for your attention to this update. We look forward to continuing our journey as your company! Kind regards [Name, Position] ``` Email template for user information (adapt as needed) ## Benefits of a clean domain migration - **Seamless transition:** Users retain access without interruption - **Centralised user management:** Unified domain structure in the IdP - **No duplicates:** Avoidance of accidentally created new accounts - **Secure access:** Login remains fully manageable via SSO or SCIM - **Professional appearance:** Unified communication externally and internally ## Conclusion: A well-planned domain migration prevents chaos and data loss Changing an email domain in Atlassian Cloud is complex – but with the right preparation, it can be implemented without issues. The most important factors are: - Technical cleanliness in the IdP - Consistent communication with users - The appropriate method for account migration Those who take a structured approach benefit from a modern, secure and brand-compliant Atlassian environment. ## We support you in the implementation and assist with - Setup & validation of new domains - Coordination of IdPs and SCIM - Automation via REST API - User communication and rollout planning [Your contact at XALT](https://www.xalt.de/en/contact/) ## Planning a domain migration in your Atlassian Cloud? We support you with setting up and validating new domains, coordinating IdPs and SCIM, and automating the process via REST API. [Talk to us](https://www.xalt.de/en/contact/) ## More articles ### [Personal AI Agents Compared: Rovo, OpenClaw, and Agent SDKs Like Claude or OpenAI](https://www.xalt.de/en/blog/personal-ai-agents-compared-rovo-openclaw-and-agent-sdks/) Rovo, OpenClaw, or Claude/OpenAI: how personal AI agents differ in 2026 and which approach fits your team. *Atlassian* ### [BaFin Compliance for Atlassian Cloud – What Financial Institutions Need to Know Now](https://www.xalt.de/en/blog/bafin-compliance-atlassian-cloud-migration/) New EU FSA rules have been in effect for Atlassian Cloud in financial services since December 2024. We show what has changed and how you can migrate to the cloud in a BaFin-compliant way. *Atlassian* ### [Atlassian Team '26 Recap: The Shift to the AI-Native Organization and the Role of the Teamwork Graph](https://www.xalt.de/en/blog/atlassian-team-26-recap-teamwork-graph/) XALT was on the ground at Atlassian Team '26 in Anaheim. Our recap covers the Teamwork Graph, Rovo, and the new Teamwork, Service, Product, Software, and Strategy Collections – and what it means for enterprises in Germany. *Atlassian* --- *This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*