Migration software
Storage Migration Service
Suggested in one of our migration playbooks, mainly for End of support. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What does Storage Migration Service handle?
The limits of the built-in tools that Storage Migration Service gets around, as covered in our playbooks.
Windows Server 2016 end of support (12 Jan 2027)
- Clustered servers cannot jump versionsSupports failover cluster sources (including 2016) and destinations, with the orchestrator on Windows Server 2019 with KB5001384 or Windows Server 2022. Only the file server cluster resources move, not the cluster itself, and Azure Local clusters are not supported as a destination.
- Desktop Experience and Server Core do not convertInventories the source, transfers files, file shares and security configuration, and can cut over the server identity. Covers file serving only, so other roles on the server need their own migration.
- An in-place upgrade cannot switch between Server Core and Desktop Experience, or change language.Moves shares, data and security settings to a new server and can take over the old name and IP. File serving only.
- Clustered servers must upgrade one version at a time with a cluster OS rolling upgrade.Moves file server cluster resources from a 2016 cluster straight to a new cluster. The cluster itself does not move.
How does Storage Migration Service handle key settings?
From the settings checklists in our playbooks: what Storage Migration Service carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| In-place upgrade rules | For file servers that must change installation type, moves shares, data and security settings to a new server and can take over the old name and IP. | Windows Server 2016 end of support (12 Jan 2027) |
| Clusters | Moves file server cluster resources from a 2016 cluster straight to a new cluster. The cluster itself does not move. | Windows Server 2016 end of support (12 Jan 2027) |
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.