Beware the OSX Migration Assistant

When I got my Retina Macbook Pro, I used the migration assistant to transfer over all my docs and apps. I had used it in the past and it had worked fine.

But this time, my experience was different. First, it struggled with the amount of picture and music content I tried to transfer over, something about 200G+ of data didn’t make it happy. I ultimately just copied over my iTunes and Aperture libraries manually.

But the bigger problem is that the migration utility refused to copy apps and docs from the “John” account on my old macbook pro to the “John” account on the new machine. It mumbled about the account already existing and demanded I used a new account.

And this ended up being a disaster. I’ve suffered thru a couple months of a constant chown/chmod fest and I have given up. Nothing wants to run, and sudo doesn’t even reliably solve.

So yesterday I nuked the whole SSD and put a fresh install of Mountain Lion on the machine. I downloaded Mountain Lion from the app store, used “Lion Diskmaker”:http://blog.gete.net/lion-diskmaker-us/ to put it on a usb key, rebooted in rescue mode, formatted the SSD, and reinstalled Mountain Lion. And then reinstalled the 50 or os apps, reconnected mail/cal/contacts to all my accounts, reinstalled plugins for xcode, aperture, safari, etc, copied over my Aperture and iTunes library and docs from a network store, and am pretty much back up and running.

Lesson learned. I’m not the only person in the world that has hit this, here is a “good description of the core problem”:http://pondini.org/OSX/MigrationProblems.html and the many ways you can try to solve. One wonders why anyone thought this was a reasonable way for the migration assistnat to act.

  4 comments for “Beware the OSX Migration Assistant

  1. JeffMc
    September 29, 2012 at 2:13 pm

    The Retina MacBook does not require you to use a USB key to re-install. Once you has the SSD wiped, the FW would go put a tertiary boot image to download ML and install from the store. No need for the manual process.

  2. john
    September 29, 2012 at 5:34 pm

    Yeah I saw that, but I was a little worried that it would fail for some reason and so I wanted the local installer. But if it works as you suggest, that would definitely make easier.

  3. Viktor
    September 30, 2012 at 2:39 pm

    I’ve had similar horrible experiences when using MA to move my old MBP to the new Retina.. tried to migrate from my Time Machine backup, but it either couldn’t find it or just hung. Eventually it worked after I fiddled with it for a couple of days (why – I have no idea.) Same experience when moving an older Macbook to to the now handed down MBP.. that I eventually just reformatted and used Setup Assistant.. that worked.
    Apple better make this easier & more robust if they want people to migrate to new hw.

Comments are closed.