THE BOTTOM LINE
Most organisations don’t need an expensive migration tool. Here’s why.
After migrating 200+ client environments over a decade, the pattern is consistent: roughly 80% of SharePoint migrations are structurally simple. File shares to SharePoint Online. SharePoint on-premises to SharePoint Online. Basic tenant moves. These don’t need a $6,000-$18,000 tool. They need a team that knows what they’re doing using the right free tools, efficiently.
SharePoint Designs’ approach uses Microsoft’s own SPMT as the migration engine, paired with custom PnP PowerShell scripts for site provisioning, metadata mapping, and permission validation. No third-party licensing. No per-user fees. No annual subscriptions. The client pays for the migration not a software markup.That remaining 20%? Complex workflows (Nintex, InfoPath,
SharePoint Designer), deeply nested permissions, tenant-to-tenant M&A mergers, or migrations from Google Workspace, Box, or Dropbox that’s where paid tools earn their price tag.The question isn’t “which tool is best?” It’s “does your migration actually need a $6,000 tool, or is the free one enough?” For 8 out of 10 organisations, the answer is the free one.
QUICK DECISION TREE
October 2026 marks the end of extended support for SharePoint Server 2019. As a result, many organizations are moving to the cloud. The migration tool market is now crowded, ranging from Microsoft’s free tool to enterprise platforms that charge $18,000 annually, with numerous options in between, each claiming to be the best choice.
The noise is real. The stakes are real, too. Choose the wrong approach, and you either pay for software you don’t need or hit problems your free tool can’t solve halfway through a migration.
This guide aims to clarify the complexities of the SharePoint migration tool landscape by drawing on extensive practical experience. Our insights are grounded in the completion of over 200 client migration projects, encompassing a diverse range of scenarios such as file share transitions, legacy SharePoint farm upgrades, Google Workspace tenant migrations, and M&A consolidations.
Based on this applied methodology, we present a detailed analysis of each tool’s strengths and limitations, as well as recommendations for tool selection tailored to specific organizational needs.
Its strength is file share to SharePoint Online migration. SPMT delivers bulk document migration with metadata preservation, incremental sync, and parallel agent support. Production throughput is 1-2 TB per agent per 24 hours. You may deploy up to 50 agents, though throttling typically limits effective concurrency to 10-15 agents.
Best for: File share to SharePoint Online migrations of any size. SharePoint on-prem to SharePoint Online with standard content and straightforward permissions. Organizations that want to avoid third-party licensing and have IT staff comfortable with PowerShell.
Best for: Organizations running multiple SPMT agents who want centralized monitoring. Basic Google Workspace to SharePoint Online file migrations.
Best for: Mid-to-large organizations with complex SharePoint-to-SharePoint migrations. Tenant-to-tenant M&A work. IT consulting firms that run migrations regularly the per-machine licensing model makes economic sense when you’re using the tool constantly.
Best for: Large enterprise migrations (5,000+ users, 5TB+ data). Multi-platform consolidations, Google + Box + on-prem into Microsoft 365. M&A scenarios requiring co-existence. Regulated industries with detailed audit requirements.
Best for: Email-first migrations Gmail to Exchange Online, IMAP to Exchange Online. Organizations migrating from multiple non-Microsoft sources. MSPs and consultants who need a single tool that works across diverse client environments without infrastructure.
Enterprise-grade migration and governance for complex, highly customized SharePoint environments. Strong scheduling, detailed reporting, and robust handling of intricate permission structures.
Part of Quest’s broader Microsoft 365 management suite. Pricing starts around $2,999. Worth considering if your organization already operates in the Quest ecosystem or faces permission structures that consistently defeat other tools.
A SaaS migration platform supporting Google Workspace, SharePoint, Teams, and Exchange. Stands out for its co-existence features during transition, which are useful when you can’t afford a hard cutover.
Per-user pricing starts at $9.50/user (one-time). A reasonable option for mid-size Google-to-Microsoft migrations where AvePoint is too much, and Migration Manager is too basic
A modern, SaaS-first tool that earns its place on this list for one feature: its free preflight scan.
Upload your source environment details, and Movebot identifies every file that would fail due to path length violations, restricted characters, or size limit breaches before you start.
That preflight visibility alone prevents days of cleanup. Migration licensing is per-GB.
A cloud-based migration tool is especially strong for Google Workspace-to-Microsoft 365 moves.
Google recommends CloudM as a migration partner, which is especially meaningful when you’re migrating away from their platform and want a smooth process.
Per-user pricing. Solid choice for organizations making the Google-to-Microsoft transition.

After working through migrations for 200+ clients across 23 countries, the pattern is clear: most migrations fail not because of the tool, but because the destination wasn’t properly designed before the data moved. That’s where the real work lives.SharePoint Designs’ migration methodology runs on three layers.
Before a single file moves, we build the target SharePoint Online environment correctly. Modern communication sites for intranets. Team sites for collaboration. Hub site navigation and information architecture. Metadata columns, content types, managed terms.
All of this is provisioned using PnP PowerShell and SharePoint site templates before migration day. The mistakes we see most often in DIY migrations happen here: people migrate into a flat document library structure with no taxonomy, metadata, or governance. The files arrive, but the environment is a mess.
This is the step most teams skip. Our validation process leverages custom PowerShell scripts to confirm that permissions match, content counts are accurate, and metadata is mapped correctly. Specifically, the validation checklist includes:
Without systematically completing these checks, teams lack assurance that the migration is complete and accurate.
They hope the migration succeeded, but cannot verify its integrity. Our approach ensures definitive confirmation that all content has been accurately migrated.
We use SPMT (or Migration Manager for Google sources) for the actual data move. Pre-migration scans identify file name issues, path length violations, and permission conflicts before we start.
Migrations run in waves by department or site, not everything at once, which keeps the scope manageable and the cutover windows short. Delta sync handles the final pass, capturing changes made to source files during the migration period.
For the 20% of migrations that genuinely need them, tenant mergers, Nintex and InfoPath conversions, and non-Microsoft platform moves, we license ShareGate or MigrationWiz on a per-project basis.
The client doesn’t carry the annual subscription. SharePoint Designs absorbs the tool cost into the project fee. The client pays for the migration, not the software.
Microsoft’s SharePoint Migration Tool (SPMT) is the best free option. It supports migration from file shares and SharePoint Server 2010/2013/2016/2019 to SharePoint Online, with metadata preservation and incremental sync.
For Google Workspace sources, Migration Manager (also free) is the right choice.
ShareGate pricing starts at $5,995/year for one machine activation (Migrate Essentials) and goes up to $17,995/year for 25 machine activations (Migrate Enterprise).
All plans include unlimited data transfer at a per-machine rate, not per GB or per user.
No. SPMT doesn’t support Google Drive as a source. Use Microsoft’s Migration Manager (free, built into the SharePoint admin center) for basic Google Drive to SharePoint Online migrations.
For email plus files together, MigrationWiz or CloudM are better options.
No. SPMT doesn’t migrate SharePoint Designer workflows, Nintex workflows, or InfoPath forms. These need to be rebuilt in Power Automate or Power Apps after migration.
No migration tool handles this fully; it’s one of the genuine constraints of the SharePoint migration tooling ecosystem.
It depends on data volume and complexity.
- Small environments (under 500GB, fewer than 500 users) typically take 2-4 weeks.
- Mid-size environments (500GB-5TB, up to 5,000 users) take 6-12 weeks.
- Large enterprise migrations (5 TB+, 5,000+ users) can take 3-6 months.
- SPMT moves 1-2 TB per 24-hour window per agent.
- Multiple agents run in parallel for larger migrations.
Use Microsoft’s free SPMT tool combined with PnP PowerShell scripts for site provisioning and post-migration validation. This approach has zero software licensing costs and covers approximately 80% of migration scenarios.
A migration partner like SharePoint Designs can execute this for a fixed project fee; the client pays for the expertise, not a tool subscription.