Your Microsoft 365 migration finishes late for reasons you could have seen on day one. Count objects instead of gigabytes, agree up front what gets rebuilt at the far end, and confirm which licenses your route needs. Those three answers set your window, your budget and your cutover weekend.
Why does a Microsoft 365 Migration Finish Late?
Microsoft 365 migrations slip because nobody measured the source, not because the software was slow.
I've sat in enough kickoff calls to know how this goes. Somebody reads a storage number off the admin center, divides it by a throughput figure from a vendor page and announces a date. Four weeks later that date moves, because storage was never what the clock follows.
Microsoft throttles migration by request cost, not by gigabyte. Its performance guide gives up to 10 TB a day for light content like video files and up to 250 GB a day for small files and list items with custom columns. Count objects and your estimate stops being a guess.
Every migration I've watched go wrong went wrong in week one, on a spreadsheet, long before anybody touched a migration tool.
Jamie Kaler Marketing Head and Content Strategist, RecoveryTools
What do You Inventory Before a Microsoft 365 Migration?
Take inventory first, because every later number depends on it. Start discovery against your source tenant before anybody quotes a date.
You want four figures out of that discovery pass.
- Sites and subsites. How many exist, and how many still get opened.
- User accounts holding data. Count accounts with content behind them rather than licenses issued.
- Item count. Files, list items and versions, counted separately.
- Cold content. How much nobody has touched in three years.
That fourth figure pays for itself. Archived material costs the same as live material to move, and nobody opens it on the far side.
Count objects, not storage. Your admin center reports gigabytes. Migration speed follows item count, so a report saying 400 GB tells you far less than one saying 1.2 million items.
What should You Clean up Before You Migrate?
Anything you move is something you pay to move twice, once in transfer hours and again in storage. Cleaning up first is the cheapest hour in your project.
Work through four piles before transfer starts.
- Stale sites. I treat sites with no activity in 12 months as stale. Archive them to a file system instead of moving them.
- Orphaned content. Files owned by accounts that left. Reassign an owner now or lose the audit trail later.
- Version bloat. Libraries that keep hundreds of versions per file multiply your item count, so cap them while you still have time to repeat the pilot.
- Duplicates and ROT. Redundant, outdated and trivial content that nobody needs. Remove it before you pay to move it.
Get sign off on what gets archived rather than moved. A department that finds its old site gone on Monday will escalate, even when nobody opened it for two years.
Do Built in Microsoft Tools Cover Your Migration Route?
Check this before your budget meeting, because for tenant to tenant work Microsoft's own tools leave gaps. Microsoft documents these boundaries on its own pages.
SPMT moves content from on premises SharePoint Server and file shares into Microsoft 365, and Microsoft's introduction page does not address tenant to tenant moves. Migration Manager covers file shares, Google Drive, Dropbox and Box. Mover is retired for admin led migrations.
Microsoft does sell a native tenant to tenant route, and it is licensed separately. SharePoint content is priced per 100 GB of data moved and offered to Enterprise Agreement customers. OneDrive needs a per user add on license, and Microsoft warns migrations fail without it.
So your route sets your license bill. Price both paths before you commit to either, alongside the rest of your SharePoint move cost.
Is Your Destination Tenant Ready to Receive Data?
Your destination tenant must be ready before the first file lands, or a clean Microsoft 365 migration becomes a failed one. Build it before you schedule anything.
- Verify your domains. DNS changes take time to propagate, so start early.
- Assign licenses first. Microsoft's cross tenant pages say to precreate users and assign licenses before the move. License the accounts, then migrate.
- Create your site structure. Agree naming and hub architecture up front, because renaming sites after transfer breaks links again.
- Set storage quotas. Compare every target account's quota with its source size before you start, because a full target cannot take more data.
Test one small transfer into the new tenant before your pilot. It surfaces license and quota problems while they still cost minutes.
What Survives a Microsoft 365 Migration and What Gets Rebuilt?
Your data moves across. Most of your configuration does not, and sorting out which is which in week one stops arguments on cutover night.
Files, folder structure, metadata and version history travel when the route supports them. Permissions travel when identity is mapped first. Version history has a second step people miss, covered in SharePoint version history migration.
Power Automate flows, retention policies, sharing links, Teams app tabs and anything wired to a tenant ID get rebuilt by hand. Write that rebuild list in week one and give it an owner. Teams moves carry extra weight here, because tabs and apps rebuild rather than transfer, and the RecoveryTools Teams Migrator page lists what moves and what does not.
How do You Size a Microsoft 365 Migration Window?
One timed pilot makes your Microsoft 365 migration schedule arithmetic instead of a guess, so measure something real before you promise a date. For the SharePoint side the published rates and the formula sit in how long does a SharePoint move take.
- Choose a representative site. Average size, average item count, real permissions.
- Time it end to end. Record items per minute, not megabytes per second.
- Divide your total item count by that rate. Now you have hours.
- Add a buffer. I add 40 percent, because throttling, retries and overnight gaps are real.
A pilot costs you a day. A date pulled out of the air costs you a quarter. Here's what that difference looks like on paper.
| Planning decision | Without a pilot | With a timed pilot |
|---|---|---|
| Window estimate | Based on a storage figure | Based on measured items per minute |
| Version history | Discovered mid transfer | Decided up front, full or capped |
| License count | Guessed, then topped up | Taken from your discovery report |
| Rebuild list | Written on cutover night | Agreed in week one |
| Rollback plan | Delete and retry | Source left untouched until sign off |
Swipe the table sideways to see both columns.
Who Owns What After a Microsoft 365 Migration?
Identity is the control plane for your move. Map it before anything transfers, because permissions ride on it. The full sequence sits in our guide to how to migrate SharePoint permissions to another tenant.
One CSV pairing every source account with its destination account solves most of this. Build it from your discovery report, not from a license list.
Two cases need a decision in advance. Departed employees who still hold permissions on live content, and external guests invited by your old tenant rather than stored inside it. Guests are tenant objects, so somebody invites them again in the new tenant, and that somebody needs naming now.
Mailbox and contact ownership follows the same logic. Teams rosters break quietly when identity mapping is skipped, and so does anything rebuilt afterwards.
Which Security Settings Need Deciding First?
Security settings decide whether your migration account can even connect, so they belong in week one rather than on cutover night.
Four settings need an answer before transfers start.
- Multi factor authentication. Your migration account needs either an exclusion or app level access, because an MFA prompt nobody sees stops the job.
- Conditional access policies. Location and device rules can block a migration service that connects from somewhere your policy does not expect.
- External sharing policy. Check the new tenant's defaults, because shared content lands under whatever rules it ships with.
- Retention and sensitivity labels. Labels do not travel. Rebuild your policy at the destination while the libraries are still empty.
Write down which account performs your migration and what it is allowed to do. Auditors ask for exactly that line six months later.
How do You Prepare Users for the Move?
Your migration can be technically perfect and still feel like an outage to the people using it. Preparation closes that gap.
Tell people three times. Two weeks out, two days out, and on the morning itself. Keep every message to what changes for them, not what changes for you.
- Start with a pilot group. Choose 10 users across 3 departments, move them a week early and collect what breaks.
- Send one page of instructions. New sign in address, what to expect on first open, who to contact.
- Name your champions. One person per department who answers the small questions so your service desk keeps the big ones.
- Warn your service desk. Expect more tickets in week one. Staff for it or your migration gets blamed for the wait.
Your pilot group also gives you honest timing. People report slow search and missing links long before any report does.
How should You Plan Cutover Weekend?
Split the move in two and cutover weekend stops being frightening. Move bulk content during the working week, then finish with a short incremental pass on the day.
- Start your long batch early. Begin days ahead while people keep working, because the source stays in use.
- Freeze new work briefly. A few hours covers it, because the freeze only needs to span the delta pass.
- Finish with your delta pass. Incremental mode moves what changed since your batch, so nothing arrives twice.
- Switch your links. Email signatures, Teams tabs and department bookmarks all point at your old address until somebody changes them.
- Keep your source untouched. Don't delete anything on the day. Weeks of overlap cost little and answer every question that follows.
Taking one site at a time? Our walkthrough on how to migrate a SharePoint site to another tenant covers the same order start to finish.
Size Your Own Estate Before You Plan a Date
RecoveryTools SharePoint Migrator has a storage scan, a delta pass and throttle aware batches. Start the free trial to scan your own tenant before you set a date.
Works on Windows 11, Windows 10 and Windows Server 2022.
What do You Verify After a Microsoft 365 Migration?
Five checks catch the problems that surface in week one, so work through them before anybody sends the all clear email.
- Item counts match. Compare source against destination per site rather than as one total.
- Permissions resolve. Spot check 10 users across 3 sites, including one guest.
- Version history landed. Open a file you know had 12 versions.
- Sharing links work. Old links point at your old tenant and die quietly.
- Search returns content. Indexing lags transfer, so check again the next day.
Lists carry pointers a library does not, covered in how to migrate a SharePoint list to another tenant. Moving OneDrive accounts is a separate job with its own mapping, and RecoveryTools OneDrive Migrator handles it.
Frequently Asked Questions
How Far Ahead should Microsoft 365 Migration Planning Start?
I start discovery at least four weeks before the target date. That leaves room for a timed pilot, a rebuild list and a license purchase without anybody rushing scope.
Does a Microsoft 365 Migration Delete Anything From the Source?
A copy does not delete anything. Your source stays in place and people keep working while the job proceeds, so keep it untouched until you sign off.
Why does Item Count Matter More Than Total Size?
Microsoft throttles by request cost rather than by gigabyte. A million small files take far longer than the same storage held in a few large ones, and every file version counts as its own object.
What Gets Missed Most in Microsoft 365 Migration Planning?
Three things surface late. Version history rules, departed users who still hold permissions and sharing links that point at your old address after everyone has moved.
Do We Need to Migrate Archived Content at All?
Not always. Content untouched in three years can be exported to a file system instead, which keeps it available for audit without paying to move it into your new tenant.
How Long should the Source Tenant Stay Alive?
Keep it read only for a few weeks after cutover. Overlap costs little, and it answers every question about a missing file without anybody guessing.
Can Microsoft Tools Move SharePoint Sites Between Tenants?
Not with SPMT or Migration Manager. SPMT covers on premises sources and Migration Manager covers file shares and cloud storage services. Microsoft does license a native cross tenant route for SharePoint content, priced per 100 GB moved and offered to Enterprise Agreement customers.
Where to Start This Week
Start discovery and write down four numbers. Sites, accounts, items and how much content nobody has opened in three years.
Those four numbers make every later argument arithmetic. Your date stops being an opinion and starts being a calculation.
So before your next planning call, answer the question that sets everything else. Do you know how many items sit in your source tenant right now?
Published 30 September 2026. Microsoft limits quoted above come from the Migrate to Microsoft 365 overview, the migration performance guide, the cross tenant SharePoint page and the cross tenant OneDrive page. Rules of thumb like the 40 percent buffer are my own and not Microsoft figures. Microsoft can change these limits, so check them before you plan.