Power Platform Migration for a Divestiture
Life sciences and diagnostics company
In short
How do you move Power Apps and flows to a new tenant in a divestiture?
A divestiture comes with a hard date. The apps and flows people use every day must move with the business without breaking. The client had 60 environments, 218 apps and 465 flows to sort before part of the company could stand alone. We inventoried the estate, agreed what should move, and ran a solution-based migration into the new tenant.
Results in numbers
- flows inventoried
- 465
- apps inventoried
- 218
- flows to migrate
- 175
At a glance
- 60 environments, 218 apps and 465 flows inventoried
- 175 flows and 50 canvas apps nominated for migration
- Every moved component packaged in a solution
The client
The client is a life sciences and diagnostics company. Its Microsoft 365 tenant held 60 Power Platform environments, 218 Power Apps and 465 flows, many tied to SharePoint Online. Part of the business was being divested into a new tenant.
What it was costing them
- Unknown estate: nobody could say which of the 218 apps and 465 flows mattered, or who owned them.
- Hidden dependencies: flows pointed at SharePoint sites and lists by address or ID, and both change in a new tenant.
- Owner risk: most components lived outside solutions, and an import makes the importing account the owner.
- Deadline pressure: the divested business needs its automations on day one, with the data structure unchanged.
What we did
We inventoried the source tenant, agreed what to move, and ran a solution-based migration that keeps every flow and app traceable.
- A clear picture of the estate: a flow on the admin actions lists every app and flow with its environment and owner.
- Only what matters moves: owners nominate components, and Teams, trial and developer environments are left out.
- No broken links: a second flow reads the SharePoint sites and lists each component uses and builds a source to target mapping.
- Right owners in the new tenant: co-owners are collected and mapped to their new accounts, so sharing can be restored.
- Repeatable deployment: each flow and canvas app goes into a solution, with hard-coded values turned into environment variables and connections into connection references.
- Safer imports: obsolete connections are removed first, flows stay disabled during data imports, and the solution checker runs before access is given.
- Clear handover: a one-page guide shows owners how to update their own connections.
Results
- Full inventory of the source tenant: 60 environments, 218 Power Apps and 465 flows, including 40 flows deployed from the Center of Excellence.
- 175 flows and 50 canvas apps nominated for migration in the backlog dated September 2023.
- Result: with every component in a solution, later moves between environments take an import and a variable check instead of a rebuild.
The risk most teams miss
The month three risk is connections. Flows imported by a migration account run under that account, some connections cannot be updated on an owner's behalf, and hard-coded values still point at the old tenant. We rated this as high probability. We answered it with environment variables, connection references, a guide for owners and a documented technical owner.
What we would add today
Improvements we would add on top of what is live.
- Place the new tenant under Managed Environments and environment groups, so sharing limits and solution checker apply by rule.
- Release through Power Platform pipelines, with a service principal owning production flows instead of a migration account.
- Keep flow secrets in Azure Key Vault, read through secret environment variables.
- Store the inventory in Dataverse and report it in Fabric or Power BI, so owners and connectors stay current after the move.
Technology
Power Apps (canvas), Power Automate, SharePoint Online, Dataverse, Power Platform admin connectors, solutions with environment variables and connection references, Center of Excellence starter kit, Microsoft Entra ID.
Tell us how many apps and flows sit in your tenant, and we will tell you which ones should move and how.
Products and capabilities
- Power Apps
- Power Automate
- SharePoint
- tenant migration
- divestiture
- solution packaging
- environment variables
- ALM
The service behind this work
Power Platform governance
Related use cases
IT and platform teamsPower 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
Dataverse Housekeeping and Storage Advice
Dataverse capacity costs money, and it fills quietly. Import logs, system jobs and old workflow records grow in the background until an environment runs short. The client asked how to housekeep its environments. We put in place a short routine of checks and clean-ups that frees storage without touching business data.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.