How to Copy Lists from One SharePoint Site to Another

Published:

Last updated: 2026-11-11

Copy a SharePoint list or library to another site with its items, versions, authors, dates and permissions using SharePoint Essentials Toolkit, then verify the result and correct links.

To copy a SharePoint list or document library to another site with its content, use Copy lists in SharePoint Essentials Toolkit. Pick the source list and target site, choose version history and permissions, run the copy, then run Copy verification. Between SharePoint Online sites, the high-fidelity bulk engine uses the Microsoft Migration API to retain original authors, dates, versions and item IDs.

Community Edition is free and never expires. Copy Sites, Copy Lists, version history, user/group mapping and both copy engines are available within its 20-site-collection allowance. Copying several selected source lists in one job requires Professional. Download SharePoint Essentials Toolkit and request a free Community Edition key.

Watch: Migrate SharePoint lists and libraries without breaking links

This walkthrough shows how to prepare source links, copy lists and libraries with full fidelity, build a destination mapping, preview replacements, fix links and verify the result.

Watch the full video with transcript and chapters

Created by the Cognillo product team. Narrated with an AI-generated voice.

Before you begin

  • Install the current SharePoint Essentials Toolkit on your Windows PC and add the source and target connections.
  • The target site must already exist. Missing lists, columns, content types and views can be created by the toolkit.
  • Use an account with access to the content on both sites. Site Owner or Full Control may be sufficient for some standard copies, but some resources require Site Collection Administrator rights. The high-fidelity engine requires Site Collection Administrator access on both SharePoint Online sites.
  • SharePoint Administrator or Global Administrator roles alone do not automatically grant access to SharePoint content.
  • For a cross-tenant copy, add a connection for the target tenant and plan user mapping for accounts that differ.
  • Check in checked-out files and review long paths, unresolved users, version settings and lookup dependencies before copying.
  • If you need to correct links after migration, prepare the source before moving anything, as described below.

Step by step: Copy a list or library to another site

1. Add and select the source

Ensure the sites are added to the toolkit. See How to add sites to the Home Page Dashboard. From the dashboard, open Explorer and select the source site. Open that site to select the list or library you want to copy. In the Actions panel, choose the Copy or move option, then select the blue copy button to open Copy Lists Options.

SharePoint Essentials Toolkit dashboard before opening Explorer to select a copy source
Start from the dashboard and open Explorer to locate the source site.
Boston Team source site selected in Explorer with the Copy or move lists action
Select the source site. Copy or move lists opens the copy task with this site as the source.
Documents library selected in Explorer with Copy 1 library to another site button
Open the source site, select one list or library, then choose the copy action.
Documents and Documents Test libraries selected together for a SharePoint copy job
For a multiple-list job, select each source list or library. Multiple selected source lists require Professional or Enterprise.
Close-up of Copy or move these 2 libraries and the Copy 2 libraries to another site button
Copy action close-up: the selected lists become the source; nothing is copied until you run the configured job.

2. Check before you copy

Run Check before you copy to review anything that would block, change or be skipped by the copy. Check target version settings, checked-out files, paths and unresolved accounts. Include the lists that lookup columns depend on so their values can resolve on the destination.

3. Pick the target and review the mapping

Select Next: Pick target and add the destination site on the Target tab. Review each source-to-target list mapping, including the target list name, internal name and folder. A missing target list can be created. If content already exists, review the available add, update, overwrite or skip behavior before running; test against a non-production target first.

You can copy one source list to another site or to multiple target sites. Selecting several source lists, including consolidation into one target, requires Professional or Enterprise. For an entire site's structure and content, use Copy sites.

4. Choose versions, metadata and permissions

  • Version history: choose all versions, major versions only, or the most recent versions you need. Major and minor version history are supported in the current high-fidelity SharePoint Online copy; the older major-only guidance no longer applies.
  • Authors and dates: preserve Created By, Modified By, Created and Modified instead of replacing them with the copying account and today's date.
  • Structure and metadata: review columns, content types, views, folders and settings. Lookups must point to the correct copied list. Content type and field mapping are not yet available.
  • Permissions: choose list and item permissions. For a site copy, site permissions, SharePoint groups and group members are separate options. Map source groups to the target's Owners, Members and Visitors where appropriate.
  • User mapping: map changed or departed accounts to destination accounts and choose a fallback account for users that cannot be resolved.
Copy Lists Options summary showing source, target, permissions, version history and copy engine
Review Copy Lists Options before running. This example has no target selected and version history and permissions are off; choose the target and settings your copy needs.

5. Confirm the copy engine and run

High-fidelity bulk copy is for SharePoint Online to SharePoint Online, within one tenant or across tenants. SharePoint imports the staged content through the Migration API, retaining authors, dates, version history and item IDs without firing target alerts or workflows. Content is staged in encrypted storage provided by SharePoint or in your own Azure Storage account.

Standard copies items through the SharePoint client API, with parallel processing and throttling management. It is used for supported on-premises copies and jobs needing content filters. A job with an on-premises site, content filters or insufficient administrator access for bulk copy falls back to the standard engine; review the job log for the reason.

Review the summary, select Run Now and inspect the report for copied items, skips, warnings and errors. Do not treat a finished job as proof that everything matches.

6. Verify the result

Run Copy verification from the completed copy job. Compare source and target item by item on size, dates, users, version and column values. Investigate missing items or differences and keep the report before retiring the source. Open the destination in SharePoint and inspect representative files, version histories, lookup values and permissions.

For a separate metadata check, see How to Compare Metadata Between Two SharePoint Lists. Run permissions reports on the source and destination and compare their exports to confirm who can access the copied content.

Prepare, map and fix links after the copy

Copying a list does not automatically rewrite every link in documents and pages. Old paths, Document ID links and GUID-based links may still point at the source. Sharing links are not recreated on the destination; mapping an old sharing-link URL to a new file address does not preserve its original access grant.

  1. Prepare the source before migrating. Under Tasks > Links > Migration, open Prepare site for link correction and choose step one, run on source. Turn on Record sharing links if needed. The task stores source URL forms and keys in the hidden SPE Source URLs and SPE Source Key columns without changing item Modified dates.
  2. Copy the content. These stamps travel with the copied items. Keep the source available until verification is complete.
  3. Scan the destination. Run Find broken links to check supported documents, pages, list values and navigation. Also review links still pointing to the old site: they may work while the source remains online but fail after it is retired.
  4. Build the mapping on the target. Open Prepare site for link correction again and choose step two, run on target. The task pairs the stamped source addresses with their destination items and builds an Excel or CSV Find and Replace mapping.
  5. Preview before writing. Select Fix links now, or import the mapping into Fix or replace links in bulk. Keep Flag only on for the first run and review every proposed replacement.
  6. Apply and verify. Once the preview is correct, turn Flag only off and run again. Re-run Find broken links and review remaining failures. Test destination access separately, especially where an old sharing link becomes a direct file link.
  7. Clean up. After confirming the migration and keeping the mapping/report, use step three, Remove the stamped columns, to remove the two preparation columns.

Community runs read-only broken-link and permissions reports at full depth. Find and Replace can be tried on lists with fewer than 100 items; unlimited bulk replacement requires Enterprise. See How to Automatically Fix Links in SharePoint for the full link-correction guide.

When built-in SharePoint copying is enough

  • Copy to copies files and folders in document libraries, but brings only the latest version. It does not copy an entire list with its settings and permissions.
  • Move to keeps file version history, but removes the files from the source; it is not a duplicate for testing.
  • From existing list copies columns, views and formatting, not list items.
  • List templates with Include Content have a 50 MB content limit and require a supported site configuration. They do not preserve permissions or full version history.
  • PowerShell can copy structure and items, but versions, attachments, lookups, people and permissions need additional handling. Test scripts on a small list first.

Edition limits and important exclusions

Community Edition is free with no time limit. Its allowance is 20 site collections per tenant, shared across Community keys, 20 per key and at most 20 per job; subsites share their site collection's count. Discovery and connection tests do not consume a site. Copy Lists, Copy Sites, version history, permissions within a copy, user/group mapping, preparation and verification are included. Multiple selected source lists require Professional. Standalone bulk permission editing and unlimited link replacement require Enterprise.

Workflows, Power Automate flows, alerts and sharing links are not migrated as part of the copy. Configure or recreate them on the target as needed. Do not remove the source until content, links and access have been checked.

Related blog guides: Copying lists, sites and migrations

Related resources