RecoveryTools
SharePoint

Copy a Document Library to Another Site

Jamie Kaler
· 9 minute read
Quick Answer

Copy document library files to another SharePoint site in 5 ways. Use Copy to, Copy-PnPList, Copy-PnPFile, sync or software. Copy to fits folders that remain under the Microsoft caps. Copy-PnPList builds the columns and views first. Copy-PnPFile fits large folders inside one tenant. Sync or download fits small libraries and a few files. RecoveryTools SharePoint Migrator copies versions and metadata. Copy one folder first because Copy to drops some metadata.

Your team has a document library that works well, with the right columns, views and folders. Now another site needs the same library and you cannot find a button that copies it.

That gap is real. This guide shows five ways to copy a library to a second SharePoint site, what every method carries and what you must fix by hand. I name the limits Microsoft publishes so you can plan before you start.

Can You Copy a Document Library to Another SharePoint Site?

Yes but in two parts. I found no Microsoft page that describes one button to copy a library with its files so you copy the structure first and the content second.

The structure means the columns, views and settings. The content means the files and folders. Copy to handles content and PnP PowerShell can handle both.

Most people copy the files first and find the columns missing at the destination. By then the data in those columns is already gone.

Jamie Kaler

Build the destination columns before you copy a single file. Copy to drops any property the new library cannot store and you only notice weeks later.

Marketing Head and Content Strategist, RecoveryTools

How do You Copy a Library Step by Step?

Use this order to copy the document library with every method below. Steps 1 to 3 prepare the copy. Steps 4 to 8 do the copy and check it.

  1. Check your access. You need owner rights on both sites. If the other site does not show up in Copy to, your organization blocks cross site copies and your SharePoint admin can change that in the SharePoint admin center.
  2. Measure the library. Count the files, find the biggest file and check the longest path. Microsoft sets a 250 GB limit for a single file and 400 characters for the full path.
  3. Create the destination library. Add the same columns, with the same names and types, before any file lands. The next sections show how.
  4. Choose a method. Use the table in this guide. A few folders fit Copy to and a large library needs a script or software.
  5. Copy one folder first. Open it at the destination and check the files, the column values and the version history.
  6. Copy the rest in batches. Keep every operation under the Microsoft size and file caps.
  7. Check versions, metadata and permissions. Compare a sample of files in both libraries side by side.
  8. Keep the source until the checks pass. Delete the old library only after users confirm the new one is complete.

Step 3 is the one people forget. A column missing at the destination loses its data for good, because Copy to carries only supported properties.

Which Method Fits Your Document Library Copy?

Here is the short version for copying a document library. The detail for every method follows.

MethodWorks across sitesBest forThe catch
Copy toYesFolders that fit the Microsoft capsLatest version only, managed metadata values drop
Download and uploadYesA few filesZip downloads stop at 20 GB and columns and versions remain behind
OneDrive syncYesLibraries that fit the sync sizeMicrosoft advises 300,000 synced files at most
PnP PowerShellYes, same tenantLarge libraries and repeat tasksNeeds an app registration and scripting skill
Migration toolYesEntire libraries with versions and metadataNeeds a license

How do You Use Copy to on a Document Library?

Who it suits. Non technical site owners with owner rights on both sites. Source file size limit. One operation takes up to 100 GB and 30,000 files and OneNote files stop at 2 GB. Extra application. None, because a browser is enough.

Copy to is the built in method and it works from the modern library view.

  1. Open the source library and select the folders and files you want.
  2. Select Copy to on the command bar.
  3. Select the destination site. If the site is missing, select More places at the bottom of the site list.
  4. Select the destination library and folder, then confirm the copy.

Microsoft lists limits for copying across sites. One operation takes no more than 100 GB of data and 30,000 files and OneNote files stop at 2 GB. Split a big library into folder batches that remain under those numbers.

Version history is the biggest loss. Copy to copies only the latest version of a file and Microsoft says you must restore and copy every earlier version one by one. Move to does carry the history but it removes the files from the source and it is not available in the Site Pages library.

Metadata needs care too. Microsoft says managed metadata values are not retained and properties the destination lacks are dropped. Plan to refill those values after the copy.

Can You Copy the Library Columns and Views First?

Who it suits. Technical admins who copy library columns and views. Extra application. PnP PowerShell and an app registration.

Copy to moves files and omits the structure. A Microsoft Q&A answer confirms that the modern create dialog cannot build a library from a saved library template and the asker found a workaround only in the classic experience.

PnP PowerShell fills the gap. Copy-PnPList copies the fields, views and settings of a list to another site and does not move the items. SharePoint stores a library as a list so I use the cmdlet for library structure but the PnP page describes lists so test with the -WhatIf switch first.

Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/Source -Interactive -ClientId <your-app-id>
Copy-PnPList -Identity "Contracts" -DestinationWebUrl https://contoso.sharepoint.com/sites/Target -WhatIf

Remove -WhatIf when the check looks right. The cmdlet works inside one tenant only and for another tenant the PnP page says to export a provisioning template. Open the new library afterward and check the content types and the Title column, because the PnP page does not list them.

Which PnP PowerShell Command Copies Library Files?

Who it suits. Technical admins who copy files inside one tenant. Source file size limit. The copy follows the same cross site caps as Copy to. Extra application. PnP PowerShell and an app registration.

In PnP PowerShell, Copy-PnPFile copies files and folders between sites in one tenant. It copies all versions by default and the -IgnoreVersionHistory switch limits the copy to the latest version.

Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/Source -Interactive -ClientId <your-app-id>
$job = Copy-PnPFile -SourceUrl "Contracts/2026" -TargetUrl "/sites/Target/Contracts" -NoWait
Receive-PnPCopyMoveJobStatus -Job $job

The -NoWait switch returns a job object at once and Receive-PnPCopyMoveJobStatus shows the state of the copy task. Add -Overwrite to replace a folder that already exists at the destination. Without it, the copy stops when the item exists.

Copy one top level folder at a time. PnP says the copy is bound to Microsoft's limits for copying across sites so batch it the way you batch Copy to. The PnP page does not say which column values travel so test one folder and compare the columns.

If you want to move instead of copy, Move-PnPFile has an -AllowSchemaMismatch switch. Without it, the move fails when the destination has different fields, which protects metadata that cannot carry over.

PnP PowerShell has limits. You need an app registration for the sign in and you need scripting skill to loop over folders and handle errors. For one tenant and a library you understand, it works well.

Can OneDrive Sync or Download and Upload Copy a Library?

Who it suits. Non technical owners who copy a small library. Source file size limit. Zip downloads stop at 20 GB and Microsoft advises 300,000 synced files at most. Extra application. OneDrive app for sync. None for download, because a browser is enough.

Both work for small libraries. Neither one carries the structure.

For download and upload, select the files in the source library and select Download. SharePoint zips a multiple file download and Microsoft sets a 20 GB limit on that zip. Upload the files to the destination, where columns and versions remain behind.

Sync needs the OneDrive app. Connect both libraries to it and drag folders from one to the other in File Explorer. Microsoft recommends syncing no more than 300,000 files in a library and the same advice counts every library you sync. I found no Microsoft page that says sync carries version history so test a sample file before you trust it.

When does Software Make Sense for Copying a Library?

Software earns its cost when you copy the document library at scale, the versions matter or users expect the same metadata and permissions at the destination.

Microsoft's own SharePoint Migration Tool (SPMT) does not include this task. Its supported sources page lists local and network file shares and SharePoint Server 2010, 2013, 2016 and 2019. It does not list SharePoint Online as a source.

RecoveryTools SharePoint Migrator is an Easy to Use, graphical interface based utility and the software can copy libraries between two Microsoft 365 accounts. RecoveryTools SharePoint Migrator is capable of carrying version history, metadata and permissions so the migrated data is accessible and formatting and metadata are maintained. A CSV file allows you to map users and sites before the copy starts.

Copy Libraries With Versions and Metadata

RecoveryTools SharePoint Migrator copies libraries, lists and sites between two Microsoft 365 accounts with version history, metadata and permissions. A CSV file maps users and sites, a delta pass copies later changes and the task resumes after a throttle. Workflows and Power Automate flows remain behind and old links do not follow.

Works on Windows 11, 10 and Windows Server 2022.

What Remains Behind After a Library Copy?

Every method omits something. This table shows where to look first.

ItemWhat happens
Version historyCopy to retains the latest version only. Copy-PnPFile copies all versions unless you add -IgnoreVersionHistory.
Managed metadata valuesMicrosoft says Copy to does not retain them.
Columns the destination lacksThe data is lost, because Copy to carries only supported properties.
PermissionsCopied files take the permissions of the place they arrive. Compare them with the source.
LinksOld links still point at the source library.
Workflows and flowsThey remain with the source library.

My guides on how to migrate SharePoint library metadata and SharePoint version history migration go deeper on the first two rows.

Which Mistakes Break a Copied Document Library?

Five mistakes show up again and again when people are copying the document library to a new site.

First, copying files before the columns exist. Second, sending 150 GB in one operation and watching it fail. Third, trusting the copy because the files open. Fourth, forgetting that copied files take new permissions, which can open a restricted folder to everyone. Fifth, deleting the source library before anyone checks the copy.

If users report broken bookmarks afterward, see my fix for the SharePoint 404 error after a move. Permissions have their own rules and I explain them in how to migrate SharePoint permissions. For a full site, use how to migrate a SharePoint site to another tenant.

My Verdict on Copying a Document Library

For a few folders, use Copy to and accept the latest version only. For a large library in one tenant, use PnP PowerShell to build the structure with Copy-PnPList and copy folders with Copy-PnPFile. When versions, metadata and permissions must match, choose software.

Whatever you choose, copy one folder first and compare it with the source. A library that opens fine can still be missing half its column values.

Frequently Asked Questions

Can You Copy an Entire Document Library in One Click?

No. I found no Microsoft page that describes a single button for it. You copy the structure first, then copy the files with Copy to, PnP PowerShell or software.

Does Copy to Retain Version History?

No. Copy to copies only the latest version of a file. Move to copies the history but it removes the files from the source library.

Is There a Size Limit for Copy to?

Yes. Microsoft sets a cap of 100 GB of data and 30,000 files for one operation. Split a bigger library into batches.

Do Managed Metadata Values Copy With the Files?

No. Microsoft says managed metadata values are not retained. Create the same columns first, then check the values on a sample.

Does Move to Carry the Version History?

Yes. Move to carries the history but it removes the files from the source library. Microsoft says it is not available in the Site Pages library.

Can You Compare the Copied Library With the Source?

Yes. Open one folder at the destination and compare the files, the column values and the version history with the source. Do this before you copy the rest in batches.

Can You Delete the Source Library After the Copy?

Yes. Delete the old library only after users confirm the new one is ready. Compare a sample of files in both libraries first.

Jamie Kaler
Jamie Kaler Marketing Head and Content Strategist, RecoveryTools

Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.

Published 21 October 2026. Limits and steps come from Microsoft's pages on moving and copying files in SharePoint, SharePoint limits and what SPMT supports. The library template point comes from a Microsoft Q&A thread, which is community guidance and not official documentation. The cmdlet behavior comes from the PnP PowerShell reference for Copy-PnPFile, Copy-PnPList and Move-PnPFile so test every command on one folder first.