Best practices for improving SharePoint and OneDrive migration performance
This article explains the factors that influence performance when migrating content to SharePoint Online and OneDrive.
Migration performance can be impacted by network infrastructure, file size, migration time, and throttling. Understanding these will help you plan and maximize the efficiency of your migration.
Currently, Microsoft's SharePoint Migration Tool (SPMT) as well as several third party vendor tools utilize the SharePoint API for migration. It leverages Azure and uses channels for large content transfer. Regardless of which migration tool you use, these factors will apply. Follow the recommendations listed below for each phase of your migration process.
Planning is the key to optimizing your migration. Determine what content you need to migrate, prioritize when the content needs to be migrated, and decide on what the optimal migration infrastructure should be.
I. Scan the source
The first rule of a good migration is to know your source; evaluate and triage your content before you migrate. What content really needs be migrated? What can be left behind? How many file versions should be included? The amount of content you migrate will determine the overall size of your project.
II. Package the content
This step is where the tool creates a proper package for the content to be imported into the cloud. This step is automated in SPMT and in most third-party tools.
Package size. To improve migration throughput, we recommend that you package at least 250 files per transfer. For the transfer size we recommend a minimum of 100MB and less than 250MB per package. This will result in a faster upload speed to Azure and leverages the scale capabilities of the migration API.
The following table provides estimates of the type of speed you may achieve based on the types of content you are migrating.
|Type of metadata||Examples||Maximum|
||ISO files, video files
||List items, Office files (~1.5MB)
||List items with custom columns, small files (~50kb)
||250 GB /day
Large file size migrates faster than smaller ones. Small file size can result in larger overhead and processing time which directly impacts the performance.
Files migrate faster than objects and list items.
The speed of this step depends on the efficiency of the tool you are using and the type of content that you package. Splitting your packages in a smart way is something that will greatly improve this step. In addition, ensure that your permissions, sharing, or other limits are set up properly for migration and are within SharePoint Online limits and boundaries.
I. Upload to Azure
SPMT or your third-party tool will migrate your content into SharePoint Online using the Migration API, leveraging Azure as a temporary holding place.
If you have a good connection and can configure your datacenter, choose the same datacenter location closest geographically to you for your Azure and your Office 365 account. Migration data throughput is highest during off-peak hours, which are typically nights and weekends in your region's time zone. Your region's time zone is determined by where your Sharepoint Online tenant is set up.
II. The Migration API
The final step of the migration process is when the data is moved from Azure to SharePoint Online. This action is transparent to the user when using SPMT or a third- party tool.
To improve throughput, users are encouraged to run parallel tasks against different site collections if possible. We recommend that you do not submit more than 5,000 migration jobs/requests at one time. Over-queuing the network will create an extra load on the database and slow migration down. Make sure your task has completed before you upload a new migration request. Some tools may already be doing this for you.
During migration, it is not uncommon for your migration task to be throttled. Throttling is implemented to ensure the best user experience and reliability of Sharepoint Online. It is primarily used to load balance the database and can occur if you misconfigure migration settings, such as migrating all your content in a single task or attempting to migrate during peak hours.
For more technical background and information, please see
After the migration is completed, verify that your content has been successfully moved to SharePoint Online or OneDrive.
FAQ and Troubleshooting
Question: My migration is going so slow or I am being throttled. What can I do?
Answer: Check that you have configured your migration settings properly. Turn off any software that you do not need to use during migration. For example, disable any file synchronization program or antivirus program on the migrated content. This will help reduce throttle and improve performance.
Question: How much can I migrate per day?
Answer: Plan to migrate at a maximum of 2TB/day.
Question: I have a very big migration (> 100 TB) and I would like some help, who should I contact?
Answer: For larger than a 100TB migration, please submit a support request with Microsoft. Please include your company name, the estimated migration size, and an estimate of when you would like to start and complete your migration.
Question: I have tried everything, but nothing works. Now what do I do?
Answer: Open a support ticket with http://support.microsoft.com.
We’d love to hear your thoughts. Choose the type you’d like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.