Setting up a new Mac from nothing is how I get rid of clutter. It is also slow, because most of the time goes on one question asked a hundred times: what did I have installed, and do I still use it? Apple’s Migration Assistant answers by copying everything, which is fast and defeats the purpose.
So I wrote a small kit that sits between the two. It captures the old Mac, turns it into a checklist I can edit, and rebuilds the new one from only what I kept.
The capture step reads what is installed and, for every application, when it was last opened. Anything used in the past 180 days starts on the keep list. Everything else starts on the drop list. Each section is sorted with the most recent first, so the clutter collects at the bottom of the file where it is easy to see and easy to delete. Settings are handled the same way: only values I changed from the macOS default are recorded, so the new machine gets my choices and nothing else.
Before writing it I looked at an existing migration kit on GitHub and decided against using it. Reading the scripts was instructive. One line set every Mac to sleep after one minute on any power source, which would have taken my always-on machines offline. Another turned off automatic updates. Destructive commands ran with no backup, and errors were silenced so a failure would never show. None of that was malicious. It was one person’s machine written down as if it were a template, and that is the lesson I kept: someone else’s setup script encodes their preferences, including the ones they have forgotten they have.
My own rules for the kit follow from that.
- It installs no runtime. It is plain shell and tools that ship with macOS.
- There is a full dry run. It prints everything it would do before it does anything.
- It never copies keys, keychains or secrets, and it refuses files that look like they contain them.
- Existing files are backed up before they are replaced.
- It asks for administrator rights for one thing only, power settings on a machine I mark as a server.
So far it has been tested against stand-ins for the macOS commands, not yet on a real migration. That first real run is next, on a laptop I can afford to redo.
It is a few hundred lines of shell and it will never be a product. But it turned a day of clicking into a file I can read in ten minutes, and I now know what is on my machine and why.