How to migrate a file server to SharePoint and keep permissions
Updated October 2026 · 8 min read
Why permissions break during migration
- NTFS ≠ SharePoint. NTFS has granular rights and inheritance; SharePoint has permission levels (Read, Edit, Full Control) applied to groups. A migration must translate between the two — a straight copy can't.
- Broken inheritance. Years of "just give them access" exceptions leave folders with explicit ACLs that don't match their parents.
- Orphaned SIDs. Deleted users and groups leave security identifiers that can't be mapped to anyone.
- Deny rules & advanced ACLs. Microsoft's own guide to file‑share migration says that all advanced NTFS permissions are removed after migration, and that content under an explicit Deny may become accessible.
What “keeping permissions” really means
There are two honest goals, and it's worth deciding which you want before you start:
- Replication — reproduce who had access to what, as closely as SharePoint's permission levels allow. Best when access is already well‑governed.
- Clean‑slate model — use the migration to tidy a decade of sprawl into a sensible structure. Often the better long‑term choice.
The wrong approach is an accidental third option: everything flattened to a few broad roles and whatever can't be translated dropped, so you neither replicated nor cleaned up — you just lost fidelity.
The right order
- 1. Survey — read every ACL; flag broken inheritance, orphaned SIDs and Deny rules, and report the permission complexity.
- 2. Remediate — take ownership, repair inheritance, remap or safely drop orphaned SIDs (with an audit trail), and resolve conflicting entries.
- 3. Map — translate the cleaned NTFS groups to SharePoint permission levels, or apply your chosen clean‑slate model.
- 4. Migrate & verify — apply the mapped permissions on upload, then verify that effective access matches what you intended.
Where Approdo fits
The Deckhand, Approdo's agent, does steps 1–2 on your server automatically: it audits the ACLs, takes ownership where needed, repairs inheritance, and handles orphaned SIDs — detecting them, remapping where it can, and safely dropping the rest with a logged record. You see the plan and the diff before anything is applied, and every change is logged. What can be carried into SharePoint in steps 3–4 is being listed, not yet proven.
NTFS → SharePoint mapping, briefly
Microsoft's file‑share migration guide gives this mapping from Windows file share permissions to SharePoint roles: Full control → Full control; Modify and Write → Contribute; Read and execute → Read. It is not a one‑to‑one match: per‑user ACLs and Deny rules need decisions — which Approdo is being built to surface.
Replicate or start clean?
For many firms, migration is the best moment they'll ever get to fix permissions, not just carry the mess across.
Approdo is coming soon
Approdo's assessment reads your NTFS permissions and flags every orphaned SID and broken inheritance before you migrate.
Register your interest →FAQ
How do I keep permissions when migrating to SharePoint?
Remediate the NTFS ACLs first (ownership, inheritance, orphaned SIDs), then map the cleaned groups to SharePoint permission levels. Approdo is being built to automate the remediation. What can be carried into SharePoint is being listed, not yet proven.
Do SharePoint permissions work like NTFS?
No — SharePoint uses permission levels on groups, not granular NTFS rights, so a mapping is always required.
What happens to deleted users / orphaned SIDs?
The account behind each one is gone, so it has to be remapped to someone else or dropped. Approdo will detect them, remap where possible, and safely drop the rest with an audit trail.