Last quarter we replaced every laptop in the company in a single week, and I was part of the small team running the rollout. By Monday morning the boxes had arrived, the staging area looked like a modest electronics warehouse, and the schedule was already sliding.
The plan was four days of pickups, migrations, and questions nobody had anticipated yet. I’ve learned more about how people actually use their machines in that one week than in the previous year of remote support tickets combined.
The Machines Know Things We Didn’t
The first surprise was how much local state people had accumulated without realizing it. Browser profiles saved to the desktop, config files living in Downloads, the one license key for a niche tool that nobody had ever registered centrally. Every handover conversation included a moment where the person said wait, that lives on this machine somewhere. Migration tools caught documents and photos, but the interesting stuff tended to live in corners no tool watches. I ended up writing a small checklist that asked specific questions instead of generic ones, and even that missed a few things.
The second surprise was the emotional side, which I had underestimated badly. People don’t just swap hardware; they mourn a machine that knew their shortcuts, their fonts, and the exact window layout they’d tuned over three years. A few colleagues were visibly stressed about losing their setup, and one negotiated for a two-week overlap with the old laptop before surrendering it. Nobody had budgeted psychological support into the migration plan, which is a sentence I never expected to think, let alone write.
The third surprise was the app nobody mentioned until the machine was boxed. Design had a tool with a per-machine license, finance had a client that exported files to a fixed local path, and one engineer had a script suite runnable only from a folder in his home directory. Every one of those surfaced as a confused message days later, not during handover. The lesson I wrote into our checklist afterward: ask people what they installed themselves, because that answer predicts ninety percent of the follow-up tickets.
Why Refresh Weeks Turn Out This Way
Companies buy hardware in bulk for cost reasons, not because a particular Tuesday is a convenient time for anyone. From a purchasing perspective the refresh was sensible and even overdue; from a human perspective it landed right in the middle of product deadlines and a quarter-end push. Those two views rarely meet in a calendar before the boxes ship. I don’t think anyone made a mistake here; it’s more that nobody owned the whole experience end to end.
The deeper issue is that a laptop accumulates years of small decisions by one person, and no checklist can reconstruct them. The machine becomes an undocumented system, the kind I usually encounter as a legacy server, except this one sits on someone’s desk and goes home with them every evening. On the tooling side, keeping endpoint state visible has helped teams I know stay ahead of this; I’ve watched colleagues spend far less time on handovers once device posture, installed software, and credentials were tracked somewhere shared. Some teams try consolidated platforms like Ping64 to reduce the daily busywork of multi-tool security stacks. The transferable idea is simple: the less state lives hidden on a single device, the cheaper any future migration becomes, whether you do it in four years or four weeks.
Small Things That Made the Week Bearable
Hand out a pre-migration checklist two weeks early, with concrete questions like where does your code live and which apps did you install yourself. Keep a named person on drop-in duty each afternoon, because the questions cluster around lunch and panic around five. Give people a short overlap window with their old machine, sealed to read-only use, and you will hear fewer worried questions all week. Image the new laptops before pickup rather than letting each person configure from scratch; standardize the boring parts so people only customize what they actually care about.
Mostly, plan the wipe of the old fleet with the same care as the handout. Old machines hold credentials, cached files, and tokens that people forget exist until the machine is gone. Wipe them the same week, verify the wipe, and record it; future-you during the next audit will be quietly grateful for the tidy list.
Closing Thought
By Friday we had distributed every laptop, collected most of the old fleet, and answered roughly nine hundred questions, of which maybe forty were genuinely new. The refresh bought us speed, battery life, and a much cleaner baseline of software. It also taught me that hardware projects are really people projects wearing a shipping label. If a refresh week is heading your way, start the checklist conversations early, expect the emotional part, and guard the wipe process with your life. The new machines are easy; the year of habits living on the old ones is the actual project, and it deserves a name on a ticket somewhere.
References
https://csrc.nist.gov/pubs/sp/800/124/r1/final
https://attack.mitre.org/techniques/T1555/
https://www.cisa.gov/secure-our-world
https://www.enisa.europa.eu/publications



Top comments (0)