Fly provides multiple customized features for Power Platform Migration. Refer to the following information to use the features:
- **IsRemoveServiceAccount** **–**Define whether to remove the service account from the co-owner of apps/flows.
If the service account does not have permissions to apps or flows, Fly will automatically add the service account as the co-owner of the apps or flows to migrate the apps or flows. If you want to remove the service account from the apps/flows after the migration, you can add the **IsRemoveServiceAccount=true** feature string to the **Customized features** section. Fly will remove the service account after migrating the apps or flows.
- **RemoveSPViewIdFromFlow** – Define whether to remove the SharePoint views from destination flow triggers.
By default, Fly will not remove the SharePoint views from destination flow triggers. If the destination does not have views with the same name as the views configured in source flow triggers, the source flows cannot be migrated. To ensure the source flows can be migrated, we recommend you add the **RemoveSPViewIdFromFlow=true** feature string to the **Customized features** section to remove the SharePoint views from destination flow triggers.
- **TrimWhiteSpaceForPowerAppsAndFlowName=true** – Define whether to trim whitespace when the Power app/flow name starts or ends with whitespace during app/flow name validation.
- By default, trailing spaces in the Power Apps or Flow name are removed after saving the mapping. This may cause discrepancies in the app/flow names and result in a failure in the Power Platform migration job. To ensure the migration job runs successfully, we recommend you add the **TrimWhiteSpaceForPowerAppsAndFlowName=true** feature string to the **Customized features** section. Fly will trim the whitespace from the app/flow name after retrieving it from Microsoft, then compare it with the flow name in the mapping.
