What's new in the Migration API

Check here to see what features or updates have been added to the Migration API. Here's a summary of what's included.

Updated reason code and descriptions

We have updated Migration API to provide detailed reasons in case a job is postponed. We encourage ISVs take appropriate actions, based on the reasons.

Possible reasons	Code	Description
JobInQueue:Resource	1，2，3，4, 5, 6, 12	The job is now in a queue for resource allocation. It is expected to start in [P75] time.
JobInQueue:DBMaint	7	The destination tenant's database is currently in maintenance. The job is in a queue to be executed when the maintenance is completed. We expect the maintenance to be completed at [P75] time.
JobFailure:TenantBlock	10	Migration is blocked at the destination tenant. The job is cancelled. Please check tenant status before resubmitting.
JobCancelled:Unknown	11	The migration job is canceled for unknown reason.

New: Speed up small file migration

The migration package includes multiple files, which are each uploaded/downloaded individually. If you have a large number of small-sized files, migration speed drops dramatically. By using the new ArchivedFiles.XML file in your prime package you can transfer files in batch resulting in a faster migration. Learn more about using the ArchivedFiles.XML

SourceType field required

Beginning April 1, 2023, the SourceType field is mandatory when calling the Migration API. Starting October 1st, 2022, a warning message will be sent if the field is missing.

To learn more, including examples, see: SharePoint Import Migration API - ExportSettings.xml

Fixes

• Changes to how Import API handles users. As a response to issues arising from broken OneDrive scenarios when importing duplicate users, the API now blocks and detect duplicate user entries in UserGroup.xml. For details see: Entering user identifiers in UserGroup.xml.