What Is the SharePoint Migration Tool (SPMT)?
The SharePoint Migration Tool (SPMT) is Microsoft’s free migration utility for moving supported on-premises SharePoint content and file-share content into SharePoint in Microsoft 365, OneDrive, and Teams-connected destinations. It provides scanning, task configuration, incremental reruns, reporting, and identity mapping for controlled migration waves.
What SharePoint Migration Tool (SPMT) Means in SharePoint
SPMT is a Windows-based tool designed for organizations that want a Microsoft-supported path into SharePoint Online. Administrators define a source, select a Microsoft 365 destination, configure migration settings, and run tasks that copy content while preserving supported metadata and permissions. It can be used interactively for smaller batches or through PowerShell and saved task files for repeatable operations.
The tool handles two source families that should not be confused: supported SharePoint Server sites and ordinary network or local file shares. Source type determines what can be scanned, transformed, and preserved. SPMT does not automatically redesign information architecture, clean obsolete content, resolve every unsupported customization, or decide whether a destination should be a site, library, OneDrive account, or Teams-connected workspace.
Why It Matters to the Business
A successful migration is a business change, not merely a copy job. SPMT can reduce tooling cost and support staged delivery, but value comes from deciding what to move, what to archive, who will own the destination, and how users will find and govern information after cutover. Those decisions affect adoption, search quality, security, storage, and long-term support.
For leaders, SPMT reports provide evidence for readiness and wave planning. Scans reveal blocked file types, invalid characters, path issues, large files, version volume, and other conditions that can delay a launch. Teams can use those findings to prioritize remediation, communicate exceptions, and establish measurable acceptance criteria before retiring a legacy environment.
What SharePoint Administrators Need to Know
Administrators should inventory sources, establish destination architecture, validate tenant and endpoint prerequisites, and run scans before scheduling production transfers. Migration accounts need the correct source and destination rights, while identity mapping must reflect current Microsoft Entra users and groups. Pilot waves should test metadata, versions, permissions, timestamps, links, search, and user access—not just file counts.
SPMT supports incremental migration so a team can perform an initial transfer and rerun the task to capture eligible changes before cutover. Incremental behavior is not a substitute for a freeze and reconciliation plan. Administrators still need task logs, exception ownership, delta timing, rollback decisions, and a documented point at which the old source becomes read-only or is decommissioned.
What to Consider
Assess before copying
Run source scans early and classify remediation by business impact. Fixing every warning can waste time, while ignoring material permission, path, version, or customization issues creates user-facing defects.
Design the destination
Map content to sites, libraries, folders, metadata, retention needs, and owners. Reproducing a legacy hierarchy exactly can preserve the problems that motivated the migration.
Validate and close
Reconcile item counts and critical metadata, review failures, obtain owner approval, communicate the cutover, and define how the source will be locked, retained, or retired.
Practical Takeaway
SPMT is a capable Microsoft migration engine, but governance, architecture, testing, and cutover discipline determine whether migrated content becomes a usable Microsoft 365 environment.
How This Shows Up in the Field
Departmental file-share move
An organization scans an operations drive, removes redundant content, maps active folders to governed SharePoint libraries, runs an initial SPMT task, and completes an incremental pass during the cutover window.
SharePoint Server modernization
A migration team inventories supported on-premises sites, remediates unsupported features, maps users, pilots high-risk libraries, and uses SPMT reports to manage exceptions before moving production waves.
SPMT compared with other migration approaches
| SharePoint Migration Tool | Microsoft’s free client utility for supported SharePoint Server and file-share sources, suited to controlled tasks, scans, incremental runs, and PowerShell-assisted repetition. |
|---|---|
| Migration Manager | A SharePoint admin center service that centrally coordinates distributed agents for large file-share migrations; it is not the SharePoint Server migration path. |
Related 6SC Services and Proof
Related SharePoint Glossary Terms
Frequently Asked Questions
Is the SharePoint Migration Tool free?
Yes. Microsoft provides SPMT without a separate tool license for supported migration scenarios. The destination still requires appropriate Microsoft 365 licensing, and organizations must budget for assessment, remediation, architecture, testing, change management, and support.
Can SPMT migrate a file share?
Yes. SPMT can migrate eligible files and folders from local or network file shares to supported Microsoft 365 destinations. Scan results and destination design should be reviewed before copying a large shared drive.
Does SPMT migrate SharePoint customizations?
Not as a blanket lift-and-shift. Content and supported structures can be migrated, but legacy solutions, workflows, forms, add-ins, authentication patterns, and custom code need separate assessment and often require replacement or redevelopment.
Official Microsoft References
- Introducing the SharePoint Migration Tool
- How the SharePoint Migration Tool works
- File share to OneDrive and SharePoint migration guide
Editorial review date: July 13, 2026. Product status and licensing can change; confirm current Microsoft documentation before implementation.
Turn an SPMT transfer into a successful migration
6SC can assess sources, design destinations, remediate risks, execute waves, validate results, and support adoption.
Talk with 6SC