web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Tenant to Tenant Migration of D365 CRM

(4) ShareShare
ReportReport
Posted on by 19

Hi community,

I’m working on a Power Platform + Dynamics 365 CRM tenant-to-tenant migration and came across this thread: Solved: Migration of D365 CRM to Another Tenant

I am planning to open a Microsoft support ticket too, but I’d really appreciate any insights from people who’ve done this before.

I’ve already used XrmToolBox and the Configuration Migration Tool to merge and export all custom solutions I published. However, I’m unsure what exactly happens with the Default Solution — since it can’t be exported directly and contains tens of thousands of components, do I really need to create a new custom solution and manually add all those items one by one? Or is there another recommended approach for handling the Default Solution content during migration?

Also, during the migration, the user domain will temporarily change and be reverted later — will this generate new user GUIDs? And if yes, will that break owner or lookup fields in tables (like Owner, Created By, etc.)?

We’re migrating:

  • Custom model-driven apps, flows, connectors, Dataverse schema & records

  • Dynamics CRM customizations (workflows, plugins, SLAs, roles, etc.)

If you’ve done this kind of migration before, what tools did you use to move Dataverse records between tenants — and did they preserve user relationships and lookups correctly?

Would love to hear your experience and advices.
Thanks in advance!

I have the same question (0)
  • Verified answer
    PerezAguiar Profile Picture
    Microsoft Employee on at
    Tenant to Tenant Migration of D365 CRM
    Hey!
     
     
    It discusses precissely everything on custom Apps, Pages and PowerAutomate.  Even the Default solution, where you'll need to create a new solution and add those customizations so you can export & Import.
     
    If you're doing a Tenant to Tenant Migration, Relationships & Lookups work correctly.  Because you'll need to open a support request and Microsoft Support will copy your environments between tenants, so data would remain, as well as everything that is within managed solutions.
     
    For the users, one of the conditions is a Mapping file. That is: user TEST01@sourcedomain.com will be now USR01@targetdomain.com and so on (as long as is a 1:1 match). This way, Microsoft will perform the mappings of the users (new guids are generated)
     
    Regards,
  • Verified answer
    Community member Profile Picture
    19 on at
    Tenant to Tenant Migration of D365 CRM

    Hey, thanks again for your earlier reply — super helpful!

    I just wanted to follow up and share what we’ve observed in our case, which seems a bit different from the standard expectation you mentioned regarding user GUIDs being regenerated.

    We’ve now gained access to the test environment in the target tenant, and were surprised to find the following:

    • The Default Solution as well as our custom unmanaged solutions (which we had exported separately) are already present in the test environment
    • All entities, records, and even user GUIDs appear to be identical to those in the source tenant
    • We didn’t need to manually import anything — flows, apps, and ownership structures were already there and functional

    This raises a few questions

    1. Is it expected that user GUIDs and record ownership are preserved exactly across tenants in a Microsoft-managed migration
    2. Or should newly created users in the destination tenant typically receive new GUIDs, requiring us to rebind ownership or lookups
    3. Is it possible the migration team performed something outside the standard documented approach, or is this actually expected behavior under the official Microsoft process

    To get clarity, I also contacted the team who performed the migration. Here's what they shared

    1.What tool or method was used to migrate and map user identities

    - We used the official Microsoft scenario https://learn.microsoft.com/en-us/power-platform/admin/move-environment-tenant

    2. Was a mapping file used? If yes, how were GUIDs handled
    - Yes, a mapping file was used — it contained only User Principal Names, no GUIDs
     

    3. Is retaining the original GUIDs expected behavior in this scenario

    - We didn’t expect it — we don’t handle or manage GUIDs

    So despite the documentation and common assumption that new users in the target tenant receive new GUIDs (which would typically require remapping of ownership or lookups), in our case everything came across intact.

    I'd really appreciate any thoughts, validation, or advice from others who've gone through this process. Is there anything we should double-check before proceeding to production?

    Thanks in advance!

  • Verified answer
    Tom_Gioielli Profile Picture
    2,393 Super User 2025 Season 2 on at
    Tenant to Tenant Migration of D365 CRM
    My experience in a Tenant to Tenant move is that everything stays exactly the same, down to the GUIDs of records (which is great, as otherwise you would receive all sorts of mapping issues). The only difference is typically in needing to map user records from one environment to another, but this is possibly only an issue if you have an existing user base in your target tenant.
     
    Regression and smoke testing is always important after a move like this, but honestly this type of move has become significantly easier in recent years and works really well.
  • Verified answer
    Muhammad Shahzad Shafique Profile Picture
    2,336 Most Valuable Professional on at
    Tenant to Tenant Migration of D365 CRM
  • CU29100422-0 Profile Picture
    2 on at
    Tenant to Tenant Migration of D365 CRM
    Tenant-to-tenant migration of Office 365 is the process of securely transferring data, users, and services from one Microsoft 365 tenant to another—often required during mergers, acquisitions, or rebranding. CloudBik Tenant to Tenant Migration Service provides a complete, automated solution to make this migration fast, safe, and seamless. It handles every step of the process, from user mapping and mailbox migration to moving OneDrive, SharePoint, and Teams data without downtime. With advanced tools, data encryption, and real-time monitoring, CloudBik ensures a smooth transition with zero data loss. Organizations can trust CloudBik to deliver a reliable and stress-free Office 365 tenant-to-tenant migration experience.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
MVP-Daniyal Khaleel Profile Picture

MVP-Daniyal Khaleel 130

#2
Tom_Gioielli Profile Picture

Tom_Gioielli 118 Super User 2025 Season 2

#3
Erin Lubben Profile Picture

Erin Lubben 57

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans