OneDrive tenant to tenant migration moves every user's files from one Microsoft 365 organization to another. Create and license the target accounts, map every source user to a destination user, copy the files with versions and dates, repeat the copy for changes and then check the result against the source before anyone switches over.
What does OneDrive tenant to tenant migration involve?
A OneDrive belongs to one person, so the job is really hundreds of small moves instead of one big one. Every user has a source account, a destination account and a mapping between the two that decides whose files land where.
Most of the effort sits around the files. The files themselves copy without much fuss. The trouble is everything attached to them: who could open a file, which version came first, what date the file was last edited and which links people saved. A OneDrive tenant to tenant migration that only moves the files and drops those details leaves users with a drive that looks right and behaves wrong.
This guide covers the full path for a OneDrive tenant to tenant migration, from preparing accounts to the final check. If you are moving SharePoint sites as well, they follow a different sequence, laid out in how to migrate a SharePoint site to another tenant.
Nobody opens a migrated OneDrive to count files. They open it to find last Tuesday's spreadsheet and see whether their manager can still edit it. Plan for that moment.
Jamie Kaler Marketing Head and Content Strategist, RecoveryTools
What moves and what stays behind in a OneDrive migration?
Files, folders, versions and dates travel. Anything that lives in the tenant instead of the file stays behind and gets set up again. Sort your plan by this table.
| Item | After a copy migration | What you do |
|---|---|---|
| Files and folder tree | Move, including empty folders | Nothing |
| Version history | Moves, or current version only if you choose | Decide before you start |
| Created and modified dates | Keep their original values | Nothing |
| Direct sharing | Re-created for people mapped to the destination | Check a sample |
| Sharing links | Do not move, because the link names the old tenant | Share again from the new location |
| Groups and outside guests | Not re-created | Invite them again in the destination |
| Personal Vault | Cannot be read for the user | Ask users to move the content out first |
| OneNote notebooks | Left out of the copy | Export and import from OneNote |
| Recycle bin | Not moved | Restore what you need before the move |
| Retention and legal holds | Tenant policy, not file content | Apply again in the destination |
| Sync app settings | Belong to the PC | Users sign in again and choose folders |
Sharing links deserve their own plan, because every saved link breaks the same way. The mechanics are explained in what happens to SharePoint sharing links after migration, and OneDrive files behave identically.
What do you need before a OneDrive migration starts?
Four things, and they decide how smooth the rest goes.
First, the destination accounts. Every user whose OneDrive you are moving needs an account in the target tenant with a license that includes OneDrive. Microsoft's own guidance says to precreate users and groups and to give every user the right license. People who stay in the source tenant but still need access get guest identities in the target.
Second, a mapping. A OneDrive tenant to tenant migration pairs every source user with a destination user. When addresses match on both sides, the pairing is automatic. When a rebrand or a merger changes the address, build the list by hand in a CSV file.
Third, admin rights on both sides, plus a sign-in method both tenants accept. Fourth, a clean destination. Microsoft says no OneDrive site should already exist for the user in the target, so restrict self service creation until the move is done. Skipping this step is the most common reason a first attempt fails.
Then tell users. Ask them to close and save open files, clear out the recycle bin items they still want and move anything in Personal Vault. A file left open and never saved has no readable copy in the cloud.
Which methods move OneDrive to another tenant?
There are four, and they suit different projects.
| Method | What it does well | Where it falls short |
|---|---|---|
| Microsoft cross tenant move | Moves content inside the Microsoft cloud and leaves a redirect at the old address | Needs a paid per user add on license, PowerShell only and no delta passes |
| Microsoft FastTrack service | Microsoft handles the move for qualifying customers | Invitation only with a 150 license minimum, and speed is not guaranteed |
| Download and upload by hand | Free for one small account | Loses versions, dates and sharing, and breaks on long paths |
| Migration software | Bulk moves with mapping, delta passes and reports | Tenant settings and links still need setup afterwards |
Microsoft's native move has hard limits worth knowing before you choose it. An account over 5 TB or 1 million items fails. Full paths longer than 400 characters are flagged, and users with an apostrophe in their name or address hit an invalid character error. Accounts under a legal hold are blocked until the hold is removed. It also moves content once. There is no second pass for files edited after the start. The add-on is explained in OneDrive cross tenant migration license explained.
The wider reasons Microsoft's free tools fall short are laid out in SharePoint Migration Tool limitations you hit in week one, and the money side is in SharePoint migration cost.
Copy OneDrive accounts between tenants with versions and dates
RecoveryTools OneDrive Migrator copies OneDrive for Business accounts from one Microsoft 365 organization to another with the folder tree, version history and original dates. Every file is hash checked against the source, which stays read only.
No credit card, no sign-up. Works on Windows 11, 10 and Windows Server 2022.
How do you migrate OneDrive from one tenant to another?
Follow this order. Steps one, three and six are the ones teams skip.
- List the accounts in scope. Record every OneDrive, its size and its owner. Mark leavers, shared mailboxes and accounts you will not move.
- Create and license the destination users. Give every mapped user a target account with OneDrive in the license, and keep OneDrive creation switched off until the copy starts.
- Build the user mapping. Let matching addresses pair automatically and import a CSV for the rest. Resolve duplicates and unknown people before the copy, not during it.
- Connect both tenants. Sign in to the source with read access and to the destination with write access. Use the least access that works.
- Choose the copy settings. Decide between all versions and the current version only, whether direct sharing is re-created and how many people copy at the same time.
- Pilot with a few real accounts. Choose a small group that includes one large drive and one with deep folders. Time it and read the report line by line.
- Copy in batches. Start the biggest drives first so one large account is not left alone at the end. Schedule the batch for the evening.
- Repeat the copy for changes. Start a delta pass on cutover day that moves only what changed, then switch users over.
Timing for the batches is worked out in how long does a SharePoint migration take, and Microsoft's throttling slows every tool the same way, as covered in SharePoint migration throttling errors and how to avoid them.
How do delta passes shorten the cutover?
They cut the final copy from days to minutes. A delta pass compares the destination with the source and moves only new and changed files, so files already there are skipped instead of copied again.
The pattern is simple. Start one long copy during the week while people keep working. Add short passes as the cutover gets close. On cutover day, ask users to stop editing, start the last pass and switch their sign in. The gap between the last pass and the switch is the only time files can drift, so keep it short.
This is the biggest practical difference between a native move and a copy tool. A native move is one shot. A copy migration can be repeated safely, because existing destination files are never overwritten or deleted. The wider sequence for a tenant change sits in the Microsoft 365 migration planning checklist.
How do you check a OneDrive migration finished?
A file count proves the copy ended. It does not prove the files are right.
Start with the report. Look for skipped and failed files and read the reason given for it. Then compare a sample of drives against the source. Check that folder names match, that dates were not reset to the day of the move and that a file with a long history still shows its versions. Open a few files that were shared with colleagues and confirm those colleagues can still edit them. Version rules are explained in does SharePoint version history migrate between tenants, and permission handling in how to migrate SharePoint permissions to another tenant.
Keep an independent copy outside both tenants while you check. The Office 365 Backup Tool holds that copy, so a failed check costs an afternoon instead of a dataset. Once the files check out, users still need to reconnect the sync app, which is covered in how to fix OneDrive not syncing after migration. Teams without spare hands for the check hand it to our cloud migration service.
Frequently asked questions
Can you migrate OneDrive from one tenant to another?
Yes. Microsoft offers a native cross tenant move that needs a per user add on license. Migration software offers the other route, copying files, versions and dates between two tenants without that license. Both need destination accounts created first.
Does OneDrive tenant to tenant migration keep version history?
It can. Microsoft's native move keeps previous versions, and RecoveryTools OneDrive Migrator copies every supported version or the current version only. Versions the source already pruned are gone before any tool reads them.
What happens to sharing links after a OneDrive migration?
Links that name the old tenant do not work in the new one. A copy migration re-creates direct sharing for mapped people, and everything else, including links and outside guests, is shared again from the new location. Plan to tell users.
How long does a OneDrive tenant to tenant migration take?
It depends on data size, file count and Microsoft throttling, not on the number of users alone. Many small files take longer than a few large ones. Pilot a few real accounts, time them and scale the result to the full batch.
Do users need new OneDrive accounts first?
Yes. Every user needs a licensed account in the target tenant before their files can land. Microsoft also says the OneDrive itself should not exist yet, so restrict self service creation until the copy is done.
Does RecoveryTools OneDrive Migrator change the source OneDrive?
No. The source is opened read only, so the copy never deletes or rewrites files there. Files already in the destination are skipped or kept alongside, never overwritten, which also makes a repeat pass safe.
Where to start this week
List every OneDrive in scope with its size and owner, and mark the leavers.
That one sheet answers most planning questions. It shows how much data you are moving, which accounts need destination users first and which drives are too large to leave for the last night. Add a column for the destination address and the OneDrive tenant to tenant migration plan is half written before you buy anything.
Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.
Published 12 October 2026. Licence, limits and prerequisites come from the Microsoft Learn page on cross-tenant OneDrive migration, with account preparation from step 4, precreating users and groups. The FastTrack service terms come from cross tenant migration on Microsoft FastTrack.