![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
#1
|
|||
|
|||
Migrating to new (old) machine
I've used SuperDuper! to restore hard drives, but whenever I've migrated to a new machine, I've set it up from scratch. That's a lot of work.
I'm trying to figure out the most efficient way to migrate to a new machine such that I end up with the same operating environment as the current machine, with least post-migration setup work. And without screwing anything up (e.g. iCloud). The SuperDuper! FAQ says don't do this, but gives as the reason the (valid) risk of cloning with an macOS version earlier than what the target machine supports. That shouldn't be an issue here, because (sadly) "new" iMacs are actually 2017 models, which originally (and still?) came with macOS 10.12.4 Sierra. Sierra is up to 10.12.6 now. Resources:
One alternative would be to do the clone before anything else. And/or, using the external drive as an intermediary: clone old iMac to drive, boot new iMac from that drive, clone from drive to new iMac. Since the migration is Sierra to Sierra, and Fusion drive to Fusion drive, APFS shouldn't be a factor. Since I've never tried this before, and so far haven't found hints for successful migration via clone, any advice would be appreciated. |
#2
|
||||
|
||||
Don't do that. Migrate from either a backup or from the original Mac over thunderbolt during first boot. See "I've got a new Mac..." in Help > Frequently Asked Questions...
__________________
--Dave Nanian |
#3
|
|||
|
|||
But doesn't that assume that the new iMac comes with a macOS version that is same or newer than the source Mac?
For example, if the new iMac has Sierra 10.12.4, rumor is you can't use Setup Assistant to migrate from 10.12.6. And you can't update by logging in and running the App Store, because that would create a UID 501, and then you couldn't migrate the user account anymore. In fact, even knowing what version of macOS the computer comes with isn't clear. Maybe start it in Recovery mode before doing anything else? I'm wondering if the solution to the version problem is to erase the drive and install Sierra 10.12.6 (by booting from a Sierra install USB stick), then do the migration via Setup Assistant on the first boot. |
#4
|
||||
|
||||
I actually *think* it'll work with a close version.
You could update the OS (you can do this from network recovery, by holding down a certain set of keys during boot - Apple has a knowledge base article) but then migrate during first boot... that's definitely the way to go.
__________________
--Dave Nanian |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Time Machine Issue with Restored Clone | sdsl | General | 3 | 10-14-2012 08:18 PM |
Time Machine Copy | jerrykrinock | General | 1 | 04-02-2010 01:36 PM |
Needed: Time Machine and SuperDuper guidance | kapalama | General | 7 | 08-13-2009 07:55 AM |
A different angle on SD & Time Machine integration | badlydrawnboy | General | 10 | 10-26-2007 08:37 PM |
write problems after cloning machine | mkrueger | General | 13 | 12-31-2004 07:17 PM |