SharePoint Tenant-to-Tenant Migration: Sites, Lists, Libraries and Teams Boundaries

Last updated: 2026-10-19

Plan the SharePoint content move and its validation separately from a complete Microsoft Teams migration. Preserve structure and metadata intentionally, not by assumption.

Cognillo · By David Cooper

Plan the SharePoint content move and its validation separately from a complete Microsoft Teams migration. Preserve structure and metadata intentionally, not by assumption.

How do I copy SharePoint sites, lists and libraries between tenants?

Connect to both SharePoint environments, confirm source and target access, and run a representative copy before the full move. SharePoint Essentials Toolkit supports complete list and library copying with columns, views, version history, metadata and preserved last-modified information. The edition comparison currently lists Copy Sites as Coming soon; the steps below cover list and library copying.

  1. Inventory source sites, lists, libraries, item counts, custom columns and versions.

  2. Prepare the target and verify content access on both sides; an admin role alone does not grant access to all content.

  3. Select the source lists or libraries and target, then configure the supported copy options.

  4. Run a pilot and validate data, structure and history before copying the remaining content.

What should I verify when preserving version history and metadata?

Verify column definitions, views, item and file counts, representative metadata, last-modified values and version history after a pilot copy. Select an edition that supports the required options: version-history copying and multiple source lists need Professional or Enterprise, Migration API copying needs Enterprise, and copying permissions needs Enterprise. Compare major and minor versions in the source and destination during the pilot to verify the copied history.

  1. Capture baseline counts and representative source values.

  2. Compare target columns, views, timestamps and sample historical versions.

  3. Check person-field mappings and access separately from file content.

  4. Record mismatches and rerun only after the cause is understood.

Does copying a Teams-connected SharePoint site migrate all of Teams?

No. Copying the SharePoint files used by Teams is not the same as migrating the entire Team. Chats, meetings, memberships, applications and other services require their own migration scope and supported tooling. Plan SharePoint content and Microsoft Teams workloads separately, using current Microsoft migration documentation to establish what each chosen service can actually move.

  1. List SharePoint files separately from Teams chats, meetings, apps and membership.

  2. Choose a supported migration approach for each workload.

  3. Test the destination Team and its file access rather than assuming a SharePoint copy recreates the Team.

How should I validate a tenant-to-tenant move before cutover?

Run a pilot with a representative library containing custom columns, views, versions and permission exceptions. Compare the source and destination, test access as ordinary users, and inventory broken references. Agree a cutover plan and a rollback decision before the production move; a successful job status alone is not evidence that every business dependency or cross-tenant identity mapping is correct.

  1. Choose representative content and record a baseline.

  2. Validate structures, versions, metadata, permissions and links.

  3. Agree how to handle source changes during the move; do not assume incremental migration support.

  4. Obtain owner sign-off, complete the agreed cutover and retain source evidence.

Sources and next steps

Start with the Community Edition reporting limits and SharePoint Essentials Toolkit. Check the current edition comparison before making changes.