Primary workflow: Robocopy migration cutover evidence pack
The primary production file-migration workflow: plan, dry-run, pre-seed, freeze writes, final delta, validate data/metadata/access, and make an explicit GO / STOP / ROLLBACK decision before the destination becomes authoritative.
Good For
Windows file server migration
SMB share cutover
Robocopy pre-seed and final delta
change-window decision evidence
permissions and application validation
How to Use It
Define source of truth, destination, scope, exclusions, ACL/ownership requirements, maintenance window, owners, rollback trigger, and maximum acceptable drift before copying.
Run a dry-run/list-only review and record planned Robocopy options; understand every switch rather than starting with an unexplained mirror command.
Perform the initial pre-seed while the source remains authoritative and retain command, timestamps, log, return code, counts, failures, and exclusions.
Interpret Robocopy return codes correctly: codes below 8 can still represent differences requiring review; 8 or higher indicates at least one failure.
Before final sync, review unresolved failures and changed-file behavior; if writes cannot be controlled, the migration is not ready for authoritative cutover.
At the approved cutover point, freeze or prevent new writes to the source and run the final delta synchronization.
Validate file counts and byte totals, review drift/failure sections, and perform targeted hashes for critical or representative files where justified.
Validate share permissions, NTFS ACLs, inheritance, ownership, timestamps, and representative application/user access from the destination.
GO: no unresolved copy failures or unexplained drift; required metadata/permissions are preserved; representative tests pass; rollback remains available.
STOP: unresolved drift, failed files, unexpected exclusions, permission differences, inability to freeze writes, or failed application/user validation. Keep the source authoritative.
ROLLBACK: if post-cutover validation fails or an unknown dependency appears, restore the original namespace/path or access path to the still-authoritative source.
Only after GO should users/applications be redirected and the destination declared authoritative.
Execution Modes
- local
- remote-host-list
Inputs and Outputs
Inputs
- source share/path
- destination share/path
- migration scope and exclusions
- write-freeze plan
- application/user validation cases
- rollback path
- change window
Outputs
- operator-notes
- csv
- log-file
Validation
Pre-seed and final-delta logs are retained with return-code interpretation.
Source/destination counts, bytes, and selected hashes reconcile or each variance is explained.
ACLs, inheritance, ownership, timestamps, share configuration, and representative access are validated.
The change record contains an explicit GO / STOP / ROLLBACK decision.
The source remains authoritative whenever STOP criteria are met.
Reporting
Attach dry-run, pre-seed, final-delta, failure/drift, count/byte/hash, ACL, and representative access evidence to the change.
Record the final GO / STOP / ROLLBACK decision in a short management/change summary.
Keep supporting Robocopy templates as implementation aids; this evidence pack is the production decision workflow.
Safety Notes
Treat a Robocopy /L dry run as read-only planning evidence. The actual copy/cutover phase writes destination data and can change production state; validate source, destination, exclusions, logging, and rollback before execution.
Robocopy can overwrite or delete data depending on switches; review the planned command and dry run before execution.
Do not declare migration success because the copy process ended.
Do not redirect users while unresolved drift or failed validation remains.
Keep the source authoritative and rollback-capable until the destination is proven.