I have a MacBook Pro 16-inch, 2019 running Sonoma 14.5 and make daily backups to alternating external SSDs using SuperDuper. (I also use Time Machine with a dedicated drive.)
If for any reason that computer becomes unusable, would I run into difficulties using Migration Assistant to restore the backup data to a MacBook Pro 15-inch, 2017 that is maxed out at Ventura 13.6.7?
In particular, how would Mail.app and email messages stored in On My Mac be affected?
If your scenario is based on Macs and drives you currently own, why not do a dry run before a disaster strikes? Then youâll know for sure what you need to do going forward (keeping in mind, of course, that the 2017 machine should be started up at least once a month to ensure it remains operational).
Iâm pretty sure Migration Assistant will not permit a down level migration.
And in particular, even if it did, Mail would be a problem. Each time you upgrade macOS to a new major version, it converts the Mail database in ~/Library/Mail. This conversion canât be reversed.
I ran into this issue myself a couple years ago. I had just purchased a new Mac and planned on migrating from my âoldâ Mac. Only problem was, I had just before the new unit arrived, updated the âoldâ Macâs macOS such that the macOS the new Mac came with was actually just slightly older and MA promptly refused to migrate. I had to first set up a vanilla admin account on the new Mac so I could update its macOS and only then was I able to migrate from the previous Mac to the new Mac (direct or via TM didnât make a difference). MA was rather strict about this â this was only a ..x update difference, not a different macOS generation.
This has happened to me several times. The OS image on a shipped computer was probably created before it was packaged, and if youâre lucky, represents the current OS version at that time. It may, of course, be even an older version. If you keep your own computer up to date, itâs almost certain that the ânewâ computer will be back-leveled.
As a consequence, my usual procedure when migrating to a new computer is to first initialize and bypass all personalization. Then pretend itâs a computer Iâm getting rid of and ask that all data and settings be erased. Now I can run an normal initialization and migration.
A factory Mac does not come with a user account. You set up either vanilla or migrate. I wanted to do the latter, but since MA doesnât allow for that if the source has a newer macOS than the target, I had to resort to on the new Mac setting up a vanilla account first (without any migration) just to install the macOS updates that would get it on par with the intended source. Once thatâs in place, MA will happily play along and set up a brand new account migrated from the previous Mac.
I havenât set up a new computer recently but as I recall, if you decide to initialize the new computer without migrating any dataâusually people do this to quickly confirm the hardware and software are functionalâyou have to be sure to erase and restore the machine to its factory-fresh state before running Migration Assistant. Otherwise, if you launch Migration Assistant from the Finder as an already-set up user, there can be very disruptive OS-user conflicts (if I remember correctly, macOS makes the user setting up a computer User 501 and Migration Assistant launched from the Finder will assign a different User number to the migrated data).
Interesting. When I get new MBPs, I do a clean state, get all updates, donât log into iCloud, etc. to test them out. Once they work, then I migrate from another older MBP. However, I only migrate other user (standard level) accounts and not the same one (admin level) I used. I donât even migrate the old apps. Just accounts.