To migrate a file server to SharePoint Online, you assess what is on the shares, clean up redundant and obsolete data, design a SharePoint and Teams structure that replaces the old folder tree, map permissions to Microsoft 365 groups, migrate content with Microsoft’s Migration Manager or the SharePoint Migration Tool in a pilot followed by bulk waves, and cut over with a final incremental sync before making the old shares read-only. Done properly, a mid-sized file server moves with no lost files and very little disruption.
The technical copy is the easy part. Most failed migrations go wrong on structure and permissions — lifting a 20-year-old S: drive into a single document library recreates every old problem in the cloud.
Step 1: Assess what you have
Run an inventory of every share: total size, file count, file types, last-modified dates, deepest folder paths and permission entries. Microsoft’s Migration Manager includes a scan that flags issues before you copy anything. Look out for:
- Long paths — SharePoint has a limit on the full decoded URL length (currently 400 characters), and deep folder trees on file servers often exceed it once the site URL is added.
- Invalid characters and blocked names — certain characters and reserved names are not allowed in SharePoint and must be renamed.
- Very large files — SharePoint supports large files, but CAD, video and database files may belong elsewhere.
- Stale data — content untouched for years is a candidate for archive rather than migration.
- Broken permissions — orphaned accounts and unique permissions on individual files.
Step 2: Clean up before you move
Delete duplicates, archive inactive content and fix naming problems at the source. Every gigabyte you do not move shortens the migration and reduces clutter in search. As a rule of thumb, data unchanged in five or more years should be reviewed with its owner rather than migrated automatically.
Step 3: Design the target structure
A file server is a hierarchy of folders. SharePoint works best as a flat set of sites, each with its own owners and permissions. Map departments and projects to sites or Teams, and keep folder depth shallow.
| On the file server | In Microsoft 365 |
|---|---|
| Department share (\\fs01\Finance) | SharePoint team site or Team: Finance |
| Project folders | One Team or site per active project; archive closed ones |
| Personal home drives (H:) | OneDrive for each user |
| Company-wide policies and templates | Communication site or intranet library |
| Deep subfolders | Libraries with metadata columns instead of nested folders |
Step 4: Map permissions to groups
Replace NTFS permissions with Microsoft 365 groups and SharePoint site roles (owners, members, visitors). Avoid unique permissions on individual folders wherever possible — they are hard to audit and slow everything down. Make sure on-premises accounts are synchronised to Entra ID first so permissions map to the right identities; see our Entra ID migration service if your directory is not yet ready.
Step 5: Choose the migration tool
| Tool | Best for | Notes |
|---|---|---|
| Migration Manager | Most file share migrations | Managed from the SharePoint admin centre, agent-based, scales across multiple servers |
| SharePoint Migration Tool (SPMT) | Smaller, one-off migrations | Desktop tool, simple to run, good for pilots |
| Third-party tools | Complex or tenant-wide projects | Useful for advanced permission mapping and reporting |
Step 6: Pilot, then migrate in waves
- Migrate one department as a pilot and have users validate files, permissions and sync.
- Fix what the pilot reveals — path issues, permissions, training gaps.
- Run bulk migration in waves outside business hours, starting with the largest and least-active data.
- Run incremental passes to pick up changes made since the first copy.
Throughput depends on file count more than total size, as well as on bandwidth and throttling. Our guide on how long a Microsoft 365 migration takes covers realistic timelines.
Step 7: Cut over and decommission
- Announce the cut-over date and set the source shares to read-only.
- Run a final incremental migration.
- Remap drive shortcuts to SharePoint or Teams, and enable OneDrive Known Folder Move for desktops and documents.
- Keep the old server read-only for an agreed period, then archive and decommission it.
Common pitfalls
- Syncing very large libraries to every laptop with OneDrive — sync the libraries people use, not everything.
- Migrating macros and linked spreadsheets without checking UNC path references.
- Skipping user training — people need to learn how to share, co-author and find files.
- Ignoring governance; set rules for site creation and external sharing first. Our Teams governance starter guide is a good starting point.
Plan your file server migration
M365 Enterprise Hub runs file server to SharePoint migrations for organisations across the UAE and the US, alongside SharePoint and OneDrive migrations from other platforms and full cloud migration programmes. For common traps, read common Microsoft 365 migration challenges, or contact us for a migration assessment.
Frequently Asked Questions
Can I move my file server directly to SharePoint?
Yes. Microsoft’s Migration Manager and the SharePoint Migration Tool copy file shares into SharePoint Online and OneDrive. For best results, clean up the data and design a site structure first rather than copying the folder tree as it is.
What is the best tool to migrate file shares to SharePoint?
For most organisations, Migration Manager in the SharePoint admin centre is the best choice because it is free, agent-based and scales across servers. SPMT suits smaller migrations, and third-party tools help with complex permission mapping.
Do NTFS permissions migrate to SharePoint?
Migration tools can carry permissions across when accounts are synchronised to Entra ID, but it is usually better to redesign access around Microsoft 365 groups and site roles than to replicate complex folder-level permissions.
Should home drives go to SharePoint or OneDrive?
Personal home drives should go to each user’s OneDrive. Shared departmental and project content belongs in SharePoint sites or Teams.
How long does a file server to SharePoint migration take?
It depends on file count, data volume, bandwidth and clean-up effort. A small file server can move in days; multi-terabyte environments with complex permissions typically take several weeks including planning, pilot and waves.
What happens to the old file server after migration?
After a final incremental sync, the source shares are set to read-only for an agreed period so users can verify content, then archived and decommissioned.