SharePoint Tenant-to-Tenant Migration Playbook for Mergers and Acquisitions
A merger, acquisition or divestiture usually arrives with a fixed date: the day the old tenant is shut down, or the day the divested business must stop using the parent company's Microsoft 365. SharePoint is often the largest and least understood part of that move. This playbook covers the file side: SharePoint sites, OneDrive and Teams files.
Phase 1: Inventory and scope
Start with a list of every site, its owner, its size and when it was last used. Sites nobody has touched in years are the cheapest content to migrate, because you can archive them instead. Measure storage with Smart Storage Analyzer, including per-file version-history size, so you know how much data a "with version history" copy really moves.
- Which sites move, which are archived, and which stay behind (common in divestitures).
- Whether version history must come across, or only current files.
- Paths that will grow longer in the target URL. Check them with Smart Path Length.
- Forms and Power Automate flows that point at source sites.
Phase 2: Identity mapping
Every file carries an author and an editor, and every unique permission points at a user or group. In the target tenant those people have new accounts. Build a mapping table early: source account to target account, for users and groups. When the only change is the email domain, a domain swap covers most rows; the rest come from HR or the identity team as a CSV.
Agree who owns the table, because it changes as people join, leave or are excluded from the deal. Recheck it against the target tenant right before each copy run.
Phase 3: Pilot
Pick two or three representative sites: one large library, one site with heavy unique permissions, one with lists and metadata. Copy them, then have their owners check files, versions, metadata and access. Use what you learn to set throttling expectations and to fix the mapping table.
Phase 4: Pre-seed
Copy the bulk of the content weeks before cutover while people keep working in the source. A later run that skips unchanged files and copies only newer ones then moves just the delta. See the cross-tenant library copy workflow for the step-by-step run in Smart Copy.
Phase 5: Cutover and validation
- Freeze or set the source sites to read-only.
- Run the final delta copy.
- Compare the copy report with the source inventory and spot-check versions and permissions.
- Repoint links, rebuild flows and move forms (see moving flows and copying forms).
- Keep the source read-only for an agreed period before deletion.
What this playbook does not cover
Exchange mailboxes, Teams chats and channel conversations, and non-Microsoft sources need a dedicated migration product. Plan those workstreams in parallel with the same identity mapping table.
If you want a second pair of hands on the plan or the cutover weekend, our team runs SharePoint migration projects, or you can tell us about your move.
Get your first result in about 10 minutes
Copy sites, libraries, lists and pages with full version history. Free, MIT licensed, no sign-up.
- Download the Windows app from the latest release.
- Run it and sign in to your Microsoft 365 tenant.
- Pick a source and target site, then copy.
Email me when a new release ships
No marketing spam. One short email when a new release ships. You can unsubscribe anytime.
Was this page helpful?
One click. No form, no email address.
Missing something in SharePoint Smart Copy? Feature requests and bug reports go straight to the developer on GitHub — no account needed to read, free account to post.
Request a featureRelated tool
SharePoint Smart Copy
Copy sites, libraries, lists and pages with full version history. Free, MIT licensed, no sign-up.
Keep reading
How to Migrate a Large SharePoint Document Library Without Timeouts or Throttling
One giant copy job is the most common reason large library migrations stall. Here is how to break the move into batches, pre-seed it and verify the result.
SharePoint to SharePoint Migration: Copy Sites, Libraries & Full Version History Free
Most SharePoint to SharePoint migrations are really library copies. Here is how to move sites and libraries — same tenant or across tenants — with version history intact, for free.
Compare two SharePoint folders and get a duplicate report in Excel
Point Smart Copy at any two folders in your tenant and it tells you what matches, what is duplicated, and what is missing — exported as an Excel workbook you can filter and share.
Need expert hands on deck?
Let our team plan and run your SharePoint migration
Full-service file and metadata migrations across sites, tenants, or from on-premises to SharePoint Online, from planning and test runs to verification and cutover.
About the author
Sean Regan
SharePoint & Microsoft 365 consultant with 20+ years of hands-on experience building SPFx web parts, migration tooling and tenant-grade automation. Maintainer of the open-source SharePoint Smart Solutions suite.
