Run Migrations to Migrate Objects
When your 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 objects of the source Teams if you run migrations for the mappings the first time.
In the Full migration panel, you can view whether your purchased user seats/Teams are sufficient for migrations. If the available user seats/Teams are sufficient, Sufficient subscription is displayed in the panel; if the available user seats/Teams 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 or retry error objects for the mappings.
- **Incremental migration** – Only migrate newly created or modified source objects since the last migration, and error and warning 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.
- **Retry** **error** **objects** – Only migrate the error objects in previous migrations to the destination.
> ***Note**: You can run this job for a migration job that is finished with exceptions to retry the error and warning objects. If the migration job is failed, you need to rerun a full or incremental migration job.
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.
During the whole migration process, we do not recommend you change the data structure. For example, rename, delete, or move source files/folders or rename source channels. If you want to change the data structure, there are some notes that need your attention:
- Before you run an additional full migration job for the project that has run a full migration job, note the following issues:
- If you rename or move folders in the source, the links to the folders migrated to the destination cannot be opened in the destination.
- If you rename channels in the source or destination, Fly will create new channels in the destination. Data of source channels that have been migrated in the last job will be migrated again to the newly created channels.
- Before you run incremental migration jobs, note the following issues:
- If you rename channels in the source or destination, Fly will create new channels in the destination. New files in source channels can be migrated to the newly created channels. However, files that have been migrated in the last job will not be migrated to the newly created channels, and links to or tabs associated with those files cannot be opened in the destination.
- If you move source files to another library of the same team site, the migration of these files will fail, and the previously migrated files in the destination will not be moved to the new library.
- If you delete source files/folders, the previously migrated files/folders in the destination will not be deleted synchronously.
- Without enabling channel mapping, the data from the first channel will be migrated to the destination's first channel. After a full job, if you rename the destination's first channel, during the incremental job, the data from the first channel will still migrate to that renamed destination channel.
For Microsoft Teams to Microsoft Teams migrations, note the following:
- After the migration, it is recommended not to rename the source channels and destination channels. Otherwise, conversation links and tabs cannot function correctly. Moreover, the incremental job will create a new destination channel if you do not update the corresponding channel mapping.
- If both the source and destination have a General (other than the first channel) folder and a first channel folder, data from the source General folder will be migrated to the destination General folder, and data from the first channel folder will be migrated to the destination first channel folder. If only the source has a General (other than the first channel) folder and a first channel folder, and the destination Team is newly created, data from both folders will be migrated to the destination General channel.
- For 21Vianet tenants, to ensure users can successfully sign in to the destination Teams after the migration, they need to enable Multi-Factor Authentication (MFA) in Microsoft Entra admin center and register their phone numbers.
