#Migration Execution

Refer to the following sections to execute the migration based on the migration modes.

• Classic mode – The destination spaces already exist.

• Advanced mode – The destination spaces will be created during the migration but not completed.

#Classic Mode (Space exists)

Refer to the following sections to execute the migration with the classic mode:

#1. Configure projects and mappings in Fly

To configure projects and mappings, refer to Create a Projectand 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 migration 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 Team to inform end users that they can run incremental jobs before final validation.

#5. Perform the final incremental migration and migrate membership

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

After you complete your migrations but the source membership is not included in the migrations, to make the destination Team available for users, you can run a Migrate membership job to only migrate the source membership, including owners, members, and guests. Refer to the user guide for details.

#6. Perform the replacement of attachment URLs (optional)

After your migration jobs are finished, some attachment URLs may fail to be replaced with the corresponding destination Google Drive URLs, rendering them inaccessible to destination users. To ensure accessibility after the migration, you can run a Replace attachment URLs job.

By default, only URLs of attachments within the current Team sites or channel sites can be replaced.

If your source Teams contain URLs of attachments from other Teams or OneDrive, you can generate URL mapping report to get the inaccessible external attachments and configure URL mappings for them. Then, you can select the Replace external attachment URLs checkbox and run the Replace attachment URLs job to replace their URLs.

#7. Validate migration results

Check the following items during the validation period:

• Number of messages

• Number of files

• Format of conversations

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

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

#9. Perform the final validation

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

#Advanced Mode (Space does not exist)

Refer to the following sections to execute the migration with the advanced mode:

#1. Configure projects and mappings in Fly

To configure projects and mappings, refer to 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 migration 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 Team 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 Teams do not have any new/modified objects. Then perform the final incremental migration job.

#6. Run a complete migration job and migrate membership

Run a complete migration job to make the destination spaces available for end users.

After you complete your migrations but the source membership is not included in the migrations, to make the destination space available for users, you can run a Migrate membership job to only migrate the source membership, including owners, members, and guests. Refer to the user guide for details.

#7. Perform the replacement of attachment URLs (optional)

After your migration jobs are finished, some attachment URLs may fail to be replaced with the corresponding destination Google Drive URLs, rendering them inaccessible to destination users. To ensure accessibility after the migration, you can run a Replace attachment URLs job.

By default, only URLs of attachments within the current Team sites or channel sites can be replaced.

If your source Teams contain URLs of attachments from other Teams or OneDrive, you can generate URL mapping report to get the inaccessible external attachments and configure URL mappings for them. Then, you can select the Replace external attachment URLs checkbox and run the Replace attachment URLs job to replace their URLs.

#8. Perform incremental migrations for other waves (optional)

If there are new or modified objects in the source after the complete job, you can perform the incremental migrations to make sure all source changes are migrated to the destination.

#9. Validate migration results

Check the following items during the validation period:

• Number of messages

• Number of files

• Format of conversations

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

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

#11. Perform the final validation

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