Migrating an acquisition into the parent tenant

Our summary

We inventoried the source tenant with PowerShell before planning any moves, then migrated four workload types into the parent tenant in five months.

The situation

A multinational food manufacturer acquired a smaller producer. Two Microsoft 365 tenants had to become one, and nobody had a reliable list of what was in the source tenant.

Acquisition migrations run on someone else’s timetable. Discovery has to be fast and it has to be right.

Discovery first

We wrote and ran PowerShell scripts to inventory SharePoint Online sites, OneDrive accounts, Teams and Power Platform workloads, including Power Apps, Power Automate and Power BI assets, so migration planning rested on evidence rather than assertion.

We then ran stakeholder workshops to assess the criticality of each component and choose its migration pathway, and worked directly with site owners to identify SPFx customisations supporting mission-critical processes.

The hard integration

We designed the replacement for a Layer 2 Cloud Connector that synchronised on-premises SQL Server data with SharePoint lists used by Power Platform solutions.

We also presented the client with options for Zero Trust architecture, document classification with sensitivity labels, and DLP for the combined tenant.

The result

The acquired business’s SharePoint, OneDrive, Teams and Power Platform workloads moved into the parent tenant over five months.

Every component was assessed for criticality before it moved, including the SPFx customisations behind mission-critical processes.