RecoveryTools · Secure SharePoint migration software for IT administrators
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.
No credit card, no sign-up. Every feature unlocked, only the item count is capped.
Screenshot of a SharePoint migration in progress
Managed service providers, IT teams, consultants and SharePoint professionals who hold Microsoft Partner status use this enterprise-grade SharePoint migrator to run their client cutovers. They keep coming back for reasons you will recognise: nothing gets left behind, business continuity holds 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.
SharePoint data migration in its primary form. Connect the source site and the destination site with OAuth 2.0, test both, then complete Source, Destination, Options, Migrate and Report. Discover every site in the account or name a single site URL.
The Options step controls what moves and how much fidelity is kept. Include or exclude by file type, keep the full version history, carry permissions with broken inheritance and preserve author and timestamp metadata.
Identities never line up neatly across two accounts. Auto by email re-grants permissions to the same address on the destination. Where addresses differ, switch to Custom, download the template and import a CSV pairing each source user with the right destination user. Anyone left out falls back to the same email, and 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 each folder and file with its status and the total data moved.
Export a site to a local or network folder. The SharePoint Backup Tool keeps the folder tree, the versions and the metadata. When you need it back, the SharePoint Restore Tool uploads that folder into any site with its structure intact.
Before moving anything, run the read-only storage scan to see how much content has not changed in years. You get a size estimate for what you could archive, so the case for a cleanup is a number rather than a guess.
The question behind every migration is not whether the files arrive. It is whether everything attached to them arrives too. All twelve of these move with the content.
Configuration and code are a different matter, and the next section sets out exactly what does not come across.
What Does Not Come Across
What is SharePoint 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. Content moves; configuration and code are rebuilt at the destination. A vendor who tells you otherwise is selling you a surprise for cutover weekend.
Built for IT administrators, SharePoint professionals, migration specialists and the novice admin on their first project. Every feature here addresses a specific point where migrations commonly fail.
Inventory your existing SharePoint environment before you commit. The site discovery process lists every site the account can reach with its libraries and lists, and the read-only SharePoint Storage Analysis job reports total size and how much has not changed in years.
Filter data for selective migration with a date-based filter for selective content, plus file size and file type filters, to include/exclude before anything moves. That leaves archived material behind instead of paying to move it twice.
Migrate every file version for regulatory compliance, migrate only the last version, or configure migration of versions to a subset of versions to cut transfer volume. Major and minor versions are handled separately, with created date and modified date kept on each.
Run that migration again and only new or modified items move. Incremental (delta) migration skips previously migrated data to migrate only newly added data, so newly arrived files land without duplicates and nobody works out by hand what changed.
Bulk SharePoint Online migration moves multiple sites simultaneously, which is the fast and efficient way through a large estate. Concurrent migration splits bulk jobs into batches that run side by side, so you migrate inside the maintenance window with minimal downtime.
Schedule migration jobs to run once, daily, weekly or monthly. The scheduler runs unattended through nights and weekends, and a summary report waits for you when the batch finishes.
OAuth 2.0 authentication through Microsoft Entra, with MFA and conditional access respected. Data travels through encrypted transfer channels in an end-to-end secure transfer, with no data stored on servers of ours and credentials are never kept in plain text. Data stays within your environment.
Feed in one CSV file to map source and destination users, and accounts resolve to target identities automatically. Map sites from it too. Unmatched users are flagged before you migrate, not after.
Track real-time migration progress on the built-in dashboard, then review migration summary and detailed and summary migration reports listing every item with what succeeded, what was skipped and why. It is the evidence an auditor asks for.
Job-based processing in this SharePoint migration tool: run up to three migration jobs side by side, migration and export together if the weekend needs it. Each gets its own dashboard card to stop, pause or manage migration jobs, and it warns you if two would overlap.
By default a source site lands at the same URL. Site mapping sends it somewhere else, which restructuring or reorganization needs when you reorganize sites under new architecture. User mapping matches people by sign-in address, or from CSV when addresses differ.
Big documents upload in resumable pieces, so one dropped connection costs the current chunk rather than the file. This SharePoint migration tool will retry failed items with auto retry on failure, a re-run migration picks up where it left off and no job can start twice.
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 run more than 40,000 migrations every year.
What The Migration Engine Gives You
Three groups of controls decide when to use SharePoint migration tool features and which ones. Select one to see what it covers.
Take a whole site collection, one library or a single list. The tree is selectable all the way down.
Pair source and destination fields when the headings differ, so nothing lands in the wrong column.
Complete metadata preservation: content types, site columns, term-store values and custom columns arrive attached to the item, not stripped. We preserve metadata the way an auditor expects to find it.
Carry unique permissions across or let items inherit from the destination site instead.
Cap the load on Microsoft 365 so a SharePoint migration does not slow everything else down.
Stopped migrations restart from where they left off rather than copying everything again.
The destination tree matches the source, so existing links keep working.
SharePoint to SharePoint or back out to a file system when a project needs it.
Every running and queued migration on one screen, with counts, sizes and current status.
Configurable alerts when a batch finishes, stalls or fails, so the run does not need to be watched.
Each failure names the item, the reason and the retry state instead of a generic error code.
Who started which migration, when it ran and what it changed, exportable for the compliance file.
The order matters. Each step narrows the migration before anything is transferred.
Install the software on any Windows machine, then add a single SharePoint Online site URL or discover every site in the account and pick the ones to move.
Sign in to each side with interactive OAuth 2.0. A Test connection button confirms the source and the destination before you continue.
Run discovery and read what came back. Every site the account can reach is listed with its libraries and lists, so the scope is agreed on paper before anything moves.
Load the user mapping CSV, then choose a new site or an existing one at the destination and decide how name collisions resolve.
Set date, type, size and version rules, then press Preview to review before migration exactly what the current settings have selected before anything leaves the source.
Start immediately or queue for the maintenance window. Track progress live and export the summary when the batch completes.
Microsoft’s SharePoint Migration Tool (SPMT) and native tooling can move a small library fine. Beyond that it turns error-prone and time-consuming, and the gap opens up on the parts that are hard to budget for.
Forty-one things worth confirming before the first batch runs. That covers inventory, identity, permissions, URL limits and the cutover window. Written from the migrations our engineers actually run.
PDF · no email required
Yes, both. Permissions map from source to target identities, including broken inheritance. Version history carries in full or capped at the latest few. Managed metadata with content types and term store values stays attached to each item.
No. In this SharePoint migration tool, adding sites, mapping users, filtering and scheduling are all set in the interface, so a non-technical operator can run it. No CSOM, PnP, SPMT command-line, Migration Manager or Power Automate to maintain.
With any SharePoint migration tool it depends on item count more than size, because Microsoft 365 throttling is applied per request rather than per gigabyte. Each version counts as a separate item, so a file with 10 versions is 10 objects, and a one terabyte estate of small files takes far longer than a one terabyte estate of large ones. Raise the parallel threads to push harder on a quiet weekend and lower them during business hours. Run discovery on the SharePoint site first and the item count is a real number rather than a guess.
Every feature is unlocked in the free demo version of this SharePoint migration tool and only the copy volume is capped, so you evaluate it before purchasing. The cap is 25 items in each 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.
Yes. Add both accounts with modern authentication and move sites, libraries and lists across. Re-runs are incremental for a clean cutover.
No. The migration is 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 it runs. 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.
Content travels 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 each one out.
Verify before you celebrate. Compare the per-item report against the source counts, spot-check permissions on a few sensitive libraries, then run a final delta pass to catch anything that changed 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.
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 run 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.
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.
Subsites move with the site collection they sit under and keep their place in the tree. Hub associations and site navigation are configuration rather than content, so they are set again on the destination once the sites exist. OneDrive is a separate job from a SharePoint site collection and is not part of this one, so plan it as its own piece of work rather than assuming it comes along.
Sign-in uses secure OAuth 2.0 against each side, 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 job and the tool runs 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.
Any Windows machine running .NET 8 with 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.
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.
Up to three, and they need not be one kind. A migration and an export happily run together. The dashboard tracks each one separately while it works. Should two of them be aimed at overlapping content the app raises it up front rather than halfway through, and launching the identical job a second time is blocked outright, which is what keeps two runs from fighting over one incremental catalogue.
Anything already at the destination that matches. Turn incremental on and a second pass moves only what is new or changed since the last run, which is what makes the usual pattern work: a long batch during the week, then a short delta pass on cutover day. Every item is counted either way, so the report tells you what moved and what was already there rather than leaving you to infer it.
HTML to read, CSV to sort and plain-text log to search, all written to your Documents folder. The source and destination names sit at the top of each one. Every item carries a status of copied, already migrated, excluded or failed. A failure carries its reason with it. The advanced settings the job actually used are written into the log, so six months later nobody has to remember. Failed items are copied to a Desktop folder for review.
Our migration engineers can look at your environment with you, tell you what it actually involves and take a request quote for a larger estate or a software customization.
Discovery and the read-only storage scan run without volume limits. Point them at your sites to see the full size of the migration before you plan it.
SharePoint Tenant-to-Tenant Migration · 2 min 41 sec