Copy a SharePoint Library to Another Site (Step-by-Step)

Two methods exist for copying a SharePoint document library to another site. Here is what each can and cannot do before you begin:

What does SharePoint's built-in Copy To do?

Copy To is a SharePoint Online action that transfers file content and folder structure to any library in the same tenant. No admin tools or PowerShell required - any user with Contribute permission on both the source and destination library can run it. It processes the copy asynchronously in the background and works well for libraries with a few hundred to a few thousand small or medium files where custom metadata is not in use.

What copies successfully

• All file types and their binary content
• Folder hierarchy, including nested subfolders at any depth
• File names and extensions
• The current version of each file (the latest checked-in version)

What stays behind

• Custom column values. If the source library has columns such as Department, Project Code, Status, or managed metadata terms, those values are not copied. Items arrive at the destination with blank columns even when matching columns exist.
• Version history. Only the current version transfers. Every prior version is left behind. For document control or regulated content workflows, this is a significant limitation.
• Item-level unique permissions. Any file or folder that had its permissions broken from the library's inherited permissions will arrive at the destination with the library's default permissions instead.
• Checked-out state. Files that are checked out in the source library arrive checked in at the destination. If the source file is actively being edited, the destination copy reflects the last checked-in version.
• Content type assignment. Items may revert to the library's default content type at the destination if the destination library does not have the same content types configured.

For many reorganisation tasks, these limitations are acceptable. If the goal is to move files to a new library and custom metadata is not in use, Copy To is the right tool.

Step-by-step: Using Copy To in SharePoint Online

1. Open the source library in the modern experience. Navigate to the SharePoint site containing the library you want to copy. If you are in classic view, switch to the modern experience using the link in the bottom-left corner of the library view.
2. Select all items. Click the checkbox in the Name column header to select all items visible in the current view. If the library has more items than fit on one page, a yellow banner appears at the top of the list: click Select all [n] items in this library to include everything.
3. Open the Copy To panel. In the command bar above the item list, click Copy to. On narrower screens or when multiple items are selected, the button may be inside the three-dot overflow menu. A panel opens on the right side of the page.
4. Browse to the destination. In the panel, click Your organization to browse all sites in the tenant. Type the destination site name in the search box or scroll to find it. Select the site, then choose the target library or a folder within it.
5. Start the copy. Click Copy here. A progress notification appears in the top-right corner of the screen. Keep the browser tab open while the operation runs; closing it before completion can interrupt the process on slower networks.
6. Verify the result. When the notification confirms completion, navigate to the destination library. Confirm that files and folders have arrived, check the item count, and spot-check a few files to ensure content is intact.

When to use Clone Master instead of Copy To

Three situations make the native Copy To insufficient for a library copy:

• The library uses custom columns. If items carry values in columns such as Department, Client, Status, Approval Stage, or any managed metadata field, those values will not transfer. The destination library receives the files with blank columns, and the metadata must be re-entered manually or rebuilt from a source export. For libraries with thousands of items, that is not a realistic option.
• Version history matters. Document control systems, regulated industries, and quality management workflows often require that previous versions remain accessible after a library is relocated. Native Copy To transfers only the current version. If auditors or end users need to open version 14 of a document that is now on version 22, Copy To is not viable.
• The library is large or network reliability is a concern. Copy To runs as a browser-initiated job with no resume capability. If the network drops or the browser session times out mid-copy, there is no built-in way to resume from the interruption point. You must identify what transferred and what did not before restarting. For libraries over a few gigabytes, this is a real operational risk.

Try ShareMaster free for 14 days

Copying a library with metadata using Clone Master

Clone Master reads the source library's schema (its column definitions, content types, and view configuration) and creates a matching structure at the destination before transferring any files. Each item's column values are then read from the source and written to the corresponding columns at the destination, including lookup columns, managed metadata terms, and person fields.

The workflow for a library copy in Clone Master:

1. Connect to the source site using the site picker.
2. Select the source library from the library list.
3. Connect to the destination site (same tenant or a different tenant).
4. Choose an existing destination library, or let Clone Master create one that mirrors the source schema.
5. Configure copy options: whether to carry version history across, how many versions to include per file, whether to copy item-level unique permissions, and whether to preserve original created and modified timestamps or use the copy date.
6. Run the copy. Clone Master processes items in batches, logging each transferred file with its outcome. If a throttle limit is reached, Clone Master backs off and retries automatically.
7. Review the transfer log. Any items that required a retry or produced a warning are listed with their specific error, so you can address them without rerunning the entire operation.

For large libraries, scheduling the copy outside peak business hours reduces the likelihood of hitting SharePoint Online's API rate limits. See the SharePoint Migration Throttling Limits Reference for the specific thresholds that apply to bulk data movement operations.

After the copy: checking your results

Run a post-copy validation before decommissioning or repurposing the source library. The checks that catch the most common issues:

• Item count comparison. The destination library should show the same number of files and folders as the source. A discrepancy means some items did not transfer.
• Metadata spot-check. Open five to ten items at random from different folders. Confirm that custom column values match what the source shows for those items.
• Version history check (if applicable). Open one or two files in the destination and click Version History. Confirm that historical versions are present and that the version count matches the source (within the version limit you set during the copy configuration).
• Permission check (if item permissions were copied). Ask a test user who had unique access to a specific item in the source to attempt to open the same item at the destination. Confirm access is as expected.

Do not delete the source library until the validation is complete. During any parallel-run period, set the source library to read-only by removing the Contribute permission from all user groups, so that no new edits accumulate in the old location while you are relying on the destination.

Frequently Asked Questions

Can I copy a SharePoint document library to another site in the same tenant?

Yes. SharePoint Online's built-in Copy To copies file content and folder structure to any library on any site in the same tenant. Custom column values, version history, and item-level unique permissions are not transferred. For a full-fidelity copy including metadata, use Clone Master.

Does copying a SharePoint library preserve the folder structure?

Yes. Copy To recreates the source library's folder hierarchy at the destination. Files land in the correct subfolders, and any subfolder that does not already exist at the destination is created automatically during the operation.

How do I copy a SharePoint library and keep metadata values?

The native Copy To does not transfer custom column values. To copy a library with metadata intact, use Clone Master, which maps source column values to destination columns for every item, including managed metadata fields and person columns.

Need to copy across tenants? See the cross-tenant document library migration guide.