AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

    Home > Perform Power Platform Migrations > Create a Migration Policy

    Export to PDF

    Create a Migration Policy

    A Power Platform migration policy allows you to define the conflict resolution for apps and flows, how to map Power Platform connections, and how to map SharePoint sites/Teams configured in flow triggers.

    Refer to the following steps to configure a migration policy for Power Platform migrations:

    1. Click Policies under Settings in the left pane.

    2. Click Migration policies to access the Migration policies page.

    3. Click the Power Platform tab.

    4. Click Create migration policy. The Create migration policy panel appears.

    5. Enter a name and an optional description for the policy, and then click Next.

    6. In the Conflict resolution section, configure the conflict resolution when the source app or flow conflicts with an existing one in the destination.

    ResolutionConflictNo Conflict
    SkipIgnore the conflicting app or flow and do nothing in the destination.A new app or flow will be created.
    OverwriteOverwrite the conflicting app or flow in the destination with the source app or flow.A new app or flow will be created.

    1. Click Next to continue.

    2. In the Options section, select the Turn on migrated Power Automate flows in the destination option if you want to turn on the migrated flows. If you do not select the option, the migrated flows will be turned off.

    3. In the Mappings section, configure the following mappings for the migration:

      • User mapping – With a user mapping, you can map a source user/group to a destination one. You can also map a domain in the source to a destination domain. Users, permissions, and user-related parameters can be migrated based on user mappings. Click the Add (Button: Add button) button to create a new one. Refer to the Create User Mappings section to view how to create a user mapping.

        You can also select a previously created user mapping from the drop-down list and click View details to view the detailed information of the selected user mapping. You can enter the keyword of a user mapping in the Search user mapping text box and press Enter on the keyboard to search the user mapping.

        *Note: For the users/groups that have not been configured in user mappings, you can choose to map the users/groups based on User principal name prefix, Display name, and/or Email address prefix. Refer to the table below for property examples:

    PropertyUser Principal NameUser Principal Name PrefixDisplay NameEmail AddressEmail Address Prefix
    Property ExampleJohnSimon@onmicrosoft.comJohnSimon@JohnSimonJohnSimon@onmicrosoft.comJohnSimon@
    - Switch on/off the button of each property to configure whether you want to map users based on that property. - Click the Up or Down button of a property to configure the sequence for mapping users. > ***Note**: If all properties are disabled, user mappings are required. - **Power Platform connection** **mapping** – By default, Fly will automatically map the Power Platform connection used by source apps/flows to destination connections with the same connection type and name. You can also configure custom Power Platform connection mappings to map the source connections to your target connections. Click the Add (![Button: Add button](/en/fly-user-guide/perform-power-platform-migrations/images/image414.png "Button: Add button")) button to create a new one. Refer to the [Create Power Platform Connection Mappings](#missing-link) section to view how to create a Power Platform connection mapping. You can also select a previously created Power Platform connection mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected connection mapping.). - **Site** **mapping** – By default, Fly will automatically map the SharePoint sites connected to source apps/flows to an existing destination SharePoint site with the same relative URL. You can also configure custom site mappings to map the source SharePoint sites to your target existing sites that will be connected to destination apps/flows. Click the Add (![Button: Add button](/en/fly-user-guide/perform-power-platform-migrations/images/image415.png "Button: Add button")) button to create a new one. Refer to the [Create Site Mappings](#missing-link) section to view how to create a site mapping. You can also select a previously created site mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected site mapping.).

    Team mapping – By default, Fly will automatically map the Teams connected to source apps/flows to an existing destination Teams with the same email address.

    You can also configure custom Team mappings to map the source Teams to your target existing Teams that will be connected to destination apps/flows. Click the Add (![Button: Add button](/en/fly-user-guide/perform-power-platform-migrations/images/image416.png "Button: Add button")) button to create a new one. Refer to the [Create Team Mappings](#missing-link) section to view how to create a Team mapping. You can also select a previously created Team mapping from the drop-down list to use it (Clicking **View details** can view and edit the detailed information of the selected Team mapping.).

    1. In the Customized features section, you can add customized features by entering the corresponding customized feature strings. Click Add customized feature, and then enter a customized feature string to configure a customized feature. Refer to Customized Features for Power Platform Migration for details.

    2. Click Next to continue.

    3. Configure the Notifications setting to send migration email notifications to specific recipients after the migration.

      • Send project level notifications (all mappings within a project) – The migration email notifications are based on the project level, which summarizes the project name and the mapping count of each migration status.

        • Recurrence – Enter a positive integer to define the recurrence days for the notifications.

        • Start date and time – Select a start date and time to send the first notification. The later notifications will be sent at the selected time based on the recurrence.

          If you want to configure the end date and time of the notifications, you can select the Configure end date and time checkbox and select a date and time.

        • Send migration email notifications to – Define the recipients who will receive the notifications.

        • Email template – Create an email template for the notifications by clicking the Add (Button: Add button) button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

      • Send individual mapping level notifications – The migration email notifications are based on the mapping level, which summarizes the migration status, the project name, the source and destination email addresses, the migration start and finish time, and the migration person.

        • Define the notification scope for mappings – Select For failed mappings only to send notifications for the failed mappings only, or select For all mappings to send notifications for all mappings.

        • Send migration email notifications to – Define the recipients who will receive the notifications.

          • Person running the migration – The person who runs the migration will receive the notifications.

          • Additional recipients – Enter the email addresses of other recipients. Separate multiple email addresses with a semicolon (;).

        • Email template – Create an email template for the email notifications by clicking the Add (Button: Add button) button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

    4. Click Save to save the migration policy. After creating the migration policy, you can click Set as default to set the policy as the default policy for migrations.

    On the Migration policies page, you can manage existing policies.

    - Set as default – Select a policy and click **Set as default** to set it as the default policy. Or you can select one policy and click **Set as default**. The default policy will be automatically selected when you create projects. - Edit – Click the policy name link to edit the policy. - Delete – Select a policy and click **Delete** to delete it. You can also select one or multiple policies and click **Delete** to delete them. - Copy – This allows you to quickly create a new policy with similar configurations by completing the following steps: 1. Select your target policy, and click **Make a copy**. You can also open your target policy, and click **Make a copy** on the **Edit migration policy** page. 2. Check the settings and make updates if necessary on the **Copy migration policy** page. 3. Click **Save**.

    Create Power Platform Connection Mappings

    Configure the following settings on the mapping page:

    1. Enter a name and an optional description for the mapping.

    2. In the Power Platform connection mapping section, you can add the Power Platform connection mapping one by one or import multiple mappings in bulk.

      • Add connection mapping – Configure the connection mapping by entering the source connection name and destination connection name into the provided field. Click Add to add additional mappings.

      • Import connection mappings – Click Import. In the Import panel, you can download the template for mapping examples and configure mappings directly in the file; or you can click Export in this section to export a mapping file and modify it. After the configurations, in the Import panel, import the mapping file by dragging the file or browsing the file from the local location. Click Save to save the mappings.

      *Note: To ensure a successful import of destination apps/flows, the destination service account must 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.

      To delete Power Platform connection mappings, select the corresponding checkboxes and click Delete.

    3. Click Save to save the settings for this mapping.

    Create Site Mappings

    Configure the following settings on the mapping page:

    1. Enter a name and an optional description for the mapping.

    2. In the Site mapping section, you can add the site mapping one by one or import multiple mappings in bulk.

      • Add site mapping – Configure the site mapping by entering the source full site URL and destination full site URL into the provided field. Click Add to add additional mappings.

      • Import site mappings – Click Import. In the Import panel, you can download the template for mapping examples and configure mappings directly in the file; or you can click Export in this section to export a mapping file and modify it. After the configurations, in the Import panel, import the mapping file by dragging the file or browsing the file from the local location. Click Save to save the mappings.

      To delete site mappings, select the corresponding checkboxes and click Delete.

    3. Click Save to save the settings for this mapping.

    Create Team Mappings

    Configure the following settings on the mapping page:

    1. Enter a name and an optional description for the mapping.

    2. In the Team mapping section, you can add the Team mapping one by one or import multiple mappings in bulk.

      • Add Team mapping – Configure the Team mapping by entering the source Team email address and destination Team email address into the provided field. Click Add to add additional mappings.

      • Import Team mappings – Click Import. In the Import panel, you can download the template for mapping examples and configure mappings directly in the file; or you can click Export in this section to export a mapping file and modify it. After the configurations, in the Import panel, import the mapping file by dragging the file or browsing the file from the local location. Click Save to save the mappings.

      To delete Team mappings, select the corresponding checkboxes and click Delete.

    3. Click Save to save the settings for this mapping.