A big migration on one PC can take days, so splitting it across three or four machines looks like the obvious fix. Sometimes it is. Other times every machine just waits longer, because the limit was never the PC. The difference comes down to where the bottleneck sits, and Microsoft's own rules decide most of that.
When more machines make it faster
Extra machines help while each PC is the thing holding the job back. Watch one machine during a run: if its upload is maxed out, its disk is busy, its CPU is pegged, or it is pulling files slowly from a file share, a second PC with its own connection and disk adds real capacity.
- Upload bandwidth. Two offices or two internet links really do move twice the data.
- A file-share or local source. Reading from a slow NAS is often the true limit; a second PC near another share doubles the reading.
- Different tenants. Machines working on different tenants never share a Microsoft budget, so they scale cleanly.
When more machines stop helping
Microsoft limits SharePoint traffic per app, per tenant. Every machine that signs in with the same app registration and certificate draws from one shared budget. Once that budget is used, Microsoft answers with "too many requests" or "server too busy" and a time to wait, and every machine has to back off. More PCs at that point add waiting, not throughput.
Our current estimate is that past three or four machines on one tenant and one certificate, extra PCs mostly buy more throttling. We are measuring that on our own test tenant and will update this page with the result. Throttling cannot be lifted by a support ticket to Microsoft, but Microsoft's guidance is that limits are looser on evenings and weekends, so long runs scheduled then go further.
| Situation | Will another machine help? |
|---|---|
| One PC's upload is saturated | Yes, if the second PC has its own connection |
| Reading from a slow file share | Yes, split the share between machines |
| Runs keep pausing on throttling | No: the tenant's budget is the limit |
| Two tenants to migrate | Yes, one machine per tenant |
| Five or more PCs on one tenant | Rarely: expect more pauses |
How to split the work
- Divide by site collection, or by OneDrive account, or by mailbox. Microsoft's migration guidance also recommends running parallel work against different site collections.
- Never point two machines at the same destination site. They compete for the same limits and can collide on the same folders and files.
- Use the same app registration on every machine. When ShareMaster asks about the certificate on a second PC, choose to use an existing app registration and give it the same certificate (PFX). One registration is simpler to manage and to remove afterwards.
- Keep a list of who runs what, so a site is never started twice and every one is covered.
What each machine does on its own
The machines do not talk to each other. Each one watches its own replies from Microsoft and pauses when it is told to wait, then carries on. That keeps every machine within the rules, but it also means one busy machine can slow the others down without anyone seeing why. If every run pauses often, fewer machines will usually finish sooner.
Job history, reports and the information needed to resume an interrupted job stay on the machine that ran the job. Resume a job on the PC that started it. If a team needs one view of the whole migration, save each run's reports to a shared folder as you go.
Common questions
Will four PCs migrate four times faster than one?
Only while the PC is what holds the job back. Against one tenant, machines on the same certificate share one Microsoft budget, so the gain shrinks quickly once throttling starts.
Can two machines copy into the same SharePoint site?
Avoid it. Give each machine its own destination site collection, OneDrive or mailbox.
Do the machines share one job history?
No. Each machine keeps its own. Save reports somewhere shared if you need one picture.
Sources
- Microsoft Learn: Avoid getting throttled or blocked in SharePoint Online, on per-app limits per tenant and the "retry after" replies.
- Microsoft Learn: Migration performance guide, on parallel work across site collections, app-based sign-in and quieter hours.
Planning the split? See what the Migration Tools copy, or read how to move files between SharePoint sites.
Last updated