File Server to SharePoint and OneDrive: What to Move, What to Leave, and How Permissions Survive the Trip

A file server that has run for ten years holds three kinds of data: the working set people open every week, the archive nobody opens but the business must keep, and the junk (installers, old backups, exported PST files). A scan before any design work tells you which is which. We report, per share: size and file count, last-modified age, deepest paths, rejected characters, oversized files, and the permission entries on each top-level folder.

A 2 TB server where 1.4 TB has not been touched in three years is a 600 GB migration plus an archive decision. A department share with 40 folders that each carry their own permissions is a site with 40 permission boundaries, not one library.

Cleanup happens before the move, on the server, where the owners still recognize what they are deleting; migrating the junk costs storage, time and goodwill. SharePoint Storage Limits explains how the tenant pool is calculated and what a migrated archive does to it.

The mapping rule: one SharePoint site per permission boundary, one library per working set, and personal data in OneDrive. Not one site per share, and never one library per server.

• Department shares become team sites, one per department, with libraries that mirror the top-level folders people use and owners, members and visitors groups that the NTFS groups map to.
• Project and client shares become libraries in the department's site while they are small, and their own sites when they have their own membership. How Law Firms Should Structure SharePoint for Compliance covers the matter-per-site pattern and ethical walls.
• The company-wide read-only share (policies, templates, forms) becomes a communication site.
• Home drives (H:, U:, Users) go to each person's OneDrive, not to SharePoint. This part maps user-for-user and is priced per seat.

SharePoint's list view threshold is 5,000 items per view; a library can hold far more, but folders with tens of thousands of items at one level are what users report as "SharePoint is slow", so split by year, client or project before you migrate. SharePoint permissions are granted to Microsoft 365 Groups and security groups in Entra ID, not to the NTFS groups on your domain; the groups comparison explains which type to use where.

Microsoft's own tools (the SharePoint Migration Tool and Migration Manager) migrate permissions from a file share, under three rules.

First, the mapping is by role, not by entry. Full Control becomes Full Control, Modify becomes Contribute, Read becomes Read. The finer NTFS rights (list folder only, write without delete, take ownership) collapse into those three. A folder that relied on "write but not delete" gives the user edit in SharePoint; versioning and the recycle bin cover the difference.

Second, Deny entries are not saved. SharePoint has no equivalent, so a subfolder hidden from a group by a Deny becomes visible to that group; either the subfolder moves to a site the group is not in, or the hiding stops.

Third, only unique permissions are migrated; inherited permissions are not carried as entries, because the destination inherits from the site or library in its own way. A folder with broken inheritance on the server becomes a folder with unique permissions in SharePoint, usually what you want, but one more place to audit later.

The precondition is identity. Domain users and groups must exist in Entra ID with matching identities, synchronized by Entra Connect or mapped in a user mapping file, or the tool cannot translate the entry and drops it. Local server groups, orphaned identifiers and deeply nested groups arrive as nothing. Simplify on the server first: three groups per share (edit, read, owners), membership cleaned, nesting flattened.

Path length. The full decoded path, including the file name, is limited to 400 characters in SharePoint and OneDrive. Most server content fits, but the SharePoint URL adds the site and library prefix, and deep trees of long folder names run out fast; we shorten the tree before the copy.

Characters and names. File and folder names cannot contain " * : < > ? / \ or |, and names that start or end with a space fail to sync. Bulk renaming on the server is the fix.

File size. The upload limit is 250 GB per file, plenty for documents and video.

Sync. Microsoft recommends keeping the items synced to a device under about 300,000 across all libraries, and the client slows well before that. A user who syncs the whole Operations share because that is what the mapped drive was will hit it; the answer is Files On-Demand plus syncing only the libraries a person works in.

Known Folder Move belongs in the same plan. The OneDrive policy to silently move Windows known folders redirects Desktop, Documents and Pictures into OneDrive without user action, with companion policies to prompt on failure and to stop users redirecting back. Set through Intune or Group Policy, it replaces the folder redirection that made the home drive share necessary, so the home drive migration and Known Folder Move are one workstream.

Some workloads belong on an SMB share:

• CAD, BIM and GIS projects with external references: the drawings reference each other by path, and the sync client is not what AutoCAD or Revit expect.
• Databases and anything with a lock file: Access databases, QuickBooks company files, SQL backups, application data folders. SharePoint is a document store, not a file system.
• Applications that write to a UNC path: scanners, label printers, ERP export jobs, backup targets.

Azure Files is the halfway house: an SMB share in Azure, joined to your identity, with the permissions model your applications expect and no server to patch. Azure Files Done Right covers the tiers and the decisions that set the monthly bill. Our File Server Migration to Azure Files and SharePoint splits one server both ways: documents to SharePoint, application data to Azure Files, and the server retired. Windows Server 2016 End of Support covers the rest of the server.

A file server migration is a copy, a delta and a switch, and the switch is the only part users notice.

1. Pilot one department share to its new site.
2. Seed the full copy while the server stays live; Microsoft's tools copy in the background.
3. Run delta passes until the change volume is small.
4. Freeze: set the source shares read-only on a Friday evening, run the final delta, verify counts and a sample of permissions.
5. Switch: remove mapped drives through Intune or Group Policy, publish the site links, turn on Known Folder Move, sync the libraries each department needs.
6. Keep the server read-only for 30 to 90 days, then retire it.

Our SharePoint Online Migration from File Share As-Is runs that pattern for one server in one week at $4,500 per server, structure copied as it stands, restructuring scoped from the inventory. Home drives run through OneDrive for Business Personal Document Migration from File Server at $50 per seat plus a $300 tenant fee, three days. The migration estimator turns a share inventory into a budget.

SharePoint and OneDrive are included in the plans most customers already hold. Microsoft list price, September 2026 price list, annual commitment: Microsoft 365 Business Basic $84.00 per user per year ($7.00 per month), Business Standard $168.00 ($14.00 per month), Business Premium $264.00 ($22.00 per month). The SharePoint storage that comes with them is pooled across the tenant, and a large migration can exhaust it; the storage article explains when the Office 365 Extra File Storage add-on is the answer rather than more cleanup. We sell all of it at Microsoft's list price.

Can I migrate a file server to SharePoint with permissions intact?

Mostly. Full Control, Modify and Read map to SharePoint roles; Deny entries are dropped, inherited entries are recreated by SharePoint's own inheritance, and any user or group missing from Entra ID is skipped.

Should we migrate the file server to SharePoint or to OneDrive?

Both, by data type. Shared department and project data goes to SharePoint sites; each person's home drive goes to their OneDrive.

What is the maximum file path length in SharePoint Online?

400 characters for the full decoded path including the file name.

How long does a file server to SharePoint migration take?

One server, as-is structure, is a one-week engagement including pilot, seed, delta and switch.

Can users keep their mapped drives after moving to SharePoint?

Not in the same way. The pattern that holds up is the OneDrive sync client with Files On-Demand for the libraries a person uses, plus the browser and Teams.

• Microsoft Support, "Restrictions and limitations in OneDrive and SharePoint": invalid characters, 400-character decoded path, 250 GB file size, about 300,000 synced items; Microsoft Learn, "Understanding permissions when migrating": role mapping, Deny not saved, unique permissions migrated, inherited not migrated; Microsoft Learn, "Redirect and move Windows known folders to OneDrive": silent move, prompt and prevent-redirect policies; Microsoft Support, list view threshold of 5,000 items per view. Not opened from this environment; as reported by clonepartner.com, mspowerhouse.com and search excerpts on 27 September 2026; verify on Microsoft Learn and Microsoft Support.
• IT Partner blog articles linked above: Windows Server 2016 end of support (12 January 2027), SharePoint storage limits, law firm SharePoint structure, Azure Files architecture, the groups comparison
• IT Partner price sheet, Commercial segment, September 2026 US price list; IT Partner service pages and engineering notes, September 2026