Tenant-to-tenant migration scenarios
What's involved in migrating Dynamics 365 from one Microsoft 365 tenant to another — common scenarios, what moves, and what has to be rebuilt.
Sometimes Dynamics 365 needs to move from one Microsoft tenant to another — an acquisition consolidates two organisations onto a single tenant, a divestiture splits one company into separate tenants, a customer migrates from a partner-managed tenant to their own, a re-organisation moves business units across tenants. These migrations are non-trivial and infrequently smooth; planning makes the difference between completed-on-schedule and stuck-for-months.
Why tenant migration is hard. A Microsoft tenant is a deep container — Entra ID, all M365 services, all licensing, all Dynamics 365 environments, all Power Platform environments, file storage, mail, SharePoint, every integration token, every service principal. Moving from one to another isn't a copy; it's a re-establishment across many surfaces simultaneously.
Common scenarios.
-
Carve-out from a parent tenant. A business unit being divested into its own company needs its Dynamics 365 environment moved to a fresh tenant. Most surgical migration scenario.
-
Merger consolidation. Two companies merging consolidate onto one tenant. Either one party's existing tenant absorbs the other, or both move to a fresh tenant. The bigger of the two usually absorbs.
-
Partner-managed to customer-managed. A customer running Dynamics 365 inside a partner's tenant moves to their own tenant once they outgrow the partner-hosted model.
-
Geographic / regulatory move. Moving from a global tenant to a country-specific sovereign tenant for data-residency requirements.
-
Sovereign cloud move. Moving from commercial cloud to GCC, GCC High, or DoD — substantial operational changes.
What Microsoft supports natively.
For Dataverse-based environments (CRM, Customer Service, Field Service, Power Platform), Microsoft has improving but not perfect tenant-migration tooling. The pac CLI and partner tools (KingswaySoft, Skyvia, Scribe) export and import data, with manual reconciliation for identity-bound items.
For Business Central, Microsoft offers a tenant migration through the BC admin centre — copy environments from one tenant to another, with limitations on identity-bound configuration.
For Finance and Operations, tenant moves go through Microsoft FastTrack-supported processes. Not self-service; substantial Microsoft engagement.
What moves cleanly.
- Application data (Dataverse rows, BC data, F&O data).
- Customisations as packaged solutions / apps / deployable packages.
- Configurations stored as data.
- File attachments (with rebinding to new SharePoint locations).
- Code (extensions stored in source control).
What has to be rebuilt or rewired.
- Identity / user accounts. Users are bound to the originating Entra tenant. Moving users requires creating new accounts in the destination tenant and reassigning record ownership.
- Service principals and app registrations. Each integration's authentication needs new registrations in the destination tenant.
- Connections in Power Automate / Power Apps. Every connection re-authenticates after migration.
- SharePoint integration. Document libraries rebind to destination SharePoint.
- Licensing. New licences provisioned in destination; original licences released.
- Custom domain names. DNS records, SSL certificates re-establish.
- External partner access — Entra B2B guest accounts re-established.
- Webhook subscriptions, Service Bus endpoints, Event Grid subscriptions — every external integration target reconfigured.
- Telemetry endpoints — Application Insights resources may move.
The phased approach.
- Discovery — comprehensive inventory of every Dynamics 365 environment, integration, custom code, configuration, integration point, user.
- Architecture — destination tenant topology, with identity and integration design.
- Pilot migration — migrate a small slice (one environment, a few users) to validate the approach.
- Mock migration — full dress rehearsal.
- Production migration — typically over a weekend with read-only freeze on the source.
- Hypercare — extended support for the first weeks as integrations re-establish.
Timeline. Realistic timelines for tenant migrations span 3–12 months depending on scope. Quick promises of "we'll move it next month" usually miss the depth of work.
Operational reality. Engage Microsoft FastTrack early. The cost-benefit of doing this without expert guidance rarely pays.
Related guides
- Tenant administration for Dynamics 365How to administer a Dynamics 365 tenant — Microsoft 365, Power Platform, Business Central, and Finance/SCM admin centres, roles, and tenant-level governance.
- Backup strategy for Dynamics 365What Microsoft backs up automatically vs what customers need to plan for — Dataverse, F&O, third-party backup tools, and the difference between backup and disaster recovery.
- Capacity planning for Dynamics 365How to plan and monitor capacity in a Dynamics 365 tenant — Dataverse storage, API calls, AI Builder credits, environments, and the cost levers that matter.
- Data classification for Dynamics 365How to classify data in Dynamics 365 to drive security, retention, and compliance decisions — classification tiers, where to record them, and the integration with Microsoft Purview.
- Data residency and compliance in Dynamics 365Where Dynamics 365 data lives, how compliance certifications stack up, GDPR and country-specific rules, and the customer's responsibilities.