UK’s trusted IT infrastructure partner since 2003
sales@servnetuk.com
0800 987 4111
Servnet
ConfiguratorGet in Touch
Collaboration migration
From
On-Premises File Shares (DFS / Windows)
→
To
OneDrive + SharePoint Online

On-prem file shares to OneDrive + SharePoint migration — UK enterprise programme

Legacy on-prem file servers and DFS namespaces consume hardware, storage, backup, replication and operational time — and they make remote / hybrid work harder. Most UK organisations on M365 now have the licences and tools to move all user + departmental file shares to OneDrive and SharePoint with full security, retention and Defender for Cloud Apps coverage. Servnet runs end-to-end file-share migrations with permissions preservation.

Vendor migration programme — On-Premises File Shares (DFS / Windows) source on the left, OneDrive + SharePoint Online target on the right, with parallel-running data streams converging through a central Servnet cutover hub.
From → To: On-Premises File Shares (DFS / Windows) vs OneDrive + SharePoint Online
CURRENTOn-Premises File Shares (DFS / Windows)Production workloadsLegacy management planeRenewal due / EoSServnetparallel-running migrationTARGETOneDrive + SharePoint OnlineProduction workloadsModern management planeStrategic 5-yr position
Typical outcomes

What good looks like after a On-Premises File Shares (DFS / Windows) → OneDrive + SharePoint Online migration

On-prem file server infra
−100%

Servers + storage + backup + DR all decommissioned post-migration.

Migration window
10-20 wk

End-to-end for a 5-50 TB shared-drive estate.

VPN dependency for file access
Removed

Users access files directly from any device, anywhere, with Conditional Access enforcement.

Permissions preserved
100%

NTFS / share-level ACLs translated to SharePoint permissions + Microsoft 365 groups.

The why

Why UK organisations migrate from On-Premises File Shares (DFS / Windows) to OneDrive + SharePoint Online

  • ✓Eliminate on-prem file server infrastructure (hardware, storage, backup, DR)
  • ✓Enable secure remote / hybrid working without VPN dependency
  • ✓Native Office co-authoring + Loop + Copilot integration
  • ✓Microsoft Purview Sensitivity Labels + retention + e-discovery
  • ✓Defender for Cloud Apps + Conditional Access for file-level data protection
  • ✓Reduce IT operational time on patching, capacity, backup of legacy file servers
How we run it

Migration phasing — typical On-Premises File Shares (DFS / Windows) → OneDrive + SharePoint Online programme

On-Premises File Shares (DFS / Windows) → OneDrive + SharePoint Online — programme timeline
W0W3W6W9W12W15W18W20Discovery + SharePoint architecture3wSharePoint + OneDrive provisioning3wPilot wave (1-2 small file shares)3wPhased migration9wFile server decommission2wTotal programme: 20 weeks · parallel running throughout
  1. 1

    Discovery + SharePoint architecture

    Weeks 1-3

    File-server estate fingerprint (size, file count, age, access patterns); DFS namespace mapping; SharePoint architecture design (hub sites, team sites, document libraries); migration tool selection (ShareGate, Quest, AvePoint, Mover).

  2. 2

    SharePoint + OneDrive provisioning

    Weeks 4-6

    SharePoint hub + team site templates; OneDrive sync client deployment via Intune; Sensitivity Labels + retention; Defender for Cloud Apps connector.

  3. 3

    Pilot wave (1-2 small file shares)

    Weeks 7-9

    Pilot shares migrated to SharePoint sites; permissions validated; user training delivered; runbook refined; user feedback gathered.

  4. 4

    Phased migration

    Weeks 10-18

    Share waves grouped by department / criticality; user training delivered per wave; legacy share access removed after each wave completes successfully.

  5. 5

    File server decommission

    Weeks 19-20

    Final shares migrated; on-prem file servers + DFS namespaces decommissioned; backup tier reclaimed.

Included in scope

What Servnet delivers in a On-Premises File Shares (DFS / Windows) → OneDrive + SharePoint Online migration

SharePoint + OneDrive architecture

Hub sites, team sites, communication sites + OneDrive personal storage — sized to your file-share patterns.

Migration tool licensing

ShareGate, Quest On Demand, AvePoint Fly or Microsoft Mover — licensed for the migration window.

Permissions translation

NTFS + share-level ACLs translated to SharePoint permissions; Microsoft 365 groups for ongoing manageability.

OneDrive sync deployment

Sync client deployed via Intune; Known Folder Move (Desktop, Documents, Pictures) optional per user; Files On-Demand for low-disk endpoints.

Sensitivity Labels + DLP

Auto-classification on migration; ongoing DLP policies enforced via Defender for Cloud Apps.

User training + change management

OneDrive + SharePoint training per wave; mobile + web experience walkthrough.

De-risking the cutover

Top risks + how we mitigate them

⚠️ Very large legacy file shares (10TB+) take significant time to migrate
Migration tools support multi-threaded uploads; we run delta migrations in waves to keep cutover windows small. Final cutover delta typically syncs in hours, not days.
⚠️ Complex NTFS permission inheritance breaks SharePoint translation
Permissions analysed during discovery; SharePoint architecture designed around Microsoft 365 groups rather than per-file ACLs; edge cases get manual remediation before user wave migration.
⚠️ Line-of-business apps hard-coded to UNC paths
App inventory + integration mapping during discovery. Options: (a) re-point app to OneDrive sync local folder, (b) keep specific UNC paths on a slim residual file server, (c) modernise the app integration to Graph API.
⚠️ Users resist losing the "open mapped drive" UX
OneDrive sync gives a Windows Explorer experience similar to a mapped drive; Known Folder Move preserves Desktop / Documents / Pictures paths transparently; helpdesk scripts ready.
Pricing guide rail

Indicative: file-share → OneDrive / SharePoint migrations for a 5-50 TB estate typically run £25k-£80k professional services (excluding M365 licensing + migration tool licences). Total programme is a net saving from year 2 (on-prem infrastructure + backup costs eliminated). Talk to us for a sized commercial proposal.

Frequently asked

FAQs — On-Premises File Shares (DFS / Windows) → OneDrive + SharePoint Online

Should we use OneDrive or SharePoint for departmental shares?

OneDrive = personal user files (My Documents, Desktop, Pictures). SharePoint = shared / departmental / project files. Both are part of the same M365 platform — we design the architecture during discovery.

What about line-of-business apps using UNC paths?

Inventoried during discovery. Options: re-point the app to a OneDrive sync local folder, keep a slim residual file server for specific UNC paths, or modernise the app to Graph API. We document the trade-off per app.

How does this compare to Azure Files / Azure Files Premium?

Azure Files retains the SMB / mapped-drive UX but moves the storage to Azure. Useful as a transitional option or for apps that genuinely need SMB. Most user-facing file shares migrate cleaner to OneDrive / SharePoint with the native collaboration features.

Can we keep some file servers on-prem?

Yes — many migrations keep a slim residual file server for specific use cases (very large files, legacy apps, regulatory requirement). Scoped honestly during discovery.

Go deeper

Ready to scope your On-Premises File Shares (DFS / Windows) → OneDrive + SharePoint Online migration?

30-minute discovery call with an engineer who's run this migration before. Honest scoping, no sales script.

Book a scoping call →