About the delivery
ProsessPilotene delivered a tenant-to-tenant migration for Kongsberg Maritime (2026).
Project Copenhagen.
Kongsberg Discovery will be spun off from Kongsberg Maritime.
The solution will be copied, and the copy's tenant will be migrated from masterX to grandX.
The solution will continue to exist separately in both the new and the old tenant.
It took 13 hours to copy the solution, which was approximately 1.5 TB, while the tenant migration itself was completed in just under half an hour.
Numerous and complex integrations and lots of projects. It was helpful to have well-documented test cases to check what worked and what didn’t.
Integration testing caused problems. No one had a complete understanding of how the various integrations were connected, and many different people had to be involved in end-to-end testing. Access to the ERP side was granted very late, so the CRM tests ended up being rather brief and fragmented.
Many risks materialized: scope creep in the delta migration, limited availability of testers, no one with a complete overview, inadequate test cases, etc.
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 changes 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.