A SharePoint tenant-to-tenant migration affects content, identities, permissions, links, workflows, compliance controls, and user habits at the same time. This reusable checklist helps IT teams move from discovery to pilot waves, cutover, and post-migration validation while reducing avoidable business disruption.
Overview
A tenant-to-tenant migration is not simply a file-copy exercise. It is a controlled change to how people access SharePoint sites, OneDrive content, Microsoft Teams-connected files, sharing links, applications, and records. The exact options available will depend on the source and target tenants, licensing, workload scope, identity architecture, migration tools, and Microsoft-supported scenarios in effect when the project begins.
Start by defining the outcome. A merger may require selective migration and the preservation of business ownership. A divestiture may require separation, legal review, and a fixed completion date. A tenant consolidation may prioritize standardization, duplicate removal, and a common governance model. Write these objectives down before selecting a tool or setting a cutover date.
Use a migration register as the project’s source of truth. At minimum, include the source URL, site or team owner, business function, target location, data volume, sensitivity, retention requirements, external sharing status, customizations, workflow dependencies, migration wave, owner approval, migration status, validation result, and exception notes. Keep a separate identity-mapping register for source users, groups, guests, service accounts, and target identities.
Microsoft-supported scenarios, administrative steps, licensing requirements, limits, and tool behavior can change. Confirm the current guidance before execution rather than treating this checklist as a substitute for product documentation or legal advice.
Checklist by scenario
1. Discovery and planning
- Define the scope: SharePoint sites, OneDrive accounts, Teams-connected sites, Microsoft 365 groups, pages, lists, libraries, permissions, metadata, versions, workflows, Power Platform connections, and external sharing.
- Identify business-critical content and systems with fixed deadlines, regulated records, active investigations, or contractual obligations.
- Inventory inactive, duplicate, abandoned, and over-permissioned sites. Decide what will be migrated, archived, rebuilt, or retired.
- Record owners and approvers for every workload. Do not rely only on the original site owner; confirm who can validate the target environment.
- Document source and target tenant settings, domains, authentication model, conditional access expectations, sensitivity controls, retention configuration, and sharing policies.
- Choose a migration method after testing its handling of permissions, versions, metadata, links, large files, customizations, and failures. A useful comparison should include Microsoft migration options and relevant third-party tools, not just transfer speed. See the SharePoint migration tool comparison for a framework.
2. Identity and dependency mapping
- Map source users to target accounts, including name changes, duplicate identities, disabled accounts, contractors, guests, and accounts that will not be recreated.
- Map security groups and Microsoft 365 groups. Decide whether each group will be recreated, replaced, or deliberately removed.
- List service accounts, app registrations, API permissions, certificates, managed identities, and scheduled jobs that touch SharePoint content.
- Identify Teams, Viva Connections, Power Automate, Power Apps, Forms, Planner, Lists, and third-party integrations that depend on source URLs or tenant-specific identifiers.
- Document external collaborators and decide how their access will be re-established, reviewed, or ended.
- Plan how users will receive new links. Old URLs, sharing links, embedded references, bookmarks, and application connections may not behave as they did before migration.
3. Pilot wave
- Select a representative pilot, not only a small or simple site. Include common documents, version history, metadata, unique permissions, pages, lists, workflows, and at least one business owner.
- Capture a baseline before migration: item counts, library sizes, permissions, owners, sample URLs, version expectations, and known exceptions.
- Run the pilot through the intended process, including pre-checks, migration, error review, user testing, remediation, and sign-off.
- Measure practical outcomes: missing items, permission differences, broken links, search visibility, page rendering, workflow behavior, sharing behavior, and user ability to complete normal tasks.
- Update the runbook from pilot findings. Do not scale a process that has unresolved identity, permissions, or compliance exceptions.
4. Migration waves and cutover
- Group workloads by business owner, dependency, risk, and operating calendar rather than by volume alone.
- Publish a wave schedule with freeze windows, owner responsibilities, support contacts, rollback or recovery decisions, and acceptance deadlines.
- Set a content change policy. Decide whether users will have read-only access, whether edits will be paused, and how late changes will be captured.
- Complete a final delta migration where the selected tool and scenario support it. Record the last successful source synchronization and target readiness decision.
- Communicate the change in plain language: what is moving, when access changes, where users will work afterward, what they must do with unsynced files, and how to report an issue.
- Use a go/no-go meeting with evidence, not optimism. Require confirmation that identity mappings, target permissions, business owners, support coverage, and validation steps are ready.
5. Post-migration validation
- Compare source and target counts for sites, libraries, folders, files, list items, pages, and versions according to the agreed scope.
- Ask owners to test representative business tasks, including opening, editing, sharing, searching, downloading, approving, and collaborating on content.
- Review permissions at the site, library, folder, item, and sharing-link levels where applicable. Pay particular attention to unique permissions and guest access.
- Test workflows, Power Automate flows, Power Apps, embedded content, forms, alerts, navigation, and Teams access.
- Verify retention labels, policies, records controls, sensitivity handling, audit expectations, and legal hold implications with the appropriate compliance owners. The retention labels and policies guide can support this review.
- Document accepted defects, owners, deadlines, and evidence. Keep the source available for the agreed coexistence or rollback period, then retire access through a controlled governance process.
What to double-check
Permissions are not the same as ownership. A site owner may not have approved access for every department, and a copied permission structure can preserve inappropriate access. Review permissions against business roles and target governance, not only against the source configuration.
Identity matching needs evidence. Similar display names are not sufficient. Confirm immutable identifiers or another reliable matching method, and maintain a list of accounts that require manual handling.
Compliance settings need a separate test plan. Content may be subject to retention, records management, sensitivity, eDiscovery, or investigation requirements. Confirm how those controls apply in the target tenant before moving or deleting source content. Preserve evidence of decisions and test results.
Links and integrations are easy to overlook. Search for source URLs in pages, documents, scripts, workflows, email templates, intranet navigation, Teams tabs, and line-of-business applications. A successful file transfer does not prove that the surrounding experience still works.
Synchronization deserves its own review. If users work with OneDrive-synced folders, identify unsynced edits, offline files, conflict risks, and the instructions required before cutover. Include mobile and remote users in the communication plan.
Backup is not a migration plan. Confirm what native recovery, retention, or third-party protection can and cannot restore. The SharePoint backup and restore comparison provides a useful way to separate recovery objectives from migration decisions.
Common mistakes
- Choosing a cutover date before discovery and pilot validation are complete.
- Counting files without checking versions, metadata, permissions, pages, and business workflows.
- Assuming Microsoft 365 groups, Teams, Power Platform connections, or external sharing will transfer unchanged.
- Using a single owner to approve a department’s entire migration without representative user testing.
- Ignoring inactive or abandoned content and carrying unnecessary governance debt into the target tenant.
- Deleting source content immediately after transfer, before acceptance testing and the agreed recovery period.
- Failing to record exceptions, leaving support teams without a reliable list of known issues.
- Communicating only on the cutover day instead of preparing users for changed URLs, sign-in behavior, sync steps, and support routes.
When to revisit
Revisit this checklist before each migration wave, after every pilot, and whenever the scope, tool, identity design, compliance requirement, or workflow inventory changes. It should also be reviewed before seasonal planning cycles, major organizational changes, tenant policy changes, and any migration rehearsal that exposes new dependencies.
At the start of each review, confirm five items: the current Microsoft-supported scenario, tool and licensing assumptions, source and target tenant settings, identity mappings, and validation evidence from the last wave. Refresh the migration register rather than copying an old version forward without review.
A practical next step is to schedule a readiness workshop with the migration lead, identity administrator, SharePoint administrator, security and compliance representatives, service owners, and business approvers. Leave the meeting with a scoped inventory, a named owner for every exception, a pilot workload, a draft communications message, and explicit go/no-go criteria. That discipline turns a tenant consolidation from a bulk transfer into a controlled SharePoint migration with measurable acceptance.