RecoveryTools · Secure OneDrive migration software for IT administrators
Copy OneDrive for Business accounts from one Microsoft 365 organization to another with the folder tree, the full version history and the original dates intact. Every file is hash checked, and the source is never changed.
No credit card, no sign-up. The demo copies up to 10 files per person, for up to 10 people.
Screenshot of a OneDrive migration in progress
Managed service providers, IT teams, consultants and Microsoft 365 administrators who hold Microsoft Partner status use this enterprise-grade OneDrive migrator to move user accounts during their client cutovers. They keep coming back for reasons you will recognise: nothing gets left behind, people keep working through the move and every run is easy to check.
Read partner storiesEvery Job, One Screen At A Time
This is the actual workflow. It runs from the migration wizard through to the report at the end.
OneDrive migration in its primary form. Connect the source tenant and the destination tenant with OAuth 2.0, test both, then complete Source, Destination, Options, Migrate and Report. Discover every OneDrive account in the tenant or name a single user.
Copy settings control how much fidelity is kept and how hard the run pushes. Choose all supported versions or the current one, say what happens if a file already exists, decide whether direct sharing is re-created, and set how many people copy at the same time.
A OneDrive belongs to one person, so the mapping decides whose files land where. The suggested match sends every source OneDrive to the same address on the destination tenant. Where addresses differ after a rebrand, switch to Custom, download the template and import a CSV pairing every source user with the right destination user. Unresolved users are logged and skipped rather than failing the run, so a departed employee never stops a migration.
The Migrate step shows counts, throughput and an ETA with a live log of every item. When it finishes, the report lists every OneDrive folder and file with its status and the total data moved, per user.
A file count is not proof. Every copied file is hash checked against the source with QuickXorHash, and a file that does not match is not quietly left behind as though it were fine. A copy that could not finish is cleaned up, and anything already sitting at the destination is never deleted or overwritten.
When the line drops, copying waits and carries on by itself once it is back, the way Gmail does. Nothing fails because of the outage. Interrupted downloads resume where they stopped, and a slow connection is detected and explained, with fewer files copied at once so every one keeps moving. Microsoft throttling is handled with automatic waits and retries.
The question behind every OneDrive migration is not whether the files arrive. It is whether everything attached to them arrives too. All twelve of these move with the content.
Tenant settings and anything a person configured are a different matter, and the next section sets out exactly what does not come across.
What Does Not Come Across
What is a OneDrive migration able to carry, and what stays behind? Every honest answer matches, whichever tool you buy. Here is ours, before you pay rather than after.
None of this is a gap in one product. Files move, and tenant settings are set again on the destination. A vendor who tells you otherwise is selling you a surprise for cutover weekend.
Built for IT administrators, Microsoft 365 specialists, migration consultants and the admin running their first tenant move. Every feature here addresses a specific point where OneDrive migrations commonly fail.
Everyone in both organizations loads before you commit, with the size of every OneDrive beside the name. Thousands of people load in well under a second. The source is opened read only, so discovery changes nothing.
Copy every folder in a person's OneDrive, or name only the ones that matter, for example Documents and Desktop. Untick anyone you are not moving yet, and the run skips them without affecting the rest of the batch.
Copy every version of every file, oldest to newest, for a compliance case. Or copy the current version only when the window matters more than the history. Created and modified dates stay as they were rather than resetting to the day the migration ran.
Run the same OneDrive migration again and only new files move. Files already at the destination are skipped rather than overwritten, so the long batch runs during the week and a short pass on cutover day catches whatever changed since.
Several people are copied at the same time, biggest OneDrive first, so one large account is not left running alone at the end. You set how many people copy at once, and 4 is the recommended starting point.
Set a start time and leave it. The run begins at the hour you picked, for example overnight, and the PC is kept awake while it waits and while it copies.
Sign in with Microsoft, use the Microsoft Graph PowerShell app, or bring your own app registration with a client secret or a certificate. The tool can create its own app in both organizations with the least access it needs, read only on the source and write on the destination.
Save the suggested list, edit it in Excel, import it back. Comma, semicolon or tab separated, UTF-8, UTF-16 or older Excel files, and duplicates or unknown people are reported line by line rather than failing the file.
Percent, files, data copied, speed and a time left with the expected finish. A people list shows who is copying, waiting or done. When it ends you get an HTML report that prints to PDF and a CSV with one line per file.
Stop a run and pick it up later. Retry copies only the files that failed rather than starting again, and progress also shows on the Windows taskbar so you can watch it without keeping the window in front.
OneDrive for Business to OneDrive for Business, between two organizations or inside the same one. The tool stops a person being copied onto their own OneDrive, which is the mistake that costs an afternoon to unpick.
Big files download and upload at the same time in resumable chunks, and the chunk size follows the speed of the line. A dropped connection costs the current chunk rather than the entire file.
RecoveryTools, Your Trusted Migration Company
We move mission-critical Microsoft 365 data for enterprises, businesses and organizations worldwide with reliable, enterprise-grade tooling, delivering total peace of mind. Our engineers run more than 40,000 migrations every year.
What The Migration Engine Gives You
Three groups of controls decide which OneDrive migration features a project needs. Select one to see what it covers.
Take every folder in a person's OneDrive, or only the ones you name, for example Documents and Desktop.
The tool suggests a destination for every person by sign-in name, email name or display name. Change any match before you start.
Created and modified dates arrive as they were rather than resetting to the day the migration ran.
Re-create direct sharing for people mapped to the destination, with the same read or edit access, or let the files arrive private.
When Microsoft 365 slows the tool down it copies fewer files at once, and more again when the service allows it.
A stopped migration picks up where it left off, and retry moves only the files that failed rather than copying everything again.
The destination tree matches the source, so the paths people have bookmarked keep making sense.
Move a OneDrive to another person in the same organization, with a guard that stops anyone being copied onto their own account.
Every previous run is listed with its result, and the HTML or CSV report opens in one click.
If a file already exists at the destination, skip it or keep both. Existing destination files are never deleted or overwritten.
Every failure names the file, the person and the reason, so you fix the cause rather than guessing at an error code.
One line per file with its path, versions, content check and sharing, written in the list format Excel expects in your region.
The order matters. Every step narrows the OneDrive migration before anything is transferred. Settle the wider project first with the Microsoft 365 migration planning checklist.
Install the software on any Windows 10 or 11 machine, then connect the source organization. A Global Administrator or Privileged Role Administrator signs in once and the tool sets up its own read only access.
Connect the destination organization the same way, with write access this time. Both cards show Connected and name the account that set them up, so there is no doubt which tenant is which.
Everyone in both organizations loads with the size of their OneDrive beside the name. Untick anybody you are not moving yet, and the header keeps a running count of who is selected and how much data that is.
The tool suggests a destination for every person. Change any match, or save the list as CSV, edit it in Excel and import it back. It blocks you from sending two people to the same OneDrive.
Choose all versions or the current one, what happens if a file already exists, whether direct sharing is re-created and how many people copy at once. The pre-flight check then counts people, files and data, and names anyone who cannot be copied yet.
Start the copy, or set a time and let it begin overnight. Watch the speed and the expected finish, then read the HTML and CSV reports when it ends.
Signing in to two accounts and dragging folders between sync clients works for one person. Past that it turns error-prone and slow, and the gap opens up on the parts that are hard to budget for.
%LOCALAPPDATA%\RecoveryTools\OneDriveMigrator holds reports, logs and saved connectionsVersion history yes, sharing only in part. Versions move in full, oldest to newest, or you copy the current version only when the window matters more than the history. Created and modified dates stay as they were rather than resetting to the day the run happened. For sharing, direct access is re-created for people mapped to the destination, with the same read or edit rights and no invitation emails. Sharing links, groups and anyone outside the organization are listed in the report so you can set them up again.
No. Adding tenants, pairing users, filtering and scheduling are all set in the interface, so a non-technical operator can run the job. There is no Graph script to write, no PnP module to install and nothing to maintain after the project ends.
It depends on file count far more than on total size, because Microsoft 365 throttles per request rather than per gigabyte. Every version counts as its own object, so one file with ten versions is ten objects. A tenant of many small files takes considerably longer than the same number of gigabytes held in a few large ones. Run discovery first and size the window from the file count it reports.
Every feature is unlocked in the free demo version and only the copy volume is capped, so you can validate a real migration path before purchasing. Every account in the batch carries its own allowance, and discovery and reporting run without any restriction, which means you can scope the entire project on the trial.
Yes. Sign in to both tenants with modern authentication, pair the users, then move the accounts across. Re-runs are incremental, so the long batch runs during the week and a short delta pass on cutover day catches whatever changed in between.
No. The migration is copy-only. The source account is read but never written to, so people keep working through business hours while the job runs and there is nothing to roll back. If a result is wrong you fix the settings and run it again, and the source is still exactly as it was.
Files move. Anything a person or a tenant configured is set up again at the far side. That covers the sync client and its selective-sync choices, Personal Vault, anonymous sharing links, notification rules, recycle bin contents, retention and legal holds, storage quota and sharing policy, external guest accounts, versions the source already pruned, OneNote sync state and the tenant activity log.
Verify before you celebrate. Compare the per-user report against the source file counts, spot-check sharing on a few sensitive folders, then run a final delta pass to catch anything saved during the window. Ask everyone to sign the sync client in to the new account and pick their folders again. Keep the source tenant in place and read-only for a while rather than deleting it on the day.
No. OneNote notebooks are counted on the Review screen and left out of the copy, and the report names every one that was skipped. Export them from OneNote itself and import them on the new account. The same applies to items shared into the account by somebody else, because those live in that person's own OneDrive.
Yes. Desktop, Documents and Pictures folders that Known Folder Move redirects into OneDrive are ordinary folders inside the account, so they migrate with everything else. On the destination everyone signs in to the sync client once and Known Folder Move picks up again from there.
External users are not carried across as accounts, because a guest is an invitation issued by a tenant rather than content held inside it. Sharing held by a guest is logged and skipped, and the destination tenant invites them again afterwards. Anonymous links behave the same way: one pointing at the old tenant address stops resolving once people move.
Sign-in uses OAuth 2.0 against both tenants through an Entra app registration in your own directory, so multi-factor authentication and conditional access still apply and only an authorised administrator can start a job. Credentials are never written in plain text and no file content is held on any server of ours. The data moves between your two tenants and nowhere else.
A Windows 10 or 11 machine with .NET Framework 4.8, which setup installs when it is missing. You also need a Global Administrator or Privileged Role Administrator of both organizations to sign in once, and outbound access to Microsoft 365 through the firewall. Sign-in runs against an Entra app registration that belongs to you, with admin consent given once.
Yes. Several people copy at the same time inside one run, biggest OneDrive first, so one large account is not left running alone at the end. Four at a time is the recommended starting point. The number of files in flight adapts on its own, fewer when Microsoft 365 slows the tool down and more when it allows.
Anything already at the destination that matches. Turn incremental on and the second pass moves only what is new or changed since the last run. Every file is still counted either way, so the report reconciles against the source rather than showing a gap where the skipped items were.
HTML to read, CSV to sort and a plain-text log to search, all written to your Documents folder, with the source and destination accounts named at the top. Every file carries a status of copied, already migrated, excluded or failed, and a failure carries its reason with it. Fix the cause, run the job again and the delta pass moves only what did not land the first time.
Our migration engineers can look at your two tenants with you, tell you what the move actually involves and quote for a larger estate or a software customization.
Discovery runs without volume limits. Point it at your tenant to see how many OneDrive accounts there are, and how big they are, before you plan the window.
Product demo · add your video embed URL here