Power Platform Tenant Migration After an Acquisition
Global insurance and financial services group
In short
How do you move hundreds of Power Automate flows after an acquisition?
After the client acquired a US risk services business, hundreds of Power Platform flows sat in one default environment with no full list, no clear owners and no plan to move them. More than half were switched off, and about four in five belonged to a single account. We inventoried everything, agreed what to move, and delivered a three-wave migration that was sized and scheduled.
Results in numbers
- flows nominated to migrate
- 256
At a glance
- 256 flows and 21 apps scoped for migration
- A three-wave migration of 1,543 hours
- Every flow reviewed and nominated before the move
The client
The client is a global insurance and financial services firm that grows through acquisition. Its newly acquired US risk services business had built its automation in the default Power Platform environment of its own Microsoft 365 tenant, with flows going back to 2018. Most used SharePoint, Outlook and SQL Server.
What it was costing them
- Unknown scope: nobody held a full list of flows, apps, connectors and owners, so the move could not be sized.
- Key-person risk: one account owned 204 of 257 flows.
- Clutter: 157 of 257 flows were switched off and 79 had not changed since 2019.
- Hidden dependencies: flows pointed to SharePoint lists by identifier, and those identifiers change in a new tenant.
What we did
We inventoried every flow, app and connection, agreed what should move, and ran the migration in three waves.
- A full picture before any move: an export script and a flow listed every app, flow, connector, solution and owner.
- Nothing moves by default: each component was marked Migrate, Ignore or Other, so the business chose what was worth moving.
- Dependencies made visible: the SharePoint sites and lists behind each flow were traced, so target equivalents could be mapped.
- Repeatable packaging: each flow and app goes into its own solution, with hard-coded values as environment variables and connections as connection references.
- Safer imports: a technical account runs the imports, so no personal account becomes the owner.
- Hard cases covered: SharePoint form apps cannot be exported from the admin centre, so a manual export and re-import route was defined.
- A migration sized and tracked: the work came to 1,543 hours across migrate, test and cutover waves, with flow and app checks after each import.
Results
- All 256 flows were nominated for migration on 21 March 2023.
- The migration ran in three waves, migrate, test and fix, and cutover, sized at 1,543 hours.
- SharePoint appeared in 194 of 255 flows, Outlook in 118 and SQL Server in 79, which showed where the dependencies were.
The risk most teams miss
The month-three risk is the flow nobody remembers. A switched-off flow can still be someone's monthly report, and a flow tied to one person's connection stops when that person leaves. The nomination step and the technical account handle this. After cutover we keep the old tenant read-only for an agreed period and watch failed runs daily.
What we would add today
Improvements we would add on top of what is live.
- Replace the single default environment with development, test and production environments in an environment group, with Managed Environments rules.
- Move solutions with Power Platform pipelines, connection references and a service principal instead of a person's account.
- Keep the inventory alive with the Center of Excellence Starter Kit rather than a one-off export.
- Read secrets from Azure Key Vault where a flow handles stored credentials.
Technology
Power Automate, Power Apps, Dataverse solutions, SharePoint Online, SQL Server, Power Platform admin PowerShell, Microsoft 365.
Tell us how many flows and apps sit in your acquired company's default environment, and we will tell you what it takes to move them safely.
Products and capabilities
- Power Automate
- Power Apps
- tenant migration
- environment strategy
- flow inventory
- solution packaging
The service behind this work
Power Platform governanceMore on this industry
Banking and finance
Related use cases
IT and platform teamsPower Platform Operating Model and Governance Framework
When Power Platform spreads across countries without a plan, licence costs, security gaps and duplicated apps follow. The client already ran one Power Platform app and needed to grow safely. We put a five-pillar operating model in place that splits duties between global IT and the countries.
Power Platform Governance and Centre of Excellence
The clients had let the Power Platform grow faster than its rules. About 100 canvas apps, 5 model-driven apps and 250 flows were in use, and the firm itself described that use as largely ungoverned. We set up formal governance and a Centre of Excellence, so the firm keeps the speed of low-code and protects client data.
- c. 100
- canvas apps analysed
- 250
- flows analysed
Power Platform Governance Kickstarter
The client was building on Power Platform in several countries without agreed rules for environments, data policies or ownership. Each month without governance meant more apps and flows to untangle later. We ran a governance kickstarter that trained the administrators, set a security baseline, deployed the Centre of Excellence Starter Kit and documented the strategy.
- 4
- programme phases
- 6 hrs
- Admin in a Day
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.