The story
A recurring freelance request: a machine that has grown too slow or too unreliable for its aging Windows install, owned by someone who mostly needs a browser, documents, and printing that works. Fedora handles that brief well, but only if the migration is done carefully. The first few I did from scratch; after that, I started writing the process down.
The playbook is that document: pre-migration checklist (data inventory, peripheral and app compatibility, the honest "should this machine stay on Windows?" question), the install and configuration sequence, data restore, and a follow-up visit schedule. The goal is the same one I bring to every repair: fix the system, document the fix, prevent recurrence.
Where it stands
Shipped, in the practical sense: it's the process I use on real client machines, refined after each migration. It stays a working document rather than a product, though it's also a quiet experiment in writing operational runbooks, a skill that transfers directly to deploying Medilog in a facility one day.