Contents
To address these issues, Microsoft came up with separate API for migrations named O365 Migration API. This API leverages Azure and boosts the migration speed like ever before and the throttling effect will be greatly reduced, so users can use SharePoint sites without any performance issues even at the time of heavy migrations.
To import your content from file shares to SharePoint Online using this API, you can click here. The Site, List Schema cannot be created with this API. Only content can be migrated. So, to migrate them, you must depend on any third-party tools or custom coding. A maximum package size restriction applies.
How to migrate content from SharePoint to Azure?
The timer jobs in Azure will pick your content and migrate them to SharePoint Online. Let’s review the process: Prepare a package (Content Package) of items/files that you wish to migrate and another package (Manifest Package) of XML files that define metadata, relations, and settings for your migration.
The job will consume a well formed (pre-defined format) import package that is located in the Azure Blob Storage Containers specified in this method. The SLA for migration job processing is be controlled through pre-configured queue and work load throttling settings, and there is no guaranteed SLA or return time for a submitted job.
How does asynchronous metadata read improve migration performance?
The goal of the new Migration Asynchronous Metadata Read (AMR) API is to reduce the number of calls, reduce throttling, and improve overall migration performance for our customers. Instead of calling thousands of calls to query information from SPO, the new Migration Asynchronous Metadata Read can return the same amount of data in a single read.
Is there an AMR API for SharePoint migration?
The AMR API also has the ability to load balance the server, and supports an unlimited amount of metadata to be migrated. This document targets ISVs and any third-party vendors/developers who are developing and maintaining a migration tool.
What is a highwater mark in migrate API?
Highwater marks allow Migrate API to track changes so that we can migrate only content that has been created or updated in the source since the migration was previously executed. This requires the source to have a special highwater property. This can be any property that indicates the highest value migrated so far.