Approdo is in build and not yet available. Register your interest →
Approdo › Guides › Keep permissions

How to migrate a file server to SharePoint and keep permissions

Updated October 2026 · 8 min read

Short answer: fix the permissions before you move. Survey the NTFS ACLs, repair broken inheritance and ownership, clean orphaned SIDs, then map the cleaned groups to SharePoint permission levels during migration. Approdo is in build. What it will carry from your file server is being listed item by item, with what cannot be carried and why. Nothing on that list has yet been proven on a test.

Why permissions break during migration

What “keeping permissions” really means

There are two honest goals, and it's worth deciding which you want before you start:

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

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.