How to Move a Microsoft 365 Tenant and Migrate Mailboxes
Question details
The user needs to move a Microsoft 365 subscription across regions to change billing currency while retaining the same custom domain and transferring all mailbox data.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating an organization's Microsoft 365 tenant to a new billing region setup (e.g., from UK/USD to India/INR) without losing the original domain name or email data.
- Observed behavior
- Because the billing region cannot be directly changed, a new tenant must be created. The custom domain must be manually removed from the source tenant before it can be added to the destination tenant, requiring careful mailbox data migration.
Ensure you have Global Administrator privileges for both the source and destination Microsoft 365 tenants, and notify all users about the scheduled email downtime during the domain transfer.
Perform a Cross-Tenant Mailbox Migration
Follow the official cross-tenant migration procedure to transfer user mailboxes and move your custom domain from the source Microsoft 365 organization to the new destination organization.
Migrating between tenants requires setting up the destination environment, syncing the data, and carefully timing the domain transfer to minimize downtime.
Purchase the necessary Microsoft 365 licenses in your new tenant (e.g., the Indian tenant) and create the initial user accounts using the default '.onmicrosoft.com' domain.
Use the Microsoft 365 Exchange admin center or a reliable third-party migration tool to perform an initial sync of mailbox data from the source tenant to the newly provisioned users.
Once the initial data is synced, remove your custom domain from the source Microsoft 365 tenant. You must first remove all user aliases, groups, and resources tied to this domain before Microsoft allows its removal.
Log into the destination tenant, navigate to Settings > Domains, and add your custom domain. Update the DNS records at your registrar to verify ownership.
Change the User Principal Names (UPNs) and primary email addresses in the destination tenant to use the verified custom domain, then perform a final delta data sync to catch any emails delivered during the transition.
Looking for a Cost-Effective Office Suite After Migration?
While restructuring your organization's Microsoft 365 tenant and billing, consider migrating your desktop productivity tools to WPS Office. It is a lightweight, highly compatible, and cost-effective alternative that reduces heavy subscription fees.
Frequently Asked Questions
Can I directly change the billing currency or country of my existing Microsoft 365 tenant?
No, Microsoft 365 does not allow you to directly change the billing country or currency (e.g., from USD to INR) of an existing tenant. You must create a brand new tenant in the desired region and migrate your users and data to it.
Will my users experience email downtime during the domain transfer?
Yes, there is a brief period of inevitable downtime when removing the domain from the source tenant and verifying it in the destination tenant. During this window, emails sent to your custom domain may bounce or be delayed.
Do I need to recreate all user accounts in the new destination tenant?
Yes, user accounts are tied to the specific tenant environment. You must provision all user accounts in the new destination tenant and assign them the appropriate licenses before migrating their mailbox data.
Does the domain removal happen instantly in Microsoft 365?
Domain removal can sometimes take a few hours to propagate through Microsoft's systems, especially if there are lingering dependencies like hidden aliases or Teams accounts tied to the domain. Always ensure every linked resource is updated to the default fallback domain first.
