#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. 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. Perform the final incremental migration

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

#5. Run a complete migration job (optional)

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

You also can select the Replace outside attachment URLs option to replace external attachment URLs.

#6. Perform the replace 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 URLs for attachments in the current user's Teams Chat Files folder can be replaced.

If your source Teams Chats 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. 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.

#8. Validate migration results

Check the following items during the validation period:

• Number of messages

• Number of files

• Format of conversations

• Destination space members