How to Migrate a Large SharePoint Document Library Without Timeouts or Throttling
Why large library migrations stall
A single job that tries to copy an entire large library has three problems. It sends a lot of requests, so SharePoint Online throttles it. It runs for a long time, so any interruption costs hours. And when it stops halfway, it is hard to tell what was copied. Microsoft explains throttling in Avoid getting throttled or blocked in SharePoint Online: the service returns HTTP 429 or 503 with a Retry-After header, and clients are expected to wait and retry.
1. Measure before you move
- Size and version history: Smart Storage Analyzer shows what is using space and can include per-file version-history size.
- Path length: Smart Path Length lists the longest paths, which matter if the target URL is longer than the source.
- Limits: the SharePoint limits cheat sheet covers file size, path and view threshold limits in one place.
2. Split the library into batches
Plan one job per top-level folder, or per group of folders of similar size, rather than one job for the whole library. Smaller jobs finish faster, are easier to re-run and make it obvious which part of the library is done. Schedule the heaviest batches outside business hours, when the tenant has less other traffic.
3. Decide what to do about version history
Version history can make a library many times larger than its current files. If you need the history, copy it; if you don't, trimming old versions first shortens every pass. Our guide to trimming SharePoint version history explains the options.
4. Pre-seed, then copy only the changes
Copy the bulk of the content days or weeks before cutover while people keep working in the source. Then re-run each batch so only new or changed files move. In Smart Copy, the If newer option does this. At cutover, a final short pass picks up the last changes.
5. Verify, then switch users over
Compare source and target before you tell users to move. Smart Copy's Verification Report checks the result independently of the copy. Fix any differences, re-run the affected batch, then update links, shortcuts and synced folders to point at the new library.
Related
Get your first result in about 10 minutes
Copy sites, libraries, lists and pages with full version history. Free, MIT licensed, no sign-up.
- Download the Windows app from the latest release.
- Run it and sign in to your Microsoft 365 tenant.
- Pick a source and target site, then copy.
Email me when a new release ships
No marketing spam. One short email when a new release ships. You can unsubscribe anytime.
Frequently asked questions
Why does my SharePoint migration slow down or stop?
Usually because the job is too big to run in one pass and SharePoint Online is throttling it. Microsoft returns HTTP 429 or 503 responses when a tenant sends too many requests. Smaller batches, running outside business hours and a tool that honors Retry-After keep the move going.
Does the 5,000-item limit stop me migrating a big library?
No. The list view threshold limits how many items one view or query can process. A library can hold far more files. Plan views with indexed columns or folders in the target so users don't hit the threshold after the move.
Should I copy version history?
Copy it when you need the audit trail, but measure it first. Version history can be much larger than the current files and adds time to every pass. Trimming old versions before the move can shorten the migration.
Can Smart Copy move a large library between tenants?
Yes. Smart Copy copies SharePoint, OneDrive and Teams files in the same tenant or between tenants, with full version history and identity mapping. Re-run it with If newer so later passes copy only changed files, and check the result with its Verification Report.
Was this page helpful?
One click. No form, no email address.
Missing something in SharePoint Smart Copy? Feature requests and bug reports go straight to the developer on GitHub — no account needed to read, free account to post.
Request a featureRelated tool
SharePoint Smart Copy
Copy sites, libraries, lists and pages with full version history. Free, MIT licensed, no sign-up.
Keep reading
SharePoint Tenant-to-Tenant Migration Playbook for Mergers and Acquisitions
Mergers and divestitures put a hard date on a tenant move. This playbook breaks the SharePoint part into five phases, with the decisions that matter in each.
SharePoint to SharePoint Migration: Copy Sites, Libraries & Full Version History Free
Most SharePoint to SharePoint migrations are really library copies. Here is how to move sites and libraries — same tenant or across tenants — with version history intact, for free.
Compare two SharePoint folders and get a duplicate report in Excel
Point Smart Copy at any two folders in your tenant and it tells you what matches, what is duplicated, and what is missing — exported as an Excel workbook you can filter and share.
Need expert hands on deck?
Let our team plan and run your SharePoint migration
Full-service file and metadata migrations across sites, tenants, or from on-premises to SharePoint Online, from planning and test runs to verification and cutover.
About the author
Sean Regan
SharePoint & Microsoft 365 consultant with 20+ years of hands-on experience building SPFx web parts, migration tooling and tenant-grade automation. Maintainer of the open-source SharePoint Smart Solutions suite.
