Information about the Migration Progress
For running mappings, the percentage of migration progress may be affected by many factors, such as the source data structure, migration policy, and API limitations. Refer to the following sections for the factors of different platforms.
Exchange Online / Exchange On-Premises Migration
For Exchange migrations, the percentage of migration progress is calculated based on the migrated mailbox size and total mailbox size. The calculation of the migration progress may be affected by the following factors:
- Microsoft API limitations – Fly uses Microsoft APIs to retrieve the total size of mailboxes. However, the total mailbox size retrieved by Microsoft APIs may be inconsistent with the actual total mailbox size due to Microsoft API limitations.
- Migration policy – You may have configured the migration scope to filter out some data for the migration job. Therefore, the size of the actual mailboxes to be migrated is smaller than that of the retrieved total mailboxes. The displayed progress will be slower than the actual progress.
Microsoft Teams Migration
For Microsoft Teams migrations, the percentage of the whole migration progress is calculated based on the progress of the Team sub job, mailbox sub job, team site sub job, and channel site sub jobs.
*Note: The number of migrated conversations cannot be retrieved due to API limitations. If the source has many conversations, the calculation of the migration progress for Team sub job may be affected.
Microsoft Teams Chat Migration
For Microsoft Teams Chat migrations, the percentage of the whole migration progress is calculated based on the progress of the chat message sub job and chat file sub job. The calculation of the migration progress may be affected by the following factors:
- The number of chats, chat messages, and chat members cannot be retrieved at the initial stage of the migration due to API limitations. If the source has many objects above, the migration finish time cannot be predicted.
- The number of chat files cannot be retrieved due to API limitations. If the source has many files, the migration finish time cannot be predicted.
SharePoint Online Migration
For site collection/site level migrations, the percentage of migration progress is calculated based on the size of migrated site collections and total size of site collections. The calculation of the migration job progress may be affected by the following factors:
- Microsoft API limitations – Fly uses Microsoft API to retrieve the total size of site collections. However, the total size of site collections retrieved by Microsoft API may be inconsistent with the actual total size of site collections due to Microsoft API limitations.
- Migration policy – You may have configured the filter policy for the migration job to filter out some data. Therefore, the size of the actual site collections to be migrated is smaller than that of the retrieved total site collections. The displayed progress will be slower than the actual progress.
- Post-migration – After migrating source data to the destination, Fly will update the properties of migrated data on the backend, such as the properties of lookup up columns. During this process, Fly cannot calculate the migration progress. If there is too much data to be updated, the migration progress may be stuck until the update is completed, and the progress will be updated to 100%.
For folder level migrations, there is no Microsoft API can retrieve the total data size and item counts of the folders. Fly cannot accurately estimate the duration of folder migrations. This will affect the accuracy of the calculation of the migration process.
For library level migrations, the percentage of migration progress is calculated based on the size of migrated libraries and total size of libraries. The calculation of the migration job progress may be affected by the following factors:
- Microsoft API limitations – Fly uses Microsoft API to retrieve the total size of libraries. However, the total size of libraries retrieved by Microsoft API may be inconsistent with the actual total size of libraries due to Microsoft API limitations.
- Migration policy – You may have configured the filter policy for the migration job to filter out some data. Therefore, the size of the actual libraries to be migrated is smaller than that of the retrieved total libraries. The displayed progress will be slower than the actual progress.
- Post-migration – After migrating source data to the destination, Fly will update the properties of migrated data on the backend, such as the properties of lookup up columns. During this process, Fly cannot calculate the migration progress. If there is too much data to be updated, the migration progress may be stuck until the update is completed, and the progress will be updated to 100%.
For list level migrations, the percentage of migration progress is calculated based on the count of migrated items and total item count. The calculation of the migration job progress may be affected by the following factors:
- Microsoft API limitations – Fly use Microsoft API to retrieve the total item count. However, the total item count retrieved by Microsoft API does not contain the count of all versions of the items. This may affect the accuracy of the calculation of the migration progress percentage.
- Migration policy – You may have configured the filter policy for the migration job to filter out some data. Therefore, the count of the actual items to be migrated is less than the retrieved total item count. The displayed progress will be slower than the actual progress.
- Post-migration – After migrating source data to the destination, Fly will update the properties of migrated data on the backend, such as the properties of lookup up columns. During this process, Fly cannot calculate the migration progress. If there is too much data to be updated, the migration progress may be stuck until the update is completed, and the progress will be updated to 100%.
OneDrive Migration
For OneDrive migrations, the percentage of migration progress is calculated based on the size of migrated OneDrive sites and total size of OneDrive sites. The calculation of the migration job progress may be affected by the following factors:
- Microsoft API limitations – Fly uses Microsoft API to retrieve the total size of OneDrive sites. However, the total size of OneDrive sites retrieved by Microsoft API may be inconsistent with the actual total size of OneDrive sites due to Microsoft API limitations.
- Migration policy – You may have configured the filter policy for the migration job to filter out some data. Therefore, the size of the actual OneDrive sites to be migrated is smaller than that of the retrieved total OneDrive sites. The displayed progress will be slower than the actual progress.
Gmail Migration
For Gmail migrations, the percentage of migration progress is calculated based on the number of migrated emails and items. The calculation of migration progress may be influenced by the following factors:
- Google API limitations – Fly uses Google API to retrieve the total number of the items. However, the total number of items retrieved by the Google API may be inconsistent with the actual number of items due to Google API limitations.
- Migration policy – You may have configured the migration scope to filter out some data for the migration job. Therefore, the count of the actual items to be migrated is less than the retrieved total item count. The displayed progress will be slower than the actual progress.
Google Drive Migration
For Google Drive migrations, the percentage of migration progress is calculated based on the number of migrated objects, including folders, files, and file versions. The calculation of migration progress may be influenced by the following factors:
- Google API limitations – Fly uses Google API to retrieve the total number of objects. However, the total number of objects retrieved by the Google API may be inconsistent with the actual number of objects due to Google API limitations.
- Migration policy – You may have configured the filter policy for the migration job to filter out some data. Therefore, the count of actual objects to be migrated is less than the retrieved total object count. The displayed progress will be slower than the actual progress.
