PC Replacement: Zero Data Loss User Profile Migration

LIMEHAWK - Managed IT

Home>Incident Reports>PC Replacement: Zero Data Loss User Profile Migration

Incident

CFO's four-year-old laptop was throwing SMART warnings and random freezes — classic signs of an SSD about to give up. Replacement machine was already approved, ordered, and sitting on our bench. The actual job wasn't the hardware swap, it was getting four years of the CFO's working environment onto the new machine without losing a single thing. We're talking documents, browser bookmarks, Outlook signatures (with the embedded logo), app settings, Sticky Notes — everything she'd tuned to her workflow over four years. Executive-level user, zero tolerance for "I lost my files."

The challenge

A manual copy gets you the obvious stuff — Documents, Desktop, Pictures. What it misses is the stuff that actually makes a computer feel like yours: AppData\Local and AppData\Roaming, HKCU registry settings, browser profiles with saved logins and extensions, Outlook signatures (which live in AppData\Roaming\Microsoft\Signatures), custom dictionaries, pinned items. OneDrive sync only covers Documents and Desktop, and even that's inconsistent if selective sync was ever touched.

- Documents: 28GB of files
- Desktop: shortcuts and live files people forget aren't synced
- AppData: app settings, Chrome profile, Teams cache
- Outlook: custom signatures with embedded images
- Sticky Notes: yes, executives live in these
- registry: HKCU preferences across dozens of apps

Solution

Microsoft's User State Migration Tool. USMT has been the enterprise standard for this for years for good reason — it's built to capture exactly this kind of state. Two binaries: ScanState (capture) and LoadState (restore). XML config files define the scope. Migration store can be encrypted in transit with /encrypt and a password. Works across Windows versions, so a Win10 source to a Win11 target is a supported path.

What USMT captures

ScanState reads the MigUser.xml, MigApp.xml, and MigDocs.xml config files and captures the full matching set of user state. It pulls registry keys under HKCU, AppData (Local and Roaming), the full user profile tree, and application-specific settings for the apps Microsoft has shipped templates for. LoadState reverses the process on the new machine, restoring everything to the right paths even when the target OS version differs.

- user folders: Documents, Desktop, Downloads, Pictures
- AppData: Local and Roaming app data
- registry: HKCU settings and preferences
- browser data: Chrome, Edge, Firefox profiles
- Office: signatures, templates, custom dictionaries
- Sticky Notes and other UWP app state

Outcome

Ran ScanState on the old laptop — took 35 minutes for a 47GB capture with /encrypt turned on. Migration store went to a network share. New laptop was already imaged and domain-joined, so LoadState pulled from the share and ran for about 45 minutes. CFO logged in, everything was where she left it: same desktop wallpaper, same Chrome bookmarks bar, same Outlook signature with the logo, same Sticky Notes on the right side of the screen. She noticed approximately none of the things we moved, which is the gold standard for a migration. Old laptop got wiped and decommissioned.

- data migrated: 47GB
- ScanState time: 35 minutes
- LoadState time: 45 minutes
- total elapsed: 90 minutes
- data loss: zero

Key takeaways

Takeaway

USMT beats manual copy for completeness on executive migrations.

Takeaway

/encrypt protects the migration store on the wire and at rest.

Takeaway

works cleanly across Windows versions (Win10 to Win11).

Takeaway

the win is the user not noticing anything changed.

Need help with something like this? Contact us

• Automating CrushFTP Upgrades and In-Place Updates (Automation)

• Winget for RMM: Silent Software Deployment at Scale (Automation)

• Mass BIOS & Driver Updates: Dell Fleet Vulnerability Patching (Automation)