SharePoint tenant-to-tenant migration checklist
Migrations rarely fail on the technical side. They fail on a forgotten account, a missing target site or a poorly announced cutover. This list works for any project, whatever the tool.
Before
- Inventory the sites, libraries, OneDrive accounts and shares to migrate, with their volume and business owner.
- Decide what stays behind: abandoned sites, archives, old versions beyond a threshold.
- List what will need rebuilding: pages, web parts, workflows, Power Automate flows, apps.
- Create the accounts and groups in the target tenant.
- Build the identity mapping table and have it reviewed.
- Create the target site collections and target OneDrive accounts.
- Get admin consent for the application in each tenant.
- Give the migration account site collection admin and term store admin rights.
- Run the trial on a representative site, measure throughput and work out the total duration.
- Announce the schedule to users: pass dates, cutover day, what changes for them.
During
- Run the first full pass, outside business hours if possible.
- Read the report: column warnings, unknown accounts, renamed files.
- Fix the identity table or the target, then re-run incrementally.
- Have business owners check a sample: versions, metadata, permissions.
Cutover day
- Set the source sites to read-only.
- Run the last incremental pass.
- Compare the report counters with the inventory.
- Open the target, share the new addresses, update bookmarks and important links.
After
- Keep the source read-only for the agreed period, then archive or delete it.
- Keep the state database and reports: they allow a catch-up pass and serve as a record.
- Rebuild pages, workflows and flows.
- Remove the application consent and the temporary admin access to OneDrive accounts.
Test it on your own tenant
The 14-day trial migrates 10% of every library, with versions, metadata and permissions. After you subscribe, an incremental run migrates the rest.