Tenant to tenant migration
This topic applies only to model-driven apps in Dynamics 365 such as Sales, Customer Service, Marketing, Field Service, and Project Service Automation. This topic does not apply to other Dynamics 365 apps such as Finance, Supply Chain Management, Business Central, and so on.
Move an instance to a different tenant
You can use the Tenant to Tenant Migration feature to request to have an instance in one tenant moved to another tenant. To do so, contact technical support and submit a support request.
There are no user-interface changes or version changes as part of this move. You can move one or multiple instances. Once complete, your instance(s) will appear in your new tenant.
When moving individual instances from one tenant to another, if that requires a geographical region change, your tenant becomes a multiregional tenant. Regional features are enabled in the Dynamics 365 admin center.
You might need to reconfigure some applications and settings after tenant to tenant migration such as Microsoft Dynamics 365 for Outlook, server-side sync, SharePoint integration, etc.
Impact of migrating between tenants
When your organization is moved from one tenant to another within the same region, the URL does not change.
In order to perform this operation, you'll need to provide some information, such as:
- What is the source tenant domain and its region? (example: EMEA, NA, APAC)
- What is the destination tenant domain and its region? (example: EMEA, NA, APAC)
- Does the destination tenant have a valid subscription?
- Does the destination tenant have enough available user licenses?
- Does the destination tenant have enough instance licenses?
- Does the destination tenant have enough storage available for the instances being migrated?
If you do not have a subscription and/or trial in the destination tenant, then you will need to create one. You might need to purchase a new subscription in the destination tenant (or convert a trial to paid), if not already done.
You will need to create a temporary instance or instances in the destination tenant, depending on how many source instances you are migrating. Source instance type and destination instance type must match (Production vs non-Production (Sandbox)). The users to be migrated from one tenant to another need to be created on the target tenant as well.
The destination tenant needs an equal or higher number of active user licenses, instance licenses for the instances being migrated, and equal or greater storage as the source tenant.
How the move works
You’ll be provided with a list of prerequisites and post-requisites for your migration as part of the support request raised. The following table describes what Microsoft does before, during, and after your move.
|Before the move
|During the move
|After the move
Notification and support
|What Microsoft does||Your support representative or Account Manager will work with you to request a move and schedule it.||Cut-over for the migration takes several hours, depending on the number of users and the amount of data. During this period, the organization is not accessible, so the cut-over should be scheduled during the evening or over a weekend.
There is a step that will require your involvement, which is to provide a User Mapping File. This is requested in advance so that we can validate the users being moved before the migration takes place.
|You will be alerted by email or telephone when your instance is migrated to the new tenant.
After the tenant migration is complete, your support representative or Account Manager will assist you to contact with billing to cancel and/or credit your previous subscription, if needed.
We will adhere to the terms of the Microsoft Online Services Service Level Agreement for all moves.