| User State Migration Tool (USMT) | |
| Developer: | Microsoft |
| Latest Release Version: | 5.0 |
| Operating System: | Microsoft Windows |
| Genre: | Command |
| License: | Proprietary commercial software |
The User State Migration Tool (USMT) is a command line utility program developed by Microsoft that allows users comfortable with scripting languages to transfer files and settings between Windows PCs. This task is also performed by Windows Easy Transfer, which was designed for general users but then discontinued with the release of Windows 10,[1] where they instead partnered with Laplink.[2] Starting with Windows 8, many settings and data are now being synchronized in cloud services via a Microsoft Account and OneDrive. USMT allows a high-volume, automated deployment of files and settings,[3] and is also useful in migrating user settings and files during OS upgrades. Because USMT has high complexity and a command line interface, there have been several attempts to provide access to its useful functionality by creating GUI wrappers for it. 32-bit to 64-bit migrations are supported, but 64-bit to 32-bit are not.
USMT 4 is included in the Windows Automated Installation Kit. USMT 5 is included in the Windows Assessment and Deployment Kit (ADK).[4] Versions of the USMT are included in the Windows ADKs for Windows 10, versions 1511 and 1607.[5]
USMT consists of two separate programs. Scanstate.exe scans the source PC for the data and settings and stores it in a file. Loadstate migrates the data and settings from the file onto the target PC.
What to transfer is specified as commandline switches in the configuration XML files migapp.xml, migsys.xml, miguser.xml and other optional Config.xml files. Which Users (and their data) to transfer is controlled by other switches.
An example of a "load data on to PC" command could look like this (in one line – newlines and indents added here for readability):
loadstate "Y:\temp\Migrationstorage\WS_toolshop1" /i:"Y:\temp\Migrationstorage\WS_toolshop1\migapp.xml" "Y:\temp\Migrationstorage\WS_toolshop1\migsys.xml" /i:"Y:\temp\Migrationstorage\WS_toolshop1\miguser.xml" /ue:*\* /ui:gutte /ui:Lotta /lac /lae /progress:"C:\Documents and Settings\Administrator\Local Settings\Temp\USMTprog.log" /l:"C:\Documents and Settings\Administrator\Local Settings\Temp\USMTscan.log".. /c
The "Scanstate" command is similar in complexity. Both commands require strict adherence to syntax.
| Version | 98 | NT 4.0 | 2000 | XP | Vista | 7 | 8 | 8.1 | 10 | Cite | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | |||||||||||
| 3 | [6] | ||||||||||
| 4 | |||||||||||
| 5 | [7] | ||||||||||
| 6.1 | [8] | ||||||||||
| 10 | [9] |
| Version | 2000 | XP | Vista | 7 | 8 | 8.1 | 10 | Cite | |
|---|---|---|---|---|---|---|---|---|---|
| 2 | |||||||||
| 3 | |||||||||
| 4 | |||||||||
| 5 | |||||||||
| 6.1 | |||||||||
| 10 |
USMT transfers[10]
Because of the complexity of USMT command-line input, there have been third-party attempts to create GUI front-ends for it. These include (but are not limited to):
Both Workstation Migration Assistant and USMT XML Builder are out of date but there are up to date commercial GUI's for USMT.