What is a tenant to Tenant Migration?
What is a tenant-to-tenant migration?
A Microsoft 365 tenant is an individual and unique customer account that provides an environment for controlling Microsoft 365 users, services, and data. Tenants are hosted on Microsoft’s cloud servers, which are redundantly backed up and spread out all over the world. Microsoft 365 tenants are used in a variety of ways depending upon the needs of different customers, and licensing determines which features get unlocked.
Office 365 Tenant Migration involve the migration of mailboxes and service settings from one Microsoft 365 tenant to another one.
When do I need a tenant-to-tenant migration?
The number of cloud adoptions among businesses is increasing each day. There are several architecture approaches for mergers, acquisitions, divestitures, and other scenarios that might lead you to migrate to a new cloud tenant:
Microsoft 365 tenant name change.
Once you create a tenant with the name, there is no option to change it. So, it's really important to choose the right name before creating a tenant. In this case if you want to use a different tenant name, you will need to create a new tenant and move/migrate data and users to it.
Microsoft 365 tenant location (region) change.
When you create a new Microsoft 365 tenant account, it automatically checks up the external IP that generated the request and provisions the tenant in that particular region. You cannot change the Microsoft 365 tenant region as Microsoft has already created the specific instances for all workloads and secured the required namespaces which cannot be modified. The only way to change the tenant location is to create a new tenant on your desired location and migrate the data from the old to a new one.
A merger or an acquisition.
Dealing with a company merger or acquisition can be challenging as this involves migrating data to Microsoft 365 or merging tenants. There are several scenarios you can consider at the time of mergers and acquisitions:
Tenant-to-tenant migration without rebranding.
You may use this scenario if you are selling your business unit and brand identity. Identities will migrate to a target tenant and will keep the existing domain as part of the migration.
Tenant-to-tenant migration with rebranding.
This business scenario is used when the business unit adopts the target company’s branding. In this case identities will migrate to a new target tenant and will change the brand identity as part of the migration.
Cloud tenant move.
When you need to split users across two tenants, you should consider cloud tenant move. If you follow this scenario, identities will remain in the source tenant, but all users in the affected domain and all workloads are moved to a new cloud tenant.