#Migration Execution

Refer to the following sections to execute the migration.

#1. Configure projects and mappings in Fly

To configure projects and mappings, refer to Create a Project and Create Migration Mappings for details.

#2. Perform regular full migrations

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 Migrations to Migrate Objects for details.

#3. Perform regular incremental migrations

Handle new, updated, and failed data. Refer to Run Migrations to Migrate Objects about how to perform regular incremental migrations.

#4. Validate migration results

Check the following:

• 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.

• Migrated data in the destination.

• Item count and permissions in the destination.

• Linkage between the organizer and the attendee.

• New data can be created in destination mailboxes.

• Functions can work normally, such as mail reply, forward, etc.

• Meeting/recurrence meeting functions work normally.

#5. Perform the final incremental migrations for current wave

Ensure all source data are migrated to the destination.

#6. Perform migrations for all other waves

This step is only needed if you have separated the migration plans into multiple waves.

#7. Finalize and clean up

• Export final reports.

• (Optional) Remove completed mappings.