Skip to download
RecoveryTools

RecoveryTools · Secure SharePoint migration software for IT administrators

SharePoint Migration Tool

Migrate sites and subsites, document libraries, generic lists and list items between two Microsoft 365 accounts with permissions, file versions and metadata intact. No PowerShell.

Download free trialWindows installer · 35 MB, downloads a Windows installer file, 35 megabytes

No credit card, no sign-up. Every feature unlocked, only the item count is capped.

Screenshot of a SharePoint migration in progress

Support And Licensing At A Glance

Trusted by Microsoft Certified Partners

Microsoft® Certified Partners Rely On Our Tools

Managed service providers, IT teams, consultants and SharePoint professionals who hold Microsoft Partner status use this enterprise-grade SharePoint migrator for their client cutovers. They keep coming back for reasons you will recognise: nothing gets left behind, business continuity holds and every migration is easy to check.

Read partner stories

Inside The SharePoint Migration Tool

Every Migration, One Screen At A Time

This is the actual workflow. It starts at the migration wizard and ends with the report.

SharePoint migration tool discovering sites over OAuth 2.0

SharePoint To SharePoint Migration

Move A Site From One Microsoft 365 Account To Another

RecoveryTools SharePoint Migrator copies sites, subsites, libraries, lists and list items from one Microsoft 365 account to another. It supports tenant to tenant moves, mergers, divestitures and rebrands. IT admins handle tenant to tenant moves in one interface, with no PowerShell scripts to write or maintain.

  • Sites, subsites, libraries, lists and list items in one migration.
  • Permissions, file versions and metadata carried across.
  • Interactive OAuth 2.0 sign-in and a Test connection button on both sides.
  • Discover every site, then untick what you want to skip.
SharePoint data migration filters for file type and version history

SharePoint File Migration Filters And Fidelity

Decide What Content Migrates And At What Fidelity

The software lets you include or exclude files by type, keep every version or only the last few, and preserve permissions, authors and timestamps. See SharePoint version history migration for how versions behave after a move. Admins control scope and fidelity before cutover, so enterprises skip clutter and keep the metadata auditors expect.

  • Include or exclude by file type.
  • Full version history and broken-inheritance permissions.
  • Author, created and modified metadata preserved.
  • Incremental migration moves new and changed items only.
SharePoint migration user mapping loaded from a CSV

User Mapping And Scheduled Migrations

Match Users Across Accounts, Then Schedule The Migration

SharePoint Migrator pairs every source user with a destination user, so permissions land on the right accounts. Users match by email automatically, a CSV template covers the rest and migrations can be scheduled migrations to start daily or on a recurring plan. The mapping rules are in how to migrate SharePoint permissions to another tenant. IT teams fix identity gaps before cutover and can start migrations after hours, so staff keep working during the day.

  • Auto by email or custom mapping from a CSV.
  • A downloadable template and a per-row Add mapping button.
  • A departed employee never stops the batch.
  • Daily or recurring schedules that start unattended.
SharePoint site migration in progress with live counters

Live Progress And Reports

Watch The Migration, Then Prove What Landed

A real-time dashboard in the software shows counts, throughput and an ETA while the migration is in progress. A report then lists every folder and file with its status and the total data moved. Admins read progress at a glance and enterprise teams keep the report as evidence for stakeholders.

  • Total, migrated, skipped and failed counters.
  • Throughput in items per minute with a live ETA.
  • A live log naming every item as it copies.
  • A per-item report available for review or audit.
SharePoint export tool restoring a backup folder to a site

Export A Site To Disk And Put It Back

Your Own Site Copy, Plus Software To Return It

RecoveryTools SharePoint Migrator exports a site to a local or network folder with its folder tree, versions and metadata. The SharePoint Backup Tool writes the export and the SharePoint Restore Tool uploads it back into any site with its structure intact. IT teams keep an offline copy of a site before a risky change and can restore it into any site when needed.

  • Export to a drive or a network share.
  • Versions and metadata stay inside the exported folder.
  • The tree is rebuilt at the far end, not flattened.
  • Identical filters and reporting apply in both directions.
SharePoint migration report with per-item status

Site Storage Scan Before Cutover

Find Cold Site Data And Price The Cleanup

A read-only storage scan inside SharePoint Migrator shows how much site content has not changed in years. You get a size estimate of what you can archive before the migration. Admins size the move and plan the cutover window early, and enterprises can archive cold content before moving it.

  • Read-only, safe to use on production.
  • Reports how much data is cold and archivable.
  • Estimates the storage you would save.
  • Feeds straight into an export or a migration.
Fidelity

What Does It Migrate? Everything A SharePoint Site Carries

RecoveryTools SharePoint Migrator moves files and everything attached to them. These twelve items migrate with the content.

Configuration and code are a different matter, and the next section sets out exactly what does not come across.

SharePoint Migration Limitations

What Does Not Come Across

The software copies content and not configuration or code. Here is what stays behind, listed before you buy.

None of this is a gap in one product. Content moves; configuration and code are rebuilt at the destination. A vendor who tells you otherwise is selling you a surprise for cutover weekend.

Features

Key SharePoint Migration Challenges, Solved

SharePoint Migrator is built for IT administrators, SharePoint professionals, migration specialists and admins on their first project. Every feature below solves a point where migrations commonly fail.

Site Discovery And A Read-Only Scan

RecoveryTools SharePoint Migrator discovers every site the account can reach with its libraries and lists, so you can inventory your environment before you commit. The read-only SharePoint Storage Analysis tool reports total size and how much has not changed in years. IT admins get a clear inventory up front, so scope and effort are agreed before cutover and not found mid-project.

Selective SharePoint Data Migration

Filters in the software cover date, file size and file type, so you include or exclude content before anything moves. Archived material stays at the source, so you do not pay to move it twice. Enterprise teams move only content users need, which shortens the migration window and keeps clutter out of the destination.

Version History Migration

SharePoint Migrator migrates every file version, only the latest version or a set number of recent versions. Major and minor versions are handled separately, with created and modified dates kept on every item. Admins in regulated teams keep full version history for compliance, or cap it to move faster.

Delta Migration, Skip Previously Migrated

Delta migration in the software moves only new or modified items on a re-run. Previously migrated data is skipped, so new files arrive without duplicates and nobody works out by hand what changed. IT teams can finish a bulk move first and add a short delta migration on cutover day, so users lose little working time.

Batch And Bulk Migration

RecoveryTools supports bulk migration of multiple sites at once. Concurrent migration splits the work into batches that move side by side, so you finish inside the maintenance window with minimal downtime. Enterprises with many sites finish in fewer maintenance windows, which keeps downtime short for users.

Schedule SharePoint Migration

SharePoint Migrator schedules a migration to start once, daily, weekly or monthly. It works unattended through nights and weekends, and a summary report waits for you when the batch finishes. Admins start migrations after hours and read the summary report the next morning.

Microsoft Modern Authentication

The software signs in with OAuth 2.0 through Microsoft Entra, and MFA and conditional access still apply. Data moves over encrypted channels with no data stored on our servers, and credentials are never kept in plain text. Security teams keep MFA and conditional access in place, so no weaker sign-in policy is needed for the migration.

Map Users And Permissions From CSV

RecoveryTools reads one CSV file to map source users to destination users, so accounts resolve to destination identities automatically. The same file maps sites, and unmatched users are flagged before you migrate. Admins fix account mismatches in one file before cutover, so permissions reach the right people on day one.

Real-Time Progress Tracking And Reports

SharePoint Migrator tracks migration progress in real time on its built-in dashboard. Summary and detailed reports list every item with what succeeded, what was skipped and why, which is the evidence an auditor asks for. IT teams answer stakeholder questions from the dashboard, and auditors get per-item evidence from the reports.

Concurrent Migration, Up To Three At Once

The software starts up to three migrations side by side, and a migration and an export can go together. Every one gets its own dashboard card to stop, pause or manage the migration, and a warning appears if two would overlap. Enterprise teams can move one site and export another at the same time, with a warning before two migrations overlap.

Site Mapping And User Mapping

By default a source site lands at the same URL. RecoveryTools site mapping sends it to a different URL when you reorganize sites under a new structure. User mapping matches people by sign-in address, or from a CSV when addresses differ. Admins reorganize site structure during the move, so the destination tenant starts clean and not as a copy of old layouts.

Large File Transfers Resume In Chunks

SharePoint Migrator uploads big documents in resumable chunks, so one dropped connection costs the current chunk and not the file. Failed items retry automatically, a re-run migration picks up where it left off and the same migration cannot start twice. IT admins can leave long uploads unattended, because a dropped connection resumes and failed items retry without a restart.

Trusted For SharePoint Data Migration

RecoveryTools, Your Trusted Migration Company

We migrate mission-critical SharePoint estates for enterprises, businesses and organizations worldwide with reliable, enterprise-grade tooling, delivering total peace of mind. Our engineers handle more than 40,000 migrations every year.

SharePoint Migration Software Capabilities

What The Migration Engine Gives You

The software groups its controls in three areas. Select one to see what it covers.

  • SharePoint List Migration At Any Level

    SharePoint Migrator copies generic lists with their items and columns, from a single list up to an entire site collection. You can select the tree all the way down.

  • Map Metadata Columns That Differ

    RecoveryTools lets you pair source and destination fields when the headings differ, so nothing lands in the wrong column.

  • Keep Managed Metadata

    The software keeps content types, site columns, term store values and custom columns attached to the item, not stripped.

  • Choose How Permissions Land

    SharePoint Migrator carries unique permissions across or lets items inherit from the destination site.

How It Works

Six Steps From Download To Report

RecoveryTools SharePoint Migrator follows six steps. Every step narrows the migration before data is transferred. For one site taken end to end, see how to migrate a SharePoint site to another tenant.

  1. Add The Source Site

    Install the software on any Windows machine, then add a single SharePoint Online site URL, or discover every site in the account and choose the ones to move.

  2. Authenticate Both SharePoint Accounts

    SharePoint Migrator signs in to both accounts with interactive OAuth 2.0. The Test connection button confirms the source and the destination before you continue.

  3. Discover Sites And Review Scope

    Start discovery and RecoveryTools lists every site the account can reach with its libraries and lists, so the scope is agreed before anything moves.

  4. Map Users And Choose The Destination Site

    Load the user mapping CSV, then choose a new site or an existing one at the destination. The software lets you choose how name collisions resolve.

  5. Apply Migration Filters And Preview

    SharePoint Migrator lets you set date, type, size and version rules, then press Preview to see exactly what the current settings have selected before anything leaves the source.

  6. Start Or Schedule The Migration

    Start the migration immediately or queue it for the maintenance window. The software shows live progress and exports the summary when the batch completes.

Comparison

SPMT And Scripting vs A SharePoint Migration Tool

Microsoft’s SharePoint Migration Tool (SPMT) and native tooling move a small library fine. Beyond that they become error-prone and time-consuming, and SharePoint Migrator covers the parts that are hard to budget for.

SharePoint Migration Tool (SPMT) Limitations Microsoft Documents

Microsoft SharePoint Migration Tool (SPMT)
RecoveryTools SharePoint Migrator
Supports SharePoint Server 2010, 2013, 2016 and 2019 plus local and network file shares as sources. Microsoft states it cannot migrate content from another tenant in Microsoft 365.
Copies sites, libraries and lists from one Microsoft 365 account to another.
You cannot set the destination site template. SPMT decides it from the source and destination sites.
You choose a new site or an existing one at the destination.
Site pages move only by uploading a CSV or JSON file.
Classic and modern site pages are recreated at the destination.
Managed metadata migration is off by default, and taxonomy updates in incremental rounds.
Content types, site columns, term store values and custom columns stay attached to every item.
Master pages, InfoPath forms and custom New, Edit and View forms do not migrate.
What stays behind is listed before you buy, so you know what to rebuild at the destination.
Workflows move to Power Automate only for SharePoint 2010 out-of-box and 2010 and 2013 Designer list, library and content type workflows. Site workflows and workflow history do not move.
Workflows and custom code stay behind, and the limitations list names them before you start.
For large volumes Microsoft advises installing SPMT on separate Windows machines and starting bulk migrations on them in parallel.
Concurrent migration starts up to three migrations side by side from one machine, with an overlap warning.

Microsoft also documents a 250 GB maximum file size and a path under 400 characters for SPMT, so check large files and long paths before any migration. These facts come from Microsoft Learn: SPMT FAQ, file size limits and SPMT troubleshooting.

Why RecoveryTools SharePoint Migrator Fits Tenant To Tenant Moves

SPMT is built to bring SharePoint Server and file share content into Microsoft 365. RecoveryTools SharePoint Migrator is built for the move after that, from one Microsoft 365 account to another. The software maps users and permissions, filters by date, file type and size, schedules migrations and writes per-item reports. Use SPMT for on-premises sources and SharePoint Migrator for tenant to tenant moves.

PowerShell And Native Tooling Compared

PowerShell / native tooling
RecoveryTools SharePoint Migrator
Technical knowledge, command-line scripts and scripting needed beyond a basic copy.
Point-and-click migration setup in this SharePoint migration tool, no PowerShell scripting, no need for PowerShell at all.
Every project needs bespoke scripting work of its own.
SharePoint to SharePoint migration is a first-class route.
Version history is commonly lost or flattened to the latest copy.
Full or capped version history preserved by design.
Permissions re-applied manually at the destination.
Permission levels and group membership mapped automatically.
Re-running a script risks duplicating everything again.
Delta migration moves only what changed since the last migration.
Complex problems surface mid-transfer, hours in.
Discovery and a read-only scan surface the scope before you start.
Reporting has to be built into the script yourself.
Per-item success, skip and failure reports exported as CSV.
You are the support line at 2am on cutover night.
24×7 support from engineers who handle these migrations daily.
Priced per user or per gigabyte, so a large environment costs more.
One licence per machine, per year, whatever the size of the migration.
You find out what the filters selected once the migration is in progress.
Preview reads the selection back before anything leaves the source.
One departed user in a permission set stops the entire batch.
Unresolved users are logged and skipped, never failed.
Free Resource

Planning A SharePoint Migration: The Admin Checklist

Forty-one things worth confirming before the first batch starts. That covers inventory, identity, permissions, URL limits and the cutover window. Written from the migrations our engineers handle.

  • What to count and measure before you scope the migration.
  • The checks that catch failures during planning, not mid-transfer.
  • Cutover-weekend runbook you can hand to the team.
Download free checklist

PDF · no email required

Rather read it on the web? Work through the Microsoft 365 migration planning checklist.

Specifications

Before You Install The Software

Software

Version
26.8
Released
August 2026
Installer size
35 MB
Licence
Per-machine, annual, covers every tool in the installer

Supported Platforms

Source
SharePoint Online (Microsoft 365)
Destination
SharePoint Online, or a local copy on a local drive or network folder
Authentication
Interactive OAuth 2.0, or app-only by secret or certificate
App registration
In your own Microsoft Entra directory, admin consent once
Projects
Four in one installer, this page covers site to site migration

System Requirements

Operating system
Windows 11, 10 and Windows Server · 32-bit or 64-bit
Processor
Intel Core i3 or equivalent, 2 GHz+
Memory
4 GB RAM minimum, 8 GB recommended
Disk space
500 MB for installation, plus space for logs
Runtime
.NET 8 Desktop Runtime and Edge WebView2
Languages
Ten, including the built-in help
Prerequisites
Admin-level access on both sides, outbound access to Microsoft 365
Hard disk
500 MB free for the installer
Product guides
Software guide, datasheet, installation guide, screenshots, video and EULA are linked from the download
FAQs

SharePoint Migration Tool Questions Admins Ask

Can I migrate SharePoint permissions and version history?

Yes, both. SharePoint Migrator maps permissions from source to destination identities, including broken inheritance. The software carries version history in full or capped at the latest few. Managed metadata with content types and term store values stays attached to every item.

Do I need PowerShell or scripting?

No. In RecoveryTools SharePoint Migrator, adding sites, mapping users, filtering and scheduling are all set in the interface, so a non-technical operator can use it. No CSOM, PnP, SPMT command-line, Migration Manager or Power Automate to maintain.

How long does SharePoint migration take?

With any SharePoint migration tool it depends on item count more than size, because Microsoft 365 throttling is applied per request and not per gigabyte. Every version counts as a separate item, so a file with 10 versions is 10 objects, and one terabyte of small files takes far longer than one terabyte of large ones. Raise the parallel threads to push harder on a quiet weekend and lower them during business hours. Start discovery on the SharePoint site first to get a real item count and not a guess.

What are the trial limits?

Every feature is unlocked in the free demo version of RecoveryTools SharePoint Migrator and only the item count is capped, so you evaluate it before purchasing. The cap is 25 items in every document library, and every library carries its own allowance, so a site with several libraries gives you plenty to judge by, and you can migrate document libraries and lists end to end. Discovery, the read-only storage scan and the full reporting are unrestricted.

Can I migrate between two Microsoft 365 accounts?

Yes. SharePoint Migrator signs in to both accounts with modern authentication and moves sites, libraries and lists across. Re-runs are incremental for a clean cutover.

Can I migrate SharePoint without data loss at the source?

Yes. RecoveryTools works copy-only, so there is no data loss, no disruption and continued access on the source. The source is read but never written to, which means users keep working through business hours while the migration is in progress. There is also nothing to roll back: if the result is wrong you simply leave the source in place and start again, because it was never altered.

What cannot be migrated?

SharePoint Migrator moves content with complete data integrity and without losing structure. Everything configured or coded is set up again at the far side. Workflows, custom web parts, solution packages, apps and add-ins, alert subscriptions, recycle bin contents, retention and legal holds, themes, lookup and calculated columns and content approval state all stay behind. The section above sets every one out.

What are the post-migration tasks after it finishes?

Verify before you celebrate. Compare the per-item report against the source counts, spot-check permissions on a few sensitive libraries, then re-run a final delta migration to catch changes made during the window. Update links that still point at the old address. Keep the source in place and read-only for a few weeks, and only decommission the old site once nobody has raised a missing item.

Which licence do I need for one project?

99 US dollars per machine, per year, with a 30-day money-back guarantee. There is no charge per user and no charge per gigabyte, so the cost of a 40 GB project and a 4 TB project is the same. That is usually the cheapest way to handle a one-off cutover, since per-seat tools bill for every account whether or not their content moves. For MSPs or unusual cases, ask us for a custom quote.

What happens to guest and external users?

External users are not carried across as accounts, because a guest is an invitation issued by an organisation rather than content stored inside it. Permissions held by a guest are logged and skipped, and the destination organisation re-invites them afterwards. Sharing links behave alike: an existing link points at the old address and does not follow the content, so links are reissued once the site is live.

Does it move OneDrive, subsites and hub sites?

The software moves subsites with the site collection they sit under, and they keep their place in the tree. Hub associations and site navigation are configuration and not content, so they are set again on the destination once the sites exist. OneDrive is separate from a SharePoint site collection and is not part of this migration, so plan it as its own project.

Is SharePoint migration safe, and what does it store?

Sign-in uses secure OAuth 2.0 against both sides, through an Entra app registration in your own Azure directory, so multi-factor authentication and conditional access still apply, only authorized administrators can start a migration and RecoveryTools works without storing credentials in plain text. There is no service account left behind for your next security review. Content moves over an encrypted transfer from the source machine straight to the destination with no external storage, no staging and no data stored by us, so data integrity is yours end to end, which is what matters for GDPR.

What do I need before a SharePoint migration?

Any Windows machine with .NET 8 and the WebView2 runtime, an account with site collection administrator rights on both SharePoint sites, and outbound access to Microsoft 365 through your firewall. Sign-in uses modern authentication against an Entra app registration that belongs to you, with a one-time admin consent on its permissions. Global administrator is not required for the content itself. Internet speed matters less than you would expect, since throttling rather than bandwidth is usually the limit.

How does sign-in work, and what will my admin have to approve?

Modern authentication only, through an Entra app registration you own, so none of the legacy routes Microsoft retired are involved. A person at the keyboard signs in with interactive OAuth 2.0, which leaves your multi-factor and conditional access policy fully in charge. Unattended work uses app-only access instead, by client secret or by certificate, and the certificate route does not expire on you. Those application permissions want admin consent one time and never ask again.

Can I migrate large SharePoint environments with several migrations at once?

The software handles up to three, and they need not be one kind. A migration and an export can go together. The dashboard tracks every one separately while it works. If two of them are aimed at overlapping content, it warns you up front, and starting the identical migration a second time is blocked, which keeps two migrations from fighting over one incremental catalogue.

What does a delta or incremental migration actually skip?

Anything already at the destination that matches. Enable incremental migration in SharePoint Migrator and a second delta migration moves only what is new or changed since the last one. A long batch during the week and a short delta migration on cutover day is the usual pattern. Every item is counted, so the report shows what moved and what was already there.

What lands in the report, and what if a SharePoint migration fails?

RecoveryTools writes an HTML report to read, a CSV to sort and a plain-text log to search, all to your Documents folder. The source and destination names sit at the top of every one. Every item carries a status of copied, already migrated, excluded or failed. A failure carries its reason with it. The advanced settings used for the migration are written into the log, so nobody has to remember them later. Failed items are copied to a Desktop folder for review.

Still Have A Question?

Our migration engineers can look at your environment with you, tell you what it actually involves and take a request quote for a larger environment or a software customization.

Talk to an engineer

Download The SharePoint Migration Tool And Try One Site

Discovery and the read-only storage scan work without volume limits. Point them at your sites to see the full size of the migration before you plan it.

SharePoint MigratorFree trial · Windows
Trial Pricing