Run Migrations to Migrate Objects
When your Microsoft Teams Chat mappings within a migration project are ready for migrations, you can run migrations for the mappings to migrate objects.
Refer to the following steps to run migrations for mappings:
-
Click Projects in the left pane to access the Projects page, and click the project name of the project you want to run.
-
On the Project mappings page, select one or multiple mappings for which you want to run migrations.
-
Click Migration, and select Full Migration to migrate all chat objects of the source chat users if you run migrations for the mappings the first time.
In the Full migration panel, you can view whether your purchased user seats/chat users are sufficient for migrations. If the available user seats/chat users are sufficient, Sufficient subscription is displayed in the panel; if the available seats/chat users are insufficient, there is an Insufficient subscription warning in the panel.
You can also configure a migration schedule in the panel to run the migration at a specific time.
-
Click Run to run the migration. If you have configured a migration schedule, the migration will run based on your configured time; if you do not configure a migration schedule, the migration will run immediately.
If you have run a full migration for the mappings before, you can also select to run an incremental migration to only migrate newly created or modified source chat objects since the last migration, and error and warning chat objects in previous migrations to the destination.
*Note: The incremental migration job will migrate newly created or modified source SharePoint data based on the audit logs in SharePoint Online. The retention period of audit logs for the data is 60 days. We recommend that you run incremental migration jobs within the retention period.
After the migration of mappings starts, if you want to stop the migration, you can select the mappings and click Stop, then the migration of the selected mappings will be stopped. If you run another migration for the stopped mappings, the migration will start from the beginning.
You can also change the migration schedule of a mapping by clicking the run at [time] link in the Stage column of the mapping; Or change the migration schedule of mappings in bulk by selecting the mappings that have migration schedules, clicking Migration, and clicking Change schedule. In the right panel, select a new schedule to run the mapping based on the new schedule, or select No schedule to stop the migration of the mapping. Click Save to save your updates.
Additional Notes for Teams Chat Migration
- For user’s data in OneDrive, Fly only migrates the files in the **Microsoft Teams Chat Files** folder. During the whole migration process, we do not recommend you change the data structure of the **Microsoft Teams Chat Files** folder. For example, rename, move, or delete the **Microsoft Teams Chat Files** folder, rename or delete files in the **Microsoft Teams Chat Files** folder, or move files out from the **Microsoft Teams Chat Files** folder. If you want to change the data structure before you run an additional full migration job for the project that has run a full migration job, or run incremental migration jobs for the project, note the following issues:
- If you rename, move, or delete files in the **Microsoft Teams Chat Files** folder in the source, links to those files in the destination chats will be unavailable after the next migration job.
- If you rename the **Microsoft Teams Chat Files** folder in the source, after you upload new files in the source, a **Microsoft Teams Chat Files** folder will be recreated. In the next migration job, only the new files in the recreated **Microsoft Teams Chat Files** folder can be migrated. Links to those previously migrated files in the destination chats will be unavailable.
- If you move or delete the **Microsoft Teams Chat Files** folder in the source, links to those files in the destination chats will be unavailable after the next migration job.
- If you simultaneously run the migration mappings for the chat users that exist in the same source chats, to avoid duplicate chats in the destination, Fly will only migrate the chats with the chat user that retrieves the chats first. For example, if user **A** and user **B** both exist in chat **A** and user **A** retrieves the chat first during the migration, Fly will migrate chat **A** with user **A**, and will filter out chat **A** for user **B**. In later migrations under this case, if you only run the mappings of user **B** and not the mappings of user **A**, Fly will migrate chat **A** for user **B** from the last migrated chat message.
- After the migration, if you want to manage the destination chats that are newly created during the migration as follows, you can run the Assist Tool for assistance.
- Keep the placeholder and remove other chat members from specific destination chats if the destination chat members are incorrect due to incorrect user mappings or the chat messages are not the same as the source.
- Remove the consent user and placeholder account from all destination chats if all chats are correctly migrated.
- Remove specific user from all destination chats if the user is incorrect due to an incorrect user mapping.
Refer to [Chat Migration Assist Tool](#missing-link) for more information.
- When configuring user mappings, if you have mapped your source chat members to unexpected destination users, and do not want those destination users to see the destination chats and chat messages, you can refer to steps in [Tool to Hide Chats from Users](#missing-link) to hide the chats from those users.
