Home > Power Platform Migration Process > Migration Execution
Export to PDFBased on your source inventory report, you need to prepare a final mapping file to list the mappings of source data and destination location. As you may have a heavy load of content to migrate, we recommend you separate your mappings into multiple waves according to your departments for easy management. Keep communicating with users about the migration status.
To configure projects and mappings, refer to Create a Project and Create Migration Mappings for details.
Before running the job, we recommend you verify the mappings to ensure that the mappings are available for migration. Refer to Pre-analyze Mappings for details.
Then you can run a full migration job to migrate the objects based on your configured migration policy. Refer to Run Migration to Migrate Objects for details.
Handle new, updated, and failed data. Refer to Run Migration to Migrate Objects for details.
Check the mapping report. If the mapping fails or finishes with exceptions, you can check the error code and comment for the mapping in the Migration error section. You can click the error code to view the details and recommendations of the code in the Troubleshooting Guide, which can assist you in resolving or avoiding the error.
Check the following data that are migrated to the destination environment:
Flow/App triggers and actions
Flow/App settings
Flow/App permissions
After the migration, the destination connection users need to manually allow the connections for the Power Apps in the destination if the apps are accessed the first time. This is a requirement from Microsoft.
Perform the final incremental migration job to ensure that all source data are migrated to the destination.
This step is only needed if you have separated the migration plans into multiple waves.