File Server to
SharePoint & OneDrive

Where file server content actually goes

There isn't one destination — file servers typically split across two:

• Shared department and team folders map to SharePoint document libraries, organised by site rather than by drive letter.
• Personal user folders — the classic "H: drive" or individual home directory — map to OneDrive for Business, one per user.

Getting this split right at the planning stage matters more than it sounds — content dumped into the wrong destination tends to get reorganised twice, once during migration and again months later once people notice it's in the wrong place.

What commonly breaks (or needs fixing first)

• File and folder naming. Traditional Windows file servers are permissive about characters and path length in ways SharePoint and OneDrive are not. A pre-migration scan routinely turns up invalid characters, trailing spaces, or folder structures nested deep enough to exceed path-length limits — all of which need remediation before content can move cleanly, not discovered mid-migration.
• NTFS permissions don't translate directly. File server security is built on NTFS permissions; SharePoint and OneDrive use a different sharing and permissions model entirely. There's no automatic one-to-one mapping — permissions need to be deliberately redesigned, which is also a natural opportunity to clean up years of permission sprawl rather than replicate it.
• Sync client behaviour is different from a mapped drive. Users accustomed to a mapped network drive (Z:\Finance\Reports) experience OneDrive/SharePoint sync differently — files sync locally, sharing works through links rather than folder access, and offline behaviour has its own quirks. This is a training and communication point as much as a technical one.
• Version history and duplicate files. File servers accumulate "Report_final_v3_ACTUAL.docx"-style duplication over years. Migration is a natural checkpoint to decide what's worth carrying forward versus archiving separately.

What we look at during discovery

Content and permissions audit. Full inventory of shares, folder structures, and existing NTFS permissions, plus a naming/path-length scan to flag content needing remediation.

Destination mapping. Deciding which content becomes a SharePoint site and library versus OneDrive, based on how teams actually use it — not just how it's currently organised.

Permission redesign. Rebuilding access control in SharePoint/OneDrive's model rather than attempting a literal one-to-one translation of NTFS permissions.

Migration and validation. Content moved in planned batches, with user communication timed around the cutover so the change to sync-based access doesn't land as a surprise.

See our cloud storage migration service for the full picture, or our OneDrive migration service for the personal-storage side specifically.