I used migration assistant with a Time Machine backup from my (temporary) M1 Mac mini to the new M2 Pro Mac mini. Worked great, but took all night.
I’ve thought about the single Time Machine backup to restore to my new Mac mini as well. My only concern is how much legacy garbage will beI migrated from a late 2015 iMac using a time machine backup, 99.5% no issues. However a few days before i received my M2 Pro, I updated my old mac and made a fresh standalone time machine backup on an ssd external I purchased to use with the new Mac. 530GB migration and such took less than fifteen minutes total. The only issues so far was no contact sync ( there were dozens of "fixes" to this posted online, but....) , so I just dropped my phone/synced contacts to the M2 Pro and all was good with only one merge suggestion on the M2 Pro. I don't know if the single copy TM backup made a difference, but it made me feel better going in and so far, all is good in my desktop world.
I did clean out a ton of no longer needed legacy junk before making the Time Machine backup and i figured i could fine tooth comb the rest out after the fact.I’ve thought about the single Time Machine backup to restore to my new Mac mini as well. My only concern is how much legacy garbage will be
Migrated from my late 2014 iMac that is useless and will just take up space on the new mini?
I ditched the myriad backups from my old iMac 2015, set up the M1 Mac mini fresh and used iCloud to populate it with documents, photos, bookmarks, mail accounts etc. I only downloaded the apps I actually use. When I migrated to the M2 Mac mini, I thus avoided the old apps and system files from the iMac.I did clean out a ton of no longer needed legacy junk before making the Time Machine backup and i figured i could fine tooth comb the rest out after the fact.
I'm also thinking of starting fresh from a MM2018. I'm only concerned I won't be able to transfer over the small settings and tweaks that I have made (many of which I can't even recall)🥲These days I just start fresh with a new machine. I keep my data in dropbox and an external RAID and I download and install all apps and drivers from their websites.
It still takes way less time than dealing with migration assistant’s c**p. And I would just end up doing it manually anyway after it fails.
On the positive side, you'd discover a range of new options to tweak in the depths of system settings. 🙃I'm also thinking of starting fresh from a MM2018. I'm only concerned I won't be able to transfer over the small settings and tweaks that I have made (many of which I can't even recall)🥲
True, that!😆On the positive side, you'd discover a range of new options to tweak in the depths of system settings. 🙃
No, but incompatible apps or apps with newer versions already installed may not be transferred or may not be usable, says Apple support https://support.apple.com/en-gb/guide/mac-help/mh27921/macTrue, that!😆
By the way, does Migration Assistant allow you to select which application to transfer over and which not to? I'm not exactly how it works.
Reason is because I have an old copy of Adobe Lightroom 6 which I can't reinstall due to it having a 32-bit installer, so I can only migrate it from system to system😂
Thanks. Yes the problem is only with the installer. I was originally thinking of not migrating everything over from my MM2018 but instead start from scratch, but I want to keep Lightroom 6 working, I have to migrate it over instead of reinstalling in on the MM M2 Pro (since the installer won't work)😅gnohz wrote:
"By the way, does Migration Assistant allow you to select which application to transfer over and which not to?"
No.
With setup assistant (and migration assistant), it's "all or none" insofar as migrating applications is concerned.
However...
Are not the "32-bit problems" with Lightroom 6 ONLY with the installer itself?
I'm thinking that since it's already installed and running, it will migrate and run (under Rosetta2) WITHOUT the installer issue. The only way to know is to try it.
Thanks for the info! I have to give it a try to be sure😅 Anyway, I'm prepared for the app to no longer work on the newer os, which means I have to also migrate my entire photo catalog to an alternative software😬No, but incompatible apps or apps with newer versions already installed may not be transferred or may not be usable, says Apple support https://support.apple.com/en-gb/guide/mac-help/mh27921/mac
Did you do any cleanup prior in the user library to get rid of legacy intel stuff or uninstalled apps?Just used migration assistant on my M2 Pro.......worked slick with no issues other than having to log into iCloud and a couple of apps needed disk access. Nice, got have everything all setup and working without spending days doing it.
Migrated from an Time Machine backup from a 2017 iMac 27"
Yes, I got rid of of old APPs I no longer used and purged files that are out-dated.......Did you do any cleanup prior in the user library to get rid of legacy intel stuff or uninstalled apps?
How did you determine which files were outdated?Yes, I got rid of of old APPs I no longer used and purged files that are out-dated.......
Also cleared out things like the downloads folder, etc.
I sold my 2017 Mac to "Sellyourmac" right after I ordered my M2 Mini, so I made sure I had good Time Machine backups and also manually backup a bunch of stuff, just in case.
Apple would only give me $180 for it, I got $525 from SYM.
would you suggest migrate assistant then ? or could i plug in the ssd t7 get information from that? im concerned about corrupting the new one with old stuff from the 2012."I’m currently booting from an external t7 Mac mini 2012 what is the best way to import the mail safari and keychain please?"
The email could be "manually migrated" without problems, using Mail.app's "import" menu choice.
If by "safari" you're talking about bookmarks, they can be easily migrated as well. Go to "export bookmarks" in Safari.
BUT...
I don't see how the keychain can be manually migrated.
REASON WHY:
You're going to create a NEW account on the NEW Mac.
Even if you use the same username and password, the Mac will see the "new" account as DIFFERENT FROM the "old one".
The keychain on the old Mac will be associated with the old account.
I don't see how it can be made to work with the new one (which will have its own keychain).
There may be workarounds for this, but I don't know them. Perhaps others will help.