OneDrive Version History After Migration

You finish a OneDrive move, open an important file at the destination and select Version history. One entry shows up. Last month's edits are gone, and nobody told you that would happen.

I see this after almost every tenant move that used a manual copy. This guide explains how OneDrive version history works, which methods keep it, what stays behind even with a tool and how to check the result.

How does OneDrive Version History Work?

OneDrive saves a new version when you change a file. You can open the Version history pane, see earlier versions and restore one. Microsoft's page on restoring a previous version of a file stored in OneDrive says it works with all file types, including Microsoft 365 files, PDFs, photos and videos. Restoring a version makes it the current one and moves the old current version into the list.

Limits decide how far back the list goes. Microsoft's page on how versioning works says versioning is on by default for Microsoft 365 and saves the last 500 versions of a document. When the limit is reached, the oldest version goes first. A work or school admin can also switch versioning off, so some files have little history to begin with.

What Happens to Version History When You Migrate OneDrive?

It depends on the method, not on OneDrive. A version is not part of the file you see in the folder. It lives in the service, so any method that only copies the file you can open copies one version.

Download and upload creates a new file at the destination with a single version. Share and copy does the same. Copying between two synced folders on one PC does the same. If you follow my steps in how to copy OneDrive files to another OneDrive account, expect the current version and nothing older.

Can a Migration Tool Keep OneDrive Version History?

Yes, if it is built to read and write versions. RecoveryTools OneDrive Migrator copies every version of every file, oldest to newest, or the current version only when speed matters more than history. Created and modified dates stay as they were instead of resetting to the day of the move. Every file is hash checked and the source stays read only.

Speed is the cost of full history. Microsoft 365 throttles per request, not per gigabyte, and every version counts as its own object. One file with ten versions is ten objects. A tenant of many small files with long histories takes far longer than the same data in a few large files. I cover timing in how to migrate OneDrive from one tenant to another.

What Version History is Lost Even With a Tool?

No tool can copy what the source no longer holds. Four things stay out of any version copy.

• Versions already pruned. Microsoft keeps a limited number of versions per file. Anything that aged out at the source is gone before a tool reads it.
• Files that were never saved. A document left open and unsaved has no readable copy in the cloud, so ask people to close their work before the move.
• OneNote notebooks. Notebooks are left out of the copy, so export them from OneNote and import them at the destination.
• Retention and legal holds. These belong to the tenant, so set them again at the destination if you need them.

Microsoft also notes that changes to the organization version limits apply to new OneDrive accounts and do not trim existing history. Read the page on setting default organization version limits before you change anything at the source in a hurry.

How do You Check OneDrive Version History Before and After a Migration?

Checking takes under an hour for a small test and saves you from finding gaps a month later. Follow this order.

1. Check the source settings. Ask your admin whether versioning is on and what limit applies to OneDrive accounts.
2. Choose sample files. Select a few files with long histories, like budgets, contracts and shared reports.
3. Record the version count. Right-click the file, open Version history and write down the number of versions and the dates.
4. Decide on all versions or the current one. Keep every version for compliance cases. Choose the current version when the move window is short.
5. Size the window. Count files, not gigabytes, because every version is one more object to copy.
6. Test one account. Copy a single user first with your chosen setting and read the report.
7. Compare after the copy. Open Version history on the same files at the destination and match the count and dates against your notes.

Should You Copy All Versions or the Current Version Only?

Most teams never open an old version, so the current version often does the job. Keep every version when a file has legal, audit or contract value, or when people use the history to see who changed what. If you are unsure, copy the current version for the first batch, then use a second pass for the folders that need history.

The same question comes up for SharePoint libraries, and I answer it in SharePoint version history migration.

What are the Best Practices for Keeping OneDrive Version History?

• Decide early. Set the version choice before the first batch starts, because changing it later means copying again.
• Ask people to save and close. Open unsaved work has no readable copy in the cloud.
• Do not trim at the source. Never cut version limits right before a move.
• Keep the source until you verify. Hold the old account until the comparison is done.
• Keep the report. A line per file with its version count is your proof that the history arrived.

Which Mistakes Lose OneDrive Version History?

Four show up again and again. First, using a manual copy for accounts that need history. Second, assuming a tool copied versions without checking the setting. Third, cutting version limits at the source before the move. Fourth, deleting the old account the same week.

If the move is part of a bigger plan, read OneDrive cross tenant migration for the full list of what changes at the destination.

My Verdict on OneDrive Version History After Migration

Version history survives only when your method is built to carry it. Manual copies bring the current version, a version aware tool brings the list and nothing brings back what Microsoft already removed.

Decide how much history you need before you choose a method, test one account and compare the counts. That one habit saves most of the pain I see after moves.

Frequently Asked Questions

Published 16 October 2026. Version limits and restore steps come from Microsoft's pages on restoring a previous version in OneDrive, how versioning works and default organization version limits. Product behavior comes from the RecoveryTools OneDrive Migrator page. Your tenant limits may differ from the defaults.