How to migrate from Windows SMB shares to Nextcloud without breaking permissions and user habits
Treat a move from mapped drives to Nextcloud as an identity, permission, client, path, versioning, backup and phased-cutover project—not just a file copy.

Establish a factual baseline with “AD/LDAP identities” and “directory and permission mapping”, then move to “desktop-client and browser access methods”. Use effective access, credentials and real file operations as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking AD/LDAP identities, directory and permission mapping and desktop-client and browser access methods independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · AD/LDAP identities | Checking AD/LDAP identities helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of AD/LDAP identities. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 02 · directory and permission mapping | Checking directory and permission mapping helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of directory and permission mapping. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 03 · desktop-client and browser access methods | Checking desktop-client and browser access methods helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of desktop-client and browser access methods. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 04 · legacy-path compatibility | Checking legacy-path compatibility helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of legacy-path compatibility. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 05 · versioning, file locks and large files | Checking versioning, file locks and large files helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of versioning, file locks and large files. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 06 · phased migration and rollback | Checking phased migration and rollback helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of phased migration and rollback. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
Investigation and change sequence
- Capture a baseline for AD/LDAP identities and directory and permission mapping and compare it with a known-good system.
- Correlate evidence from desktop-client and browser access methods and legacy-path compatibility to distinguish the direct fault from dependent symptoms.
- Only if evidence points to versioning, file locks and large files, plan a controlled change with backups, a change window and rollback triggers.
- Finally check phased migration and rollback and the real business workflow. Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
Validation and rollback evidence
- Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
- Recheck versioning, file locks and large files and phased migration and rollback against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming AD/LDAP identities is sufficient while overlooking directory and permission mapping and dependent checks.
- Changing several settings before preserving the original evidence for desktop-client and browser access methods.
- A healthy RAID, snapshot or successful backup job is not proof of a recoverable workload.
Common questions and acceptance criteria
What should be checked first?
Begin with AD/LDAP identities and directory and permission mapping. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
Need to assess your actual environment?
Share the current topology, device and software versions, symptoms, impact, maintenance window and available configuration or backup evidence. We will assess risk, dependencies and rollback before defining scope.
