Decide by workload, not drive letter
Replacing a file server with SharePoint makes sense for team documents, but not automatically for every workload. Fictional North Workshop separates Office procedures, application files and archives. Each batch gets a destination, owner and acceptance criteria. This assessment prepares a decision; it does not replace an environment audit.
Good candidates: collaboration and document access
Team Office documents, procedures and project records can benefit from shared libraries, search and coauthoring where the format and client support it. Team files belong in a SharePoint site rather than an employee’s personal OneDrive. Teams provides a collaboration interface; channel files reside in SharePoint. Define owners, sharing rules and member offboarding.
When to retain file services
An application requiring UNC paths, SMB locks or very low latency needs vendor validation before moving. A live database, VM disks, backup repository or application continuously rewriting files does not become compatible because its extension can be uploaded. CAD projects and references need specific tests. Retain file services or evaluate a suitable SMB service such as Azure Files when filesystem semantics remain necessary. A OneDrive shortcut or WebDAV drive does not guarantee SMB equivalence.
Inventory without scanning everything at once
Record shares, owners, sizes, file types, available usage evidence and application dependencies. File age does not prove it is unnecessary. On Windows Server, a delegated administrator can read shares using SmbShare; a scoped folder inventory only needs read access to that scope. Recursive enumeration can load storage: begin with a small batch outside peak hours. Paths and ACLs are sensitive; protect collected results. The following commands do not modify data.
# Lecture sur le serveur Windows / Read on the Windows server
Get-SmbShare | Select-Object Name,Path,Description
Get-SmbShareAccess -Name 'Projets'
# Petit périmètre fictif / Small fictional scope
Get-ChildItem -LiteralPath 'D:\Partages\Projets\Pilote' -File -Recurse -ErrorAction Continue |
Select-Object FullName,Length,LastWriteTime
Get-Acl -LiteralPath 'D:\Partages\Projets\Pilote' |
Select-Object Owner,AccessToStringCheck service and client limits
Current limits allow 250 GB files and a complete decoded path of at most 400 characters. These are ceilings, not design targets. Include the target site and library path in calculations. A library’s supported item count is not the sensible number to sync on each endpoint: Microsoft recommends staying below 300,000 files for optimal performance and warns about cumulative effects across libraries. Files On-Demand reduces local storage without removing every sync constraint. Test names, shortcuts and actual Office clients; plan offline availability and version conflicts.
Design permissions before copying
Design sites and libraries around teams, confidentiality and ownership, using groups rather than excessive per-file exceptions. NTFS ACLs are not a SharePoint sharing model. SPMT does not preserve every explicit deny or advanced permission. With Migration Manager, inspect settings: file permissions are not migrated by default in the same way as folder permissions, and incremental jobs do not necessarily reapply every unchanged permission. Map identities, resolve unmatched accounts and test both allowed and denied access. Do not enable broad external sharing to fix identity problems.
Prerequisites, licensing and migration tool
Validate users’ SharePoint subscriptions, tenant capacity and additional Purview, protection or backup needs. Personal OneDrive storage is not the same as available SharePoint capacity. Use a supported SPMT release or current Migration Manager agent; check Windows requirements, allowed endpoints and workspace before installation. Migration Manager requires SMB 2.0 or later at the source, a Windows account with source read access and an appropriate SharePoint/OneDrive destination role. Prefer that role over Global Administrator. Agent installation and library creation are changes, separate from inventory.
Assess, then pilot the document migration
Run the selected tool’s scan-only mode first and review errors, exclusions and destination mappings. Scanning can create reports and load source storage; it is separate from copying. Include Office documents, a long path, restricted access, document links and offline files in the pilot. Measure transferred volumes and address every skipped item. A successful copy does not automatically rewrite embedded UNC links. Have users test opening, editing, search after indexing, supported coauthoring and synchronization.
Cutover and rollback: one authoritative copy
Document configuration, back up the source and test restoration before cutover. After the initial copy and pilot corrections, agree on a window to make the source read-only, run the final increment and reconcile reports. Declare the target authoritative only after business acceptance. Update links, procedures and shortcuts. If stop criteria are met, pause target changes, preserve new writes and decide how to reconcile them before reopening the source. Blind reverse copying can overwrite work. Retain the old share for an approved period with limited access, then retire it under retention requirements.
Decide with measurable deliverables
Deliver a batch-level matrix: chosen destination, rationale, owner, approved access, exclusions, cost, acceptance and recovery. At North Workshop, procedures move to SharePoint while the SMB-dependent application retains suitable storage. Provide training and post-cutover support. Version history, recycle bins and synchronization do not replace independent backup with tested restoration. Infrastructure and Microsoft 365 audit services can help validate the choice and prepare a pilot without imposing a global migration.