Power Apps and Power Automate tenant-to-tenant migration

Microsoft recommends the PowerShell for Power Platform Administrators module for the tenant-to-tenant move, and it also gives you the inventory cmdlets. Check the version first: it must be 5.x. If prompted to change the repository InstallationPolicy, type A and press Enter. Add-PowerAppsAccount opens a sign-in window: sign in as a Power Platform administrator of the source.

$PSVersionTable.PSVersion
Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
Update-Module -Name Microsoft.PowerApps.Administration.PowerShell
Add-PowerAppsAccount

Export every environment with its type, then every app and flow with its owner. Create C:\migration first.

Get-AdminPowerAppEnvironment | Select-Object DisplayName,EnvironmentName,EnvironmentType,Location |
  Export-Csv C:\migration\environments.csv -NoTypeInformation
Get-AdminPowerApp | Select-Object DisplayName,AppName,EnvironmentName,@{n="Owner";e={$_.Owner.email}} |
  Export-Csv C:\migration\apps.csv -NoTypeInformation
Get-AdminFlow | Select-Object DisplayName,FlowName,EnvironmentName,CreatedBy,Enabled |
  Export-Csv C:\migration\flows.csv -NoTypeInformation

Record every connection per environment, including custom connectors and on-premises data gateways. None of them move.

Get-AdminPowerAppConnection -EnvironmentName <EnvironmentId> |
  Select-Object DisplayName,ConnectorName,CreatedBy,CreatedTime |
  Export-Csv C:\migration\connections.csv -NoTypeInformation

Pick each environment, open Solutions and open each unmanaged solution to see which apps and flows it contains. Add a "Solution" column to apps.csv and flows.csv. That decides the route in Step 2.

For each app and flow, record SharePoint site URLs, list names, mailbox addresses, Teams channels, HTTP trigger URLs and any Microsoft Forms used as triggers. These all change in the target.

Create every app owner, flow owner and environment user in the target Microsoft Entra ID and assign licences (bulk create users, assign licences). Users not in the mapping file see an empty environment after a move.

For the export and import route, select New, enter the Name, Region and Type, set Add a Dataverse data store to Yes where needed (this cannot be undone) and select Next. Choose Language, URL, Currency and a Security group, then select Save.

Recreate data loss prevention policies so imported apps and flows are allowed to use their connectors. Name the policy, move the connectors your apps use into Business as in the source policy, choose custom connectors and the environments in scope, and create it.

Install and register on-premises data gateways in the target before importing anything that uses them. The steps are the same as in the Power BI guide.

Apps and flows that read SharePoint lists or files should be imported after those sites have moved. See SharePoint cross-tenant migration.

Select each unmanaged solution, select Export, choose Publish all changes and Next, pick Managed or Unmanaged and select Export. Then delete solution-aware canvas apps, custom pages and component libraries: delete managed solutions to remove their apps; use Delete from this environment for apps in unmanaged solutions. Export Copilot Studio agent solutions the same way, and delete Power Pages websites, which you reprovision afterwards.

For each app select More Commands, then Export package (preview), enter the details and select Export. Then delete the app. Admins can also view and delete canvas apps in the Power Platform admin center: Manage > the environment > Resources > Power Apps.

Flows already in Dataverse solutions move with the environment. Add the rest from the Outside Dataverse tab and select Add, or add them in bulk with PowerShell.

Add-AdminFlowsToSolution -EnvironmentName <EnvironmentId> -SolutionId <SolutionId>

Name it usermapping.csv (case-sensitive) with exactly two comma-separated columns, Source and Destination, and no spaces around the header. Every user must exist and be active in both tenants. Each environment needs its own file. If you include administrative access users, the destination users must be licensed or the move fails.

Source,Destination
user1@contoso.com,user1@fabrikam.com
user2@contoso.com,user2@fabrikam.com

Select the environment, then Move environment on the command bar. Enter the destination tenant ID in Target tenant ID and select Submit request. With PowerShell, submit and record the migration ID.

TenantToTenant-SubmitMigrationRequest -EnvironmentName <EnvironmentId> -TargetTenantID <TargetTenantId>
TenantToTenant-ViewMigrationRequest

Select Review moves on the banner, select the environment ID, review and approve. Requests expire after seven days if not approved.

Add-PowerAppsAccount
TenantToTenant-ViewApprovalRequest
TenantToTenant-ManageMigrationRequest -MigrationId <MigrationId>

Select Begin move, upload usermapping.csv and select Validate. With PowerShell, upload the file, copy the read-only container URI from the output, then run prepare and check the status. If validation fails, select Download errors (or open the SAS URL from the status), fix the file and upload it again.

TenantToTenant-UploadUserMappingFile -EnvironmentName <EnvironmentId> -UserMappingFilePath C:\migration\usermapping.csv
TenantToTenant-PrepareMigration -MigrationId <MigrationId> -TargetTenantId <TargetTenantId> -ReadOnlyUserMappingFileContainerUri <SasUri>
TenantToTenant-GetMigrationStatus -MigrationId <MigrationId>

Select Move environment, review the pre-move steps, tick the confirmation and select Move environment. Run the move within seven days of a successful prepare, or prepare again. Microsoft says to allow up to 24 hours and that a lack of visible progress does not mean failure. You can cancel with Cancel move before it completes.

TenantToTenant-MigratePowerAppEnvironment -MigrationId <MigrationId> -TargetTenantId <TargetTenantId>
TenantToTenant-GetMigrationStatus -MigrationId <MigrationId>

Select each validating admin, Manage security roles, tick System Administrator and Save. Then update security groups, re-enable Managed Environments (with the required licence), update environment settings that were not copied, and reconfigure connections, custom connectors and gateways. Generative AI settings reset to environment defaults.

Select the unmanaged solution and Export. In Before you export select Publish all changes and Next. In Export this solution choose Export as Managed for production targets or Unmanaged if development continues in the target, then select Export. A solution file can be up to 95 MB.

Select Import solution, choose Browse, pick the .zip and select Next. Pick or create a connection for each connection reference and select Next, enter environment variable values that are not already set, then select Import. Unmanaged imports arrive as drafts and must be published.

If the import lists missing dependencies, install them (the import screen links to available updates) and restart the import. If it fails, select Download Log File; Microsoft says the most common cause is missing required components.

Select the app and Export package. Enter a Name and Description, set each resource's import action to Update or Create as new, and select Export. Microsoft says you can only import the exported package; edits to the package file are not supported.

Select Import canvas app, then Upload and the package. Select Import Setup (the wrench) for each resource and choose Create as new or Update. For connections choose Select during import and pick or create the target connection. Select Import. Choosing Update on an existing app saves a draft that you must publish.

Repoint SharePoint, Dataverse and SQL data sources to target locations, re-add gateway connections, reconfigure any flows associated with the app, publish, and share the app again with target users and groups.

Solution-aware flows move with their solution or with an environment move. Add existing flows from the Outside Dataverse tab, or use Add-AdminFlowsToSolution, all at once or by flow ID.

Add-AdminFlowsToSolution -EnvironmentName <EnvironmentId> -FlowNames <flowId1>,<flowId2> -SolutionId <SolutionId>

Flows in solutions should use connection references rather than direct connections. After import, open the solution, go to the connection references and reauthenticate or link each one to a target connection. If a flow will be turned on by another user, share the connection with them (Connections > the connection > Share > Can use).

Environment variables hold values such as SharePoint site URLs and list names. Remove the current value from the solution before export so it stays in the source, then enter the target value on import. Values are limited to 2,000 characters. For SharePoint data source variables, column display names and logical names must match between source and target.

For a one-off move of a flow outside a solution, select the down arrow next to Export, choose Package (.zip), enter a name and select Export. In the target select Import > Import Package (Legacy), Upload the .zip, set Create as New or Update under IMPORT SETUP, choose connections under Related Resources and select Import. Only the owner or a co-owner can export, and the importer needs the Environment Maker role. If the target has Create in Dataverse solutions turned on, you cannot import packages with non-solution flows and must use solution import.

Imported flows are off. Turn on child flows before the parent flows that call them.

Flows triggered by HTTP requests get new URLs after import; copy the new URL from the trigger and update every caller. Flows triggered by Microsoft Forms, SharePoint lists or shared mailboxes must be edited to use the target resources.

Have each app and flow owner test in the target with real accounts. Check sharing, connections, run history of a test run, and that data lands in the target locations.

Turn off source flows, remove source app sharing or set a message in the app pointing to the new one, and send users the new links.

After validation, select the ellipsis next to the orphaned source environment, select Delete, provide the confirmation and select Confirm. Microsoft says to do this only once you have confirmed the data is no longer needed in the source tenant.