#Run Migrations to Migrate Objects

When your Power Platform mappings within a migration project are ready for migrations, you can run migrations for the mappings to migrate objects.

Refer to the following steps to run migrations for mappings:

1. Click Projects in the left pane to access the Projects page, and click the project name of the project you want to run.

2. On the Project mappings page, select one or multiple mappings for which you want to run migrations.

3. Click Migration, and select Full Migration to migrate all source objects if you run migrations for the mappings the first time.

   In the Full migration panel, you can view whether your purchased apps/flows are sufficient for migrations. If the available apps/flows are sufficient, Sufficient subscription is displayed in the panel; if the available apps/flows are insufficient, there is an Insufficient subscription warning in the panel.

   You can also configure a migration schedule in the panel to run the migration at a specific time.

4. Click Run to run the migration. If you have configured a migration schedule, the migration will run based on your configured time; if you do not configure a migration schedule, the migration will run immediately.

If you have run a full migration for the mappings before, you can also select to run an incremental migration to only migrate newly created or modified source objects since the last migration, and error and warning objects in previous migrations.

After the migration of mappings starts, if you want to stop the migration, you can select the mappings and click Stop, then the migration of the selected mappings will be stopped. If you run another migration for the stopped mappings, the migration will start from the beginning.

To change the migration schedule for a mapping, click the run at [time] link in the Stage column of the mapping; Or change the migration schedule of mappings in bulk by selecting the mappings that have migration schedules, clicking Migration, and clicking Change schedule. In the right panel, select a new schedule to run the mapping based on the new schedule, or select No schedule to stop the migration of the mapping. Click Save to save your updates.

During the whole migration process, we do not recommend you rename flow or apps in the source or destination after a migration job. Otherwise, the flows or apps cannot be found in the next migration jobs, and the migration jobs will fail.