Moving a Working Dev Machine to Linux With Every File Verified

Developer tools · Sole engineer · complete

Moving a laptop from Windows to Linux when its disk holds 533 git repositories and worktrees, irreplaceable datasets and fourteen months of agent history, all recorded with Windows paths.

The detail

A survey sorted every file on three drives into tiers. A single-command backup to an external drive fingerprinted everything with SHA-256, and an install-day runbook had go and no-go gates. Scripts then brought the work back: re-clone what is on GitHub, overlay uncommitted files, restore unpushed commits from bundles, and rewrite every Windows path in the coding agents' saved state, tested first on a full copy of the real data.

135,218 files were verified on restore, with a full insurance mirror kept beside them. Daily jobs moved to systemd timers afterwards.

Python, PowerShell, Bash, SHA-256 manifests, git bundles, systemd.

What I did

  • Surveyed three drives and wrote a tiered move plan
  • Built a single-command backup with SHA-256 manifests and an insurance mirror
  • Wrote restore scripts for clones, uncommitted files and unpushed commits
  • Re-pathed the coding agents' saved state, tested on a full copy first
  • Verified 135,218 files on restore and ported daily jobs to systemd timers

Stack

Python, Bash, PowerShell, Linux, Git, Automation, systemd, Data Integrity

Case study: https://www.siddhvasudev.com/projects/moving-a-working-dev-machine-to