Migration Assistant Logs Out

No, I never use the Migration Assistant via wifi (Though, I never tried via Ethernet either), it could take days, depending on how much data/files/pics/music/videos etc you are trying to transfer.

Via USB 2.0 with an external hdd enclosure it still can take several hours, but it is still the fastest way to accomplish that task. Usually I do it overnight, but you might ran into issues, if you have bad files.

Thanks Voca but I was talking to G4444, he said it worked for him.

I have an appointment at genius bar tomorrow night so I'll post on here if they figure out the cause of the logging out

So I tried hooking the computers up via wifi and it worked just fine.

The migration assistant does prompt for an Ethernet cable to be plugged in for faster transfer. I hooked up the Ethernet cable but the migration time just keeps increasing! It's up to 40 hours now!

G4444, how did you get it to start transferring through the Ethernet cable instead of the wifi?

I just plugged it in and it continued from where it was, and worked fine. I didn't have to do anything else.

My solution: "migrated" from time capsule by ethernet. MA is predicting 6 hours for 750 GB.

Computer-to-computer: tried direct ethernet & ether via the router. Crashed every time. The machines did not even see each other when one was 10.9 and the new one 10.8.5; I upgraded the latter to Mavericks.

@orestej: you were clever checking the console. I wish I knew what the error meant! The lethal blow was apparently a crash of the user login session, not a logout. We should not be seeing crashes without explanation, it's totally inappropriate. Even those stupid negative error numbers are better than this.

Edit: I strongly endorse Carbon Copy Cloner. That would have been my next approach.

Same issue both Mavericks both updated both connected via ethernet and firewire 800 still drops the transfer and logs off the destination Mac

Help?

Same issue here--have tried ethernet and wifi, everything updated, power saving turned off etc. Moving a 2010 15" MBP to my brand new Retina 13".

After playing around with every possible combination, I was thinking it was something to do with my user name. I had set up the new machine with a slightly different name than the original, and the target 13" Retina machine was quitting the migration and going to the log-in screen.

When I double checked and named the new machine the exact same as the old, the problem moved to the old machine, which would quit the migration and go directly to the log in screen.

Suggestions?

I was having same problems with recipient computer logging out in the middle of trying to handshake with the source computer, and going back to the login screen. I found that if you have an account name on the recipient which is the same on the source computer, say "admin" on both, then this was causing my problem. I was connecting via Thunderbolt, between an older macbook air, and a new retina. I created a new account on the target mac "admin1", deleted "admin" which I had created when setting up new machine, and it worked.

I have always thought "repair disc permissions" was like the PC specialist advice of "have you tried rebooting it?", but in this case it worked. My new MacBook Pro logged out at every attempt to transfer from my old MacBook. So I repaired permission on both machines and Bingo! - it's off and running (although I am waiting to see how it will handle migrating VmWare Fusion with its partition, etc!)

I experienced this problem when trying to transfer files to a 15" MacBook Pro Late 2013 running Mavericks.

The source and target computers were connected via Ethernet.

The Migration Assistant process on the target computer would exit immediately after I selected the files to be transferred. This dropped me into the login screen.

Running the Console application on the target computer I saw that Migration Assistant (aka Setup Assistant) crashed due to a null/nil pointer exception occurring in one of its threads.

I was able to fix my problem by deleting all of my WiFi connections on both source and target computers. This ensured that the two computers were only communicating to each other via Ethernet cable.

Prior to this I had tried fixing disk permissions which did not solve the problem for me.

Keywords: Migration Assistant, Crash, Mavericks, 2013, 2014

I had also tried:

1. Deactivating my antivirus firewall on the source computer.
2. Turning on file sharing and various sharing options on the source and target computers.
3. Uninstalling my antivirus firewall on the source computer.

The fix that worked for me was deleting all of the WiFi connections on both source and target computers.

This helped me.

OS X: How to migrate data from another Mac using Mavericks