I upgraded from Mojave to Catalina and, for the most part, everything went smoothly. It does not appear to matter if one machine is on a different OS from the other.It does not include the cache, which is also probably for the best. It included all my virtual machines, which is also great. This even includes anything you may have installed on the command line, which is great. Everything from your user account appears to get migrated over.Here are some tips, tricks, and gotchas about this migration. Rather than go down that route this time, Migration Assistant - which I’ve only ever heard good things about - seemed like a good bet.īut it’s not all smooth, of course. That takes a lot of time and often encounters strange bugs. In the past, I’ve used SuperDuper to handle my migrations. And next time I need to do this, I’ll refer to this post as a starting point. I wanted to write some tips and tricks about this process, because Apple’s kbase article isn’t particularly clear. So I used Migration Assistant for the first time. Between my Linux VMs, my Git repositories, and even all the fonts I have installed, setting up a new machine would be a laborious practice. I like setting things up from scratch and starting with a completely new setup, but that’s rarely feasible these days. (Which hopefully mean I can leave the house with my laptop without living in fear.) But that meant I had to migrate all my files and settings to this new machine. I caved and I bought myself one of the new MacBook Pros with the scissors keyboard switches.
0 Comments
Leave a Reply. |