What Is Migration Manager in SharePoint?
Migration Manager is Microsoft’s centralized service in the SharePoint admin center for scanning and migrating file shares to SharePoint, OneDrive, and Teams-connected locations. Administrators deploy lightweight agents near source data, create migration tasks, monitor progress, and coordinate large or distributed file-share migration programs from one interface.
What Migration Manager Means in SharePoint
Migration Manager separates orchestration from data transfer. The admin center stores task configuration, status, and reports, while installed migration agents perform source discovery and transfer work. Multiple agents can be grouped and positioned close to file servers, allowing an organization to distribute workloads across locations without managing every migration from a single desktop.
Its intended source is a file share, not an on-premises SharePoint Server farm. That boundary is important: a business may use Migration Manager for departmental drives and SPMT for supported SharePoint Server content within the same modernization program. Neither service decides the target architecture or automatically cleans poor permissions, redundant files, abandoned folders, and unclear ownership.
Why It Matters to the Business
Central coordination helps program leaders understand progress across sites, regions, and migration waves. Scans and reports expose source volume, risk, task state, and failures in a consistent place. That visibility supports realistic cutover sequencing and makes it easier to assign remediation to the business teams that understand the content.
The business outcome should be measured in usable, governed destinations rather than terabytes moved. Each task needs an owner, target purpose, acceptance criteria, adoption plan, and legacy-source disposition. Migration Manager can accelerate execution, but moving every folder without those decisions can create an expensive cloud replica of an unmanaged shared drive.
What SharePoint Administrators Need to Know
Administrators install agents on qualified Windows computers with network access to the source and outbound access to Microsoft 365. Agent service credentials require appropriate file-share access, and migration administrators need the necessary tenant roles. Agent groups, capacity, source proximity, maintenance windows, network throughput, and endpoint security controls should be planned before bulk tasks begin.
A sound operating cycle is scan, analyze, remediate, map, migrate, validate, and rerun eligible changes. Administrators should monitor task and agent health, retain reports, investigate skipped or failed items, and reconcile results with source inventories. Identity mapping and destination permissions deserve explicit testing because a successful transfer does not guarantee that the right people can safely find and use the content.
What to Consider
Use it for the right source
Migration Manager is designed for file shares. Use Microsoft’s supported SharePoint Server migration path, such as SPMT, when the source is an on-premises SharePoint environment.
Engineer the agent layer
Place enough healthy agents near source data, secure their service accounts, monitor updates and connectivity, and account for network constraints that can dominate migration duration.
Govern the destination
Create target sites, libraries, owners, access models, metadata, retention, and support standards before tasks run. Destination readiness should be a wave entry criterion.
Practical Takeaway
Migration Manager provides scalable, centralized control for file-share migrations, while a complete program still needs content decisions, destination governance, agent engineering, validation, and adoption.
How This Shows Up in the Field
Distributed office file servers
A company installs agent groups in several regions, scans each local drive, and coordinates migration waves from the SharePoint admin center while regional owners validate their new libraries.
Department-by-department modernization
IT creates separate tasks for finance, operations, and human resources, using findings to remediate sensitive access and map each department to an appropriately governed destination.
Migration Manager compared with SPMT
| Migration Manager | Cloud-based orchestration in the SharePoint admin center, using distributed agents to scan and move file-share sources at program scale. |
|---|---|
| SharePoint Migration Tool | A Microsoft client tool that supports both eligible file-share tasks and supported SharePoint Server-to-Microsoft 365 migrations. |
Related 6SC Services and Proof
Related SharePoint Glossary Terms
Frequently Asked Questions
Is Migration Manager the same as SPMT?
No. Both are Microsoft migration technologies, but Migration Manager centrally coordinates agents for file-share sources. SPMT is a client utility that can migrate supported SharePoint Server content as well as eligible file-share content.
Where is Migration Manager administered?
Migration Manager is administered from the migration area of the SharePoint admin center. Authorized administrators use it to add agents, configure sources and tasks, initiate scans or transfers, and review status and reports.
Why does Migration Manager need agents?
Agents provide the execution path between source file shares and Microsoft 365. They run near the data, access source files through configured credentials, receive tasks from the service, and perform scan and migration operations.
Official Microsoft References
Editorial review date: July 13, 2026. Product status and licensing can change; confirm current Microsoft documentation before implementation.
Plan a controlled file-share migration
6SC can turn Migration Manager scans and tasks into an accountable program with destination design, remediation, security review, wave execution, validation, and adoption.
Talk with 6SC