RecoveryTools
SharePoint

How to Migrate SharePoint Version History to Another Tenant

Jamie Kaler
· 9 minute read
Quick Answer

SharePoint version history moves by 4 routes between tenants. Native cross tenant, SPMT, manual download or migration software. Microsoft does not state versions for the native move. SPMT copies versions when its version setting is On. Manual download and upload carries the latest version only. RecoveryTools SharePoint Migrator copies versions with the content. Destination limits can delete copied versions so test one library.

Does SharePoint Version History Migrate Between Tenants?

Yes, when the method copies versions. SPMT has a version setting for it and software built for versions copies them oldest to newest. A manual download and upload flattens a file to its latest copy. Microsoft's cross-tenant overview does not say whether versions come across so confirm that in its step guides.

So the question people should be asking is different. Not whether SharePoint version history moves but whether it survives the first week at the destination.

That is where projects get caught. A migration report says 40,000 files landed with full history. Three weeks later someone opens a contract and finds four versions where the source had sixty.

Jamie Kaler

Nobody lost those versions during the transfer. They arrived and then the destination library deleted them according to a policy nobody checked.

Marketing Head and Content Strategist, RecoveryTools

Which Routes Carry SharePoint Version History?

Who it suits. Technical migration admin Extra application. SPMT or migration software, by route

Four routes exist between tenants and they treat version history differently. Price and scope differ too, which is covered in how to migrate a SharePoint site to another tenant.

RouteVersion historyControl you get
Native cross tenantNot stated on Microsoft's overview pageCheck the step guides before you rely on it
SPMTCarried when the version setting is OnOff, all versions or a number you set
Download and upload by handLostLatest version only, every time
Migration software built for versionsCarriedDepends on the product so test one library

Swipe the table sideways to see every column.

RecoveryTools SharePoint Migrator sits in that last row and copies version history with the content, permission levels and metadata. Test one library first and compare the version counts.

SPMT deserves a note. Its settings page lists a version option under Filters. Off moves the latest copy only. On retains every version or you enter a number to cap the history.

Why does Version History Vanish After a Clean Migration?

Few projects plan for this part and it has nothing to do with your copy method.

Microsoft added automatic version history limits to SharePoint Online to optimize version storage. When a library uses the Automatic setting, SharePoint decides how many versions to retain.

Say your copy brings 60 versions. When versions go past the library limits, Microsoft marks them for permanent deletion and they bypass the recycle bin. A low limit at the destination removes history you just copied.

Three symptoms give it away:

  • Version counts drift apart. Source and destination matched on migration day and stopped matching a month later.
  • Counts drop after edits. A library over its limit purges older versions every time a user saves a new one.
  • Old versions go first. The newest copies look fine so a spot check of recent files finds nothing wrong.

What are the SharePoint Version History Limits Now?

Microsoft sets defaults and the numbers decide how much SharePoint version history your destination will store.

  • New libraries default to manual limits. 500 major versions, no expiration, applied to libraries created after the policy is set.
  • Manual count range at organization level. Anything from 100 to 50,000 major versions.
  • Expiration has a floor. Either never or a custom value of more than 30 days.
  • Automatic mode hands the decision to SharePoint. No count to set, no expiry to agree, the algorithm chooses.

Two rules in that documentation matter more than the numbers, because teams view the settings page and assume more than it says.

First, an organization level edit reaches new libraries only. Microsoft states that edits to organization level version history limits will not update the limits on existing document libraries and applying them to existing libraries at organization level is not supported. Edits take up to 24 hours to show on new libraries.

Second, lowering a library level count does not wipe the excess at once. Versions are trimmed gradually and Microsoft documents the pace: up to 20 of the oldest versions are purged every time a new version is created, until the library reaches its limit. A busy document loses its history quietly over a few weeks.

How do You Prepare the Destination Library for Version History?

Who it suits. Technical admin who owns the destination library Source file size limit. Count limit of 100 to 50,000 major versions at organization level Extra application. None, because a browser is enough but PowerShell suits many libraries

Five minutes of setup at the destination protects the entire SharePoint version history migration. Do it before the first batch starts, never after.

  1. Open the destination library settings. Go to the library, open Library settings, then Versioning settings.
  2. Set Document Version History to Manual. Automatic hands the decision to SharePoint, including how much history remains.
  3. Select No time limit. An expiry window silently deletes old versions on a timer.
  4. Raise the count above your deepest file. Find the source file with the most versions, then set the limit higher than that number.
  5. Check the organization default too. New libraries inherit it so a site created mid project gets the old policy.
  6. Move one library and open a file. If the version count matches the source, the policy is right and you can start the rest.

Tenants with hundreds of libraries do this with PowerShell rather than clicking. The cmdlet takes a count limit, a minor version limit and an expiry in days, with zero meaning never.

Migrator options step showing the full version history checkbox
The Full version history checkbox is the first setting in the options step.

Copy SharePoint Libraries With Their Version History

RecoveryTools SharePoint Migrator is an Easy to Use, graphical interface based utility that copies sites, libraries and lists between Microsoft 365 tenants with permission levels, version history and metadata. The software can copy versions from oldest to newest and is capable of a delta pass that catches edits made after the first copy. RecoveryTools SharePoint Migrator allows you to map users and sites from a CSV file and is able to resume a copy that stops. Versions, permissions and metadata are retained on the destination, while lookup and calculated columns, workflows and Power Automate flows do not move.

Works on Windows 11, 10 and Windows Server 2022.

How Much Storage does Version History Use?

Every version occupies storage in your tenant quota. That is the reason Microsoft built automatic trimming and it is the reason somebody in your organization will ask you to switch it on again.

Answer that question with numbers rather than a policy argument. Pull the version counts from the source and the picture is lopsided: a small group of files carries most of the history while the bulk of the library sits on two or three versions apiece.

That shape gives you a sensible plan. Retain full history on the libraries where it means something: legal, finance and contracts. Then set a tighter count on the libraries where version 47 of a meeting agenda serves nobody.

Settle the policy during planning rather than on cutover weekend, alongside the rest of the Microsoft 365 migration planning checklist. Decide it before cutover, not after. Trimming later is the slow gradual purge described above and you cannot bring those versions back.

Does List Item Version History Migrate as Well?

List items carry version history too and it moves with the list on the same routes. One difference catches admins out.

The organization level version limit settings apply to document libraries, not to lists. A list retains its own versioning configuration so copying a library policy across your tenant does not touch any list. Check list versioning separately at the destination, especially on the lists that power a process rather than store documents.

Columns and content types are their own task, set out in how to migrate SharePoint document libraries with metadata so this post remains on version history.

How do You Verify Version History Landed?

Who it suits. Non technical site owner or admin Extra application. None, because a browser is enough

A finished migration task and a full version history are two different claims. Check the second one directly.

  • Start with your deepest files. Find three source files with the most versions and count them at the destination, one by one.
  • Open a version, do not trust the number. A version row that will not open is worse than a missing one, because the count looks right.
  • Check the library limits. If the count limit sits below your source counts, the policy is still wrong. Fix it before the first batch.
  • Confirm dates came across. Created and modified stamps should match the source, not the migration date.
  • Check access while you are there. Versions are no use to somebody without access so pair this with how to migrate SharePoint permissions to another tenant.
  • Check again two weeks later. This is the one step teams omit and it is the only one that catches gradual trimming.

Retain the source tenant untouched while you verify so a failed check costs an afternoon instead of a dataset.

Frequently Asked Questions

Does Microsoft Say Cross-Tenant Moves Carry Versions?

No. Microsoft's cross-tenant overview does not say whether versions come across. Confirm that in its step guides before you rely on the native move.

Does SPMT Copy Version History?

Yes. Its settings page lists a version option under Filters. Off moves the latest copy only and On moves every version or a number you set.

Do Destination Libraries Apply Their Own Version Limits?

Yes. Microsoft marks versions that go past a library's limits for permanent deletion. Check the destination policy before the first batch.

Is 500 the Default Major Version Limit for New Libraries?

Yes. New document libraries default to manual limits with 500 major versions and no expiration. Organization level limits range from 100 to 50,000 major versions.

Can You Confirm Versions Landed by Opening a File?

Yes. Find three source files with the most versions and count them at the destination. Open a version too, because a row that will not open is worse than a missing one.

Can You Recover Trimmed Versions From the Recycle Bin?

No. Microsoft says versions that go past the limits are marked for permanent deletion. They bypass the recycle bin so you cannot recover them from it.

Does Raising the Organization Limit Fix Existing Libraries?

No. Microsoft states that organization level edits do not update limits on existing document libraries. Set existing libraries one by one, by hand or with PowerShell.

Where Should You Start With Version History This Week?

Open one destination library and look at its versioning settings. That single screen tells you whether your SharePoint version history migration is safe or quietly on a timer.

Then find the file in your source with the deepest history and note the number. Your destination count limit has to sit above it and your storage plan has to account for it.

Two checks, ten minutes. Both are far cheaper than explaining to a legal team why a contract lost fifty versions.

Jamie Kaler
Jamie Kaler Marketing Head and Content Strategist, RecoveryTools

Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.

Published 6 October 2026. Version limits and trimming behavior quoted above come from set default organization version limits, set version limits for an individual document library, Set-SPOListVersionPolicy and the SPMT settings reference.