Microsoft's native cross tenant route is sold per 100 GB, only to Enterprise Agreement customers, and it has no delta pass. That one missing feature decides your entire cutover plan. Here is what every route costs, what it leaves behind, and how to prove the site landed.
Why does a SharePoint Site Move Go Wrong?
Almost every SharePoint site move that goes wrong goes wrong for the same reason. Somebody chose a route before reading what that route cannot do.
I've watched teams book a cutover weekend around Microsoft's native cross tenant tool, then find out on the Thursday that it is sold only to Enterprise Agreement customers. I've watched another team plan a long batch and a short catch up pass, then learn the native route has no catch up pass at all.
Neither of those is a hidden detail. Both sit on Microsoft's own documentation pages. They just do not appear in the blog posts people read first.
Choose the route after you read its limits, not before. Every SharePoint site move I've seen slip was a route decision made in week one and discovered in week six.
Jamie Kaler Marketing Head and Content Strategist, RecoveryTools
What are Your SharePoint Site Move Routes?
Four SharePoint site move routes exist between tenants, and they are not interchangeable. Price, scope and rollback differ on every one.
| Route | Who can use it | What it costs | Delta pass |
|---|---|---|---|
| Native cross tenant | Enterprise Agreement customers only | Per 100 GB moved | No |
| SPMT | Anyone, but on premises sources only | Free | Yes, on premises |
| Download and upload by hand | Anyone | Your time | No |
| Third party migration tool | Anyone | Vendor price list | Yes |
Swipe the table sideways to see every column.
Route price is only one line of the budget. Where the rest of it goes is set out in SharePoint move cost.
SPMT is the one people reach for first and it is the one that cannot help here. Its source list, and the rest of SPMT limitations, rule it out on day one. Microsoft states it moves content from SharePoint Server on premises into Microsoft 365, and that it cannot move content from another Microsoft 365 tenant. Migration Manager covers file shares, Google, Dropbox and Box, so it does not fill that gap either.
That leaves the native cross tenant route, hand copying, or a tool built for the job. RecoveryTools SharePoint Migrator sits in that last column.
What does the Native Route Actually Require?
Read this list before you build a SharePoint site move plan around Microsoft's cross tenant route, because two lines on it rule the route out for most organizations.
- Enterprise Agreement only. Microsoft's cross tenant SharePoint page says the licenses are currently available only to Enterprise Agreement customers.
- Priced per 100 GB moved. Budget from your discovery figure, with a 20 percent grace allowance for growth during the project.
- Trust between both tenants. You connect both sides, establish trust, then verify that trust before anything else happens.
- Users and groups precreated. Everyone in scope must already exist on the target tenant before the identity mapping step.
- Source sites set to Read/Write. Microsoft says a read only source site fails the migration.
- No Customer Key encryption on the source. Service encryption with Microsoft Purview Customer Key on the source tenant blocks the route outright.
Two hard ceilings sit on top. A site can hold no more than 5 TB or 1 million items, and no path can exceed 400 characters. A site over either ceiling fails.
What does a SharePoint Site Move Leave Behind?
Files and folders travel. A surprising amount of what sits around them does not, and Microsoft names the gaps on its own page rather than leaving you to find them.
- Teams content and channels. The native route does not include them, so a team site that backs a Microsoft Teams team needs its own plan, covered in how to move Microsoft Teams to another tenant.
- Workflows. SharePoint 2010 and 2013 workflows are recreated and republished by hand.
- Apps. Apps are republished at the destination and sometimes modified before they work again.
- Power Apps and Power Automate. Both are rebuilt and reconnected to the new site.
- Sensitivity labels with user defined permissions. Microsoft states these cannot be migrated by the cross tenant route.
Write that rebuild list in week one and give every line an owner. A list written on cutover night is a list nobody finishes.
Why does the Missing Delta Pass Decide Your Cutover?
Here is the line that changes your schedule more than any other. Microsoft states that incremental and delta migration passes cannot be performed on the cross tenant route.
Think about what that removes. The normal shape of a safe SharePoint site move is a long batch during the working week while people carry on, then a short pass on the day that copies whatever changed since. Without a delta pass, that shape is gone.
You are left with one option. Freeze the site, move all of it in one pass, and hope the window holds. For a 2 TB site collection that is a long freeze to ask a department to accept, and how long does a SharePoint move take works out what that freeze costs in days.
That is the entire argument for a third party tool. A delta pass shrinks a frozen weekend to a few frozen hours, because the bulk already moved during the week and only the changes are left.
How do You Prepare the Source Site for Migration?
Preparation is where a SharePoint site move is won, and it is mostly counting. Start with discovery on the source before anybody quotes a date, and the rest of the plan becomes arithmetic.
- Count items, not gigabytes. Microsoft publishes speed estimates from 250 GB a day for heavy content to 10 TB a day for light content, and throttling applies to migration traffic during weekday daytime hours.
- Find the long paths. Anything past 400 characters fails, and it fails late. Shorten folder names before transfer rather than during it.
- Check the ceilings. A site over 5 TB or 1 million items needs splitting before the native route will touch it.
- Clear the dead weight. Sites with no activity in 12 months cost the same to move as live ones. Archive them instead.
- Cap version history. A library keeping 500 versions per file multiplies your item count, so decide the cap while you can still repeat the pilot.
Our post on Microsoft 365 migration planning checks covers the discovery pass in more depth, including how to size the window from a timed pilot.
How do You Map Users Before the Move?
Permissions ride on identity, so identity is mapped before content moves. Microsoft puts precreating users and groups ahead of the mapping step for exactly that reason. What survives that step, and what Microsoft drops on the way, is covered in how to migrate SharePoint permissions to another tenant.
One CSV pairing every source account with its destination account solves most of it. Build it from the discovery report rather than from a license list, because a license does not tell you who holds content.
Two cases need a decision in advance. Departed employees who still hold permissions on live content, and external guests who were invited by the old tenant rather than stored inside it. Guests do not come across, so somebody invites them again, and that somebody needs naming now. The links those guests already hold are a separate decision, covered in what happens to SharePoint sharing links after migration.
When two organizations are combining rather than one moving out, the identity work is larger again. The Microsoft 365 migration planning checklist helps you scope that extra identity work.
How should Cutover Weekend Go?
With a tool that supports delta passes, split the SharePoint site move in two and the weekend stops being frightening.
- Start the long batch early. Begin days ahead while people keep working in the source site.
- Freeze new work briefly. A few hours covers it. The freeze only needs to span the delta pass.
- Start the delta pass. Incremental mode moves what changed since the batch, so nothing arrives twice.
- Switch the links. Email signatures, Teams tabs and department bookmarks all point at the old address until somebody changes them.
- Keep the source in place. Do not delete anything on the day, so every question that follows has an answer.
Mailbox and personal file work follow separate tracks. Read Exchange Online mailbox migration between tenants for mailboxes and copy OneDrive files to another account for personal files.
Count Your Sites Before You Choose a Route
Count sites, items and long paths first. Then test one site in the free trial before you commit to a plan.
Works on Windows 11, 10 and Windows Server 2022.
How do You Prove a SharePoint Site Move Landed?
Most SharePoint site move guides stop at the moment the job says finished. That is where the real work starts, because a finished job and a complete site are different claims.
- Item counts match per site. Compare source against destination site by site rather than as one total, because one failed library hides inside a big number.
- Permissions resolve. Spot check 10 users across 3 sites, including one external guest and one departed account.
- Version history landed. Open a file you know had 12 versions and count them, then check again two weeks later, because SharePoint version history migration depends on the version limits of the destination library.
- Long paths survived. Search the report for anything that failed on the 400 character limit, because those fail quietly.
- Search returns content. Search indexing needs time after the transfer, so do not panic on the first check.
A report that lists files is not proof that the files are intact. Compare content rather than names alone.
Lists carry pointers a library does not, covered in how to migrate a SharePoint list to another tenant. Permissions follow their own rules, and the levels behind them are explained in SharePoint permission levels explained.
Frequently Asked Questions
Can SPMT Move a Site to Another Tenant?
No. Microsoft states SPMT moves content from SharePoint Server on premises into Microsoft 365 and cannot move content from another Microsoft 365 tenant. For tenant to tenant work you need the native cross tenant route or a third party tool.
How Much does the Native Cross Tenant Route Cost?
Microsoft offers it to Enterprise Agreement customers and prices it per 100 GB of data moved, with a 20 percent grace allowance for growth during the project. Microsoft's cross tenant SharePoint page lists no other customer type.
Does the Native Route Support Delta or Incremental Passes?
No. Microsoft states incremental and delta migration passes cannot be performed. That means one single pass with the site frozen for its entire duration, which is why most teams with a large site collection choose a tool that supports a catch up pass.
Do Permissions Survive a SharePoint Site Move?
They survive when identity is mapped first. Users and groups are precreated on the target tenant, then the mapping pairs every source account with its destination account. External guests are the exception, because a guest is an invitation issued by a tenant rather than content held inside it.
What is the Largest Site the Native Route will Move?
No more than 5 TB of storage or 1 million items per site, and no path longer than 400 characters. A site over either ceiling fails, so split it before transfer.
How Long should the Source Tenant Stay Alive?
Keep it in place for a few weeks after cutover, so every question about a missing file has an answer without anybody guessing.
Do Shared Links Still Work After a Cross Tenant SharePoint Move?
Yes for migrated files. Microsoft says existing shared links redirect automatically to the new target location. The source tenant keeps those redirects until it is deprovisioned or an admin removes them site by site.
Where to Start This Week
Start discovery and write down four numbers. Sites, items, the longest path and the share of content nobody has opened in a year.
Those four numbers tell you which SharePoint site move routes are even available to you, before anybody argues about tools. A site over the ceilings rules out the native route on its own.
So before the next planning call, answer the question that decides everything after it. Which route can your estate actually use?
Published 3 October 2026. Microsoft limits quoted above come from the cross tenant SharePoint site migration overview, the cross tenant migration FAQs and the SPMT FAQ.