#Migration assistant target disk mode how to#
#Migration assistant target disk mode upgrade#

Uninstalling VirtualBox did not work, but reinstalling it did. The documentation said to uninstall VirtualBox and re-install it.

#Migration assistant target disk mode upgrade#

I donвЂ™t know if this was because of Catalina or because of Migration Assistant, but I had to upgrade my VM software ( VirtualBox) to the latest version.If you use Git, youвЂ™ll need to hop into your directories and run git status to force the connection.Office is the only major culprit IвЂ™ve found, but I like to fix this stuff right away, so give each of your major apps a first-run experience. Some software, like Office, needs to be re-activated.Most of your software does not need to be re-authenticated.(Because of this, IвЂ™ll be returning the cable I bought.) And you donвЂ™t need Thunderbolt 3 for that throughput. I bought this Thunderbolt cable to make this process faster, but the transfer was never faster than 90mb/s. You can use the USB-C cable that came with your Mac. Target disk mode means you can connect your two machines together with a good old Thunderbolt or USB-C cable.Boot into target disk mode and save yourself some trouble. ThatвЂ™s too slow and unreliable for my liking. If you just run Migration Assistant on your old machine, the entire process will run over wifi. The fastest way to do this is to boot up your old machine in target disk mode and connect them via a cable.

#Migration assistant target disk mode how to#

(Related: Catalina is nicer than I thought it would be, although IвЂ™m unsure how to approach Zsh.) 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.