About the delivery
ProsessPilotene delivered a tenant-to-tenant migration for Opus Systemer AS (2026).
Used the new tenant-transfer GUI for the first time; it went seamlessly.
Issues: They provided an incomplete list of users in the user mapping file.
→ As a result, users could not access their data without assistance from MS support.
Another issue: Reactivating mailboxes. The old tenant ID remained and caused problems.
Solution: Find the email server records (via make.powerapps.com → tables → email server) and add the columns “use built-in tenant ID” and “tenant ID”. Set the first field to “no” and enter the new tenant ID in the second field. This overrides the old value.
Other issues:
They provided an incomplete list of users (user mapping). As a result, these users had to be created after the migration was complete, views had to be recreated, and data had to be reassigned.
Value creation
The company can continue working with the same CRM, configuration, data, and more, without having to set up the solution again.
The solutions
- Tenant-to-tenant migration
Tenant-to-tenant migration: Moving CRM instance(s) from the current tenant to another tenant in connection with corporate restructuring such as mergers/demergers, etc.
Area and keywords
Other
Limitations
Tenant migration of CRM only includes the “inside” of CRM, and not associated services such as the portal, Azure, or other services.