#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 Mappingsfor 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 Objectsfor 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 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 migrated data in the destination.

• Check the item count in the destination.

• Check the linkage between the organizer and the attendee.

• New data can be created in destination mailboxes.

• Meeting/recurrence meeting functions work normally.

#5. Perform the final incremental migrations

Ensure all source data are migrated to the destination.

#6. Reduce DNS TTL

​It is recommended to reduce the DNS time-to-live (TTL) to one hour or below to reduce the delay of emails sent from people outside of the organizations on cutover.

#7. Perform the final cutover

Modify Exchange MX records, etc. It can take up to 72 hours (related to the TTL mentioned in the previous section) for your email systems to recognize the changed MX records. We recommend you run a final incremental job after the cutover to ensure updates of source data are migrated to the destination. Make sure the source email addresses in project mappings are not modified, and the destination email addresses in project mappings exist as aliases of the original destination email addresses.