A file migration is successful only when users, paths, and permissions behave exactly as before.

Storage Migration Service projects should begin with a precise inventory of shares, local groups, paths, scheduled tasks, backup jobs, DFS references, antivirus exclusions, and every client path assumption tied to the old server identity.

Runbook note: Treat identity cutover as the critical milestone. Copying data is the easy part; preserving host identity, ACL behavior, and application dependencies is where migrations succeed or fail.

• Inventory share names, NTFS ACL inheritance breaks, local security principals, printers, scheduled jobs, and services that still reference the old hostname.
• Document line-of-business applications, scripts, mapped drives, and DFS namespaces that target the source server directly.
• Capture backup, restore, and shadow-copy behavior on the old server before any migration job begins.
• Define rollback as restoring client access to the original identity quickly if cutover validation fails.

Command path:

• Get-SmbShare
• icacls D:\\Data /save acl-baseline.txt /t
• Get-LocalGroup
• Get-ScheduledTask | Select TaskName,State

GUI path: Windows Admin Center > Storage Migration Service inventory workflow, Computer Management > Shared Folders, and File Explorer security views.

Use the service to discover differences before copying at scale.

The Storage Migration Service inventory phase surfaces share definitions, identities, and transfer issues early. Resolve mismatches there instead of discovering them during production cutover.

• Run inventory against the source server and review shares, users, groups, and excluded paths carefully.
• Stage the destination server with matching storage layout, performance expectations, and management tooling before transfer.
• Tune transfer windows around active workloads so open-file contention and backup overlaps do not pollute the migration signal.
• Review transfer logs for failed paths, long-path issues, unsupported data, and denied ACLs before declaring readiness.

Command path:

• Get-SmsTransferProgress
• Get-WinEvent -LogName "Microsoft-Windows-StorageMigrationService/Admin" -MaxEvents 50

GUI path: Windows Admin Center > Storage Migration Service > Inventory, Transfer, and Cut over steps.

Do not let successful copy statistics hide permission drift.

Before identity cutover, validate that copied data is usable by the same people and services that relied on the source server, including inherited and explicitly denied paths.

• Compare share counts, total data footprint, and representative ACLs between source and destination.
• Test application service accounts, user access paths, and backup software against the destination server before identity cutover.
• Verify DFS targets, shadow-copy expectations, antivirus exclusions, and monitoring agents on the destination host.
• Reconcile any skipped files or denied paths explicitly instead of accepting summary success metrics.

Command path:

• robocopy \\\\OLD-FS01\\D$ \\\\NEW-FS25\\D$ /MIR /COPY:DATSOU /R:1 /W:1 /L /NFL /NDL
• icacls D:\\Data /verify /t
• Get-SmbShareAccess -Name Data

GUI path: Windows Admin Center transfer reports, File Explorer > Security, and backup or monitoring consoles on the destination server.

Make the new host look old only when the new path is already trusted.

During cutover, the destination inherits server identity or client targeting changes are applied. Keep that window narrow and validate name resolution, SMB sessions, permissions, and backup visibility immediately.

• Quiesce active application writes and user sessions before identity cutover to avoid partial or divergent change states.
• Perform the host-identity switch or namespace-target update during a defined window with rollback criteria already agreed.
• Test mapped drives, UNC paths, service dependencies, and backup jobs immediately after the cutover.
• Keep the source server isolated but recoverable until several clean production cycles have completed on the new server.

Command path:

• Get-SmbSession
• Test-Path \\\\OLD-FS01\\Data
• Resolve-DnsName OLD-FS01
• Get-WinEvent -LogName System -MaxEvents 50

GUI path: Windows Admin Center > Storage Migration Service > Cut over and DNS or DFS management tools used to validate identity change.