#Prepare for Migrations

Before performing Power Platform migrations in Fly, follow the instructions below to prepare for the migration:

1. Build the inventory on your source Power Platform environment.

   • Numbers of Power Apps/Power Automate flows

   • Connection types and corresponding connection users used by the Power Apps/Power Automate flows

2. To migrate source Power Apps/Power Automate flows and corresponding permissions, prepare a service account for both Fly source and destination connections with required permissions. Refer to Required Permissions for Power Platform Migration for details.

   Additionally, you must use the destination service account to create Power Platform connections with the same type as the source connections in advance.

   After the migration, the destination apps/flows will be connected to the connections created by the destination service account. In this case, we recommend you inform the end users of the destination apps/flows to update the connections to their own connections if necessary.

3. To find and automatically map the trigger/action parameters of the source and destination tenants, prepare an app profile for both Fly source and destination connections with required permissions. Refer to Required Permissions for Power Platform Migration for details.

4. Make sure the objects configured in the source trigger/action parameters can be found in the destination. For example:

   • If the parameters are configured with a site collection and a list, the destination must have a site collection with the same relative URL as the source site collection, and has a list with the same title as the source list.

   • If the parameters are configured with a Team and a channel, the destination must have a Team with the same email address as the source Team, and has a channel with the same name as the source channel.

   • If the parameter is configured with an Exchange mailbox folder, the destination mailbox must have a folder with the same name as the source folder.

     To ensure that the source parameter can be mapped to the destination parameter, the destination tenant must have a user with the same user principal name prefix as the source mailbox user; or you can configure Power Platform connection mappings to map the source connection users to corresponding destination connection users.

5. Fly does not automatically provision new users/groups in Microsoft 365. Make sure the destination users/groups already exist before the migration.

   There are different ways to add new Microsoft 365 users/groups:

   • Adding users individually. See instructions .

   • Adding users in bulk. See instructions .

   • Adding users via PowerShell. See instructions .

   • Synchronizing users from local Active Directory to Microsoft 365 via Microsoft Entra Sync or Microsoft Entra connect. See instructions .

6. Your users will receive notifications during the migration in the following situations.

   • When migrating Power Automate flows:

     • If the source or destination service account is not the owner or co-owner of source flows, the service account will be added as a co-owner to source or destination flows during the migration, and will receive an email notification.

     • Destinations users, which are configured in user mappings or mapped by auto-map options enabled in the migration policy, will receive email notifications while being added to the destination flows. Note that the destination service account will not receive email notifications while being added to the destination flows.

   • When migrating Power Apps:

     • Destinations users, which are configured in user mappings or mapped by auto-map options enabled in the migration policy, will receive email notifications while being added to the destination apps. Note that the destination service account will not receive email notifications while being added to the destination apps.