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.