There are a few ways of telling which ones of your apps are native too: https://www.macrumors.com/how-to/tell-apps-optimized-for-m1-...
The spring transition was lightly rocky, had some Docker issues, a couple Node image handling packages gave me grief. I had roped off three days for troubleshooting but only needed an afternoon.
Last night’s move was flawless.
Tip: if you’ve got a Thunderbolt 3 cable, use it. No network settings necessary, just plug both computers in. My brother in law’s setup too a couple hours, mine took twenty minutes.
I had a true Thunderbolt 3 that I use with an eGPU handy
Docker worked surprisingly well; it just automatically uses QEMU for all the x86 images, flagging those containers as a warning that they aren't native. I went through a hassle to get arm images to speed things up, but that just makes running builds on an x86 build agent less repeatable and images uncachable.
To prepare I do a quick pass over the script and update version numbers and such. When the new laptop arrives, I curl down my install script and run it, and I’ll end up with a Mac that works the way I expect it to with my favorite apps, but the system kind of defaults to “fresh” - I need to think about “what do I want to add” instead of “what do I need to undo or remove”.
This is more repeatable than the transfer utility, especially for employer-issued Macs. Are they gonna let me run Migration Assistant on my last day to copy state to my next employer, or my personal laptop? Nope!
My setup script: https://github.com/justjake/Dotfiles/blob/new/mac-setup.sh
Yikes, I wonder if this is a universal problem or just an anecdotal issue.
I have a lot of preferences and such built up over the years, and if I didn't use the assistant, I'm not sure how I'd thoroughly migrate everything.