How to Migrate File Shares to SharePoint Online (Step-by-Step)

Migrating Windows file shares to SharePoint Online is the single most common Microsoft 365 project we run. Done right, users get faster search, external sharing, versioning and Copilot access. Done wrong, you inherit twenty years of NTFS chaos. This guide is the exact step-by-step process we use for file-share migrations on MSPowerhouse cloud migration projects.

Before you start — three decisions

• Destination: SharePoint site, Teams channel, or OneDrive? Team content → SharePoint / Teams. Personal / draft → OneDrive. Our OneDrive vs SharePoint guide covers the rule.
• Tool: SPMT for under ~2 TB, Migration Manager for larger. See our tools comparison.
• Permissions strategy: map NTFS to SharePoint groups, or start fresh? For messy legacy shares, fresh is often faster.

Step-by-step: file share → SharePoint Online with SPMT

1. Install SPMT on a jump box. Windows 10 / 11 or Server 2019+, 16 GB RAM, SSD, direct network line-of-sight to the file server. Download from Microsoft's official page.
2. Sign in. Use a Microsoft 365 admin account that is Site Collection Administrator on every target site.
3. Provision the destination. Create the SharePoint sites, Microsoft 365 groups, and target libraries first. Set the metadata schema now — SPMT can populate existing columns during the migration.
4. Add the source. Choose "File Share" and paste the UNC path (\\fileserver01\finance). Add the destination site URL and library.
5. Run scan-only. This is non-negotiable. Scan reports long paths, reserved characters (~ " # % & * : < > ? / \ { | }), unsupported files, and identities that will not resolve.
6. Fix what scan flags. Shorten paths, remove reserved characters, sync missing identities to Entra ID. Doing this now saves you cutover night.
7. Run the bulk copy 2–4 weeks before cutover. Users keep working on the source. Only new and changed files re-copy on subsequent runs.
8. Cutover. Set the source share to read-only, re-run the same SPMT task for the final delta, redirect shortcuts / mapped drives, open the SharePoint site.
9. Validate. Compare source and destination counts from the SPMT report CSV in %LOCALAPPDATA%\Microsoft\MigrationTool\. Investigate any delta.

Permissions: how NTFS maps to SharePoint

SPMT tries to translate NTFS ACLs to SharePoint permissions. Identities that resolve in Microsoft Entra ID land in the right SharePoint group. Identities that do not resolve (local groups, disabled users, old-domain SIDs, "Everyone", broken inheritance) get skipped. Two paths:

• Preserve: clean up identity before migrating. Every ACL identity must exist in Entra ID.
• Start fresh: migrate content with default site permissions and rebuild access using Microsoft 365 groups. Faster, cleaner, and usually the right call for legacy shares.

Either way, do the permission cleanup while owners are already engaged. See our SharePoint permissions best practices for the target model.

Path length and reserved characters

SharePoint Online allows up to 400 characters for the full path — site URL + all folder names + filename. Deep folder trees on legacy file shares blow past this fast. Options:

• Rename overly long folders (usually project subfolders like "01 - Working documents (backup)").
• Break large libraries into multiple sites so the site URL portion is short.
• Let SPMT auto-rename reserved characters, or fix them upstream — decide before you run.

Performance and throughput

Real-world SPMT throughput is 50–100 GB / day / task, dominated by average file size and bandwidth. Microsoft's network planning guide recommends off-hours runs and provides a benchmarking method. To scale, run parallel SPMT tasks against different destination sites, or switch to Migration Manager which is designed for multi-agent parallelism.

After the migration

• Publish a "your files now live here" one-pager and pin it in Teams.
• Keep the source share read-only for 30 days minimum.
• Audit sharing links weekly for the first month.
• Confirm your Microsoft 365 backup is capturing the new sites.
• Formally decommission the file server only after user sign-off.

Migrating a large file share and want a partner who has done it before?
See our data migration service or book a scoping call.