#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 the Create a Project and Create Migration Mappings for details. Use the mapping file of data to be migrated to configure the migration project.

#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

Some issues may occur during a full migration job. Run an incremental job to handle new, updated, and failed data. Refer to Run Migrations to Migrate Objects about how to perform regular incremental migrations.

#4. Communicate with end users (optional)

Notify end users of the migration schedule. Publish a message in each source Group to inform end users that they can run incremental jobs before final validation.

#5. Perform the final incremental migration

Notify all users and make sure the source Groups do not have any new/modified objects. Then perform the final incremental migration job.

#6. Validate migration results

Note the following items during the validation period:

• Number of files

• Number of mails in Group mailbox

• No failed data in job report

#7. Perform migrations for all other waves (optional)

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

#8. Perform the final incremental migration for other waves (optional)

You can perform the final incremental migration to make sure all source data are migrated to the destination if needed.

#9. Perform the final validation

During the final validation, you should validate members of the destination Google Groups.