"21 hours remaining": Is Migration Assistant meant to be this slow?

I'm trying to migrate from one Lion machine (upgraded from Snow Leopard) to another new Mac Book Pro. 140 G total. It says it will take 21 hours? Is that normal? And when the system looks like it is sleeping, is it?

Wifi. But I dumped the Wifi, SuperDuper!-ed the old Mac to a drive, then am now migrating from the drive. Says it will take 2 hours.
I was surprised the Migration Assistant didn't determine that the machine was set to allow it to sleep. Should at least be a warning about that.

Similar Messages

  • PC went to sleep 3 hours into a migration assistant transfer to MBA.

    Is there any way to recover?  The situation was complicated by the fact that while the screen was dark on the PC, I must have inadvertently hit the close box.  I turned off the sleep function on the PC (too bad the migration assistant didn't remind me, although it did tell me to turn off software update).
    The migration assistant on the MBA remained on the whole time.  When I restated MA on the PC, I was hoping it would resynch and continue on.  It did not. 
    If I restart it on the Mac, will I get a bunch a duplicate files or will it know where to pick up?  Any suggestions?
    Thanks.

    the system should have gone to sleep only after the migration was finished.
    compare folder sizes / folder to verify everything is there.
    to be on the safe side or if you spot data missing, I'd just start over from scratch.

  • HT4889 Migration Assistant taking too long

    I am trying to Migrate from my old MacBook Pro to my new MacBook Air using a Thunderbolt cable but the Migration Assistant is telling me this will take 642 hours. How can this be?

    Welcome to Apple Suppport Communities
    You should see that time decreases quickly. Note that sometimes Migration Assistant may give a wrong remaining time. If you see that Migration Assistant doesn't progress or it keeps saying that it will take 642 hours, unplug and plug your Thunderbolt cable again. If nothing works, restart the Mac that is receiving the files from the other computer and try again. Make sure that Migration Assistant isn't transferring the data through Wi-Fi turning off Wi-Fi on the menu bar

  • Migration Assistant and user permissions broken

    I just used Migration Assistant to my old early 2008 unibody 15" MBP to import stuff to my brand new 15" quad core i7. The old machine was connected through FW800 in target disk mode.
    Somehow this process failed and it left me to an odd result which I cannot figure out how or why such things would happen. I have used migration assistant often successfully, if not exactly this way.
    I already decided to start things from scratch, but I would appreciate any insight that somebody might have. Like what just happened? Do you have similar experiences?
    The process:
    - In my old machine I had two users, for the sake of argument, "MainUser" and "OldUser".
    - In my new machine I had two users made right after a clean install, "Admin" and "MainUser". I usually work with "MainUser" so I made one without thinking about it much.
    - I connected the old machine in Target Disk mode and started Migration Assistant under Admin of the new machine. First question I answered to migrate from another disk, as the other machine was in Target Disk mode. Next one asked to pick the disk and that is followed by a selection "What to migrate". I wanted to install applications from scratch, so I checked everything except applications. I do not know if this is relevant, but I would imagine it is not.
    - A pop-up appeared, which correctly told that there already is MainUser on the new machine. The dialog gave me three options: 1. Rename the account that I am transferring, two with the same name could not exist 2. Replace the existing account with the one I am transferring 3. Do not transfer this account.
    - I chose 2, because there was nothing worth saving in the MainUser account on the new machine. Continue.
    - Watch a few hours of progress bar
    - After the migration process the machine was in very odd state. I logged in as MainUser and it oddly looked like default Snow Leopard state, not like the desktop of the migrated account. No folder items that I had on the desktop previously were visible, language was default English and desktop background was the Snow Leopard nebula. I tried, but could not change that in the system preferences.
    - Closer inspection revealed that I did not have permissions to access any of the folders under my username, like Documents, Music, Movies etc. This also explained the desktop problems. It meant that none of the programs were allowed to read or write any data under Library folder so everything was and stayed as default. For instance, any settings that I tried to change and which might even apparently change, would reset back on logout. Programs settings were empty, like no bookmarks on Safari or Apple Mail did not show the mail accounts.
    - I checked with Terminal what was on with permissions, and for some odd reason, all the folder owners under MainUser belonged to OldUser(!).
    - There is no reason that I can think of why that user account would have anything to do with this migration -- after all, the whole deal was supposed to be to migrate (or overwrite) MainUser, not to mess with OldUser in any way, except bring that over as a separate item.
    - For the sake of argument, I also logged to OldUser account and that seemed to be transferred correctly. No issues with file permissions or the desktop. Only MainUser was messed.
    - I decided to take the ownership of all files under MainUser account back. I did "sudo chmod -R MainUser *" to grab everything. Immediately the stuff on desktop appeared. After logout and login rest of things seemed to return (mostly) to those places that the migrated MainUser should have had, like the desktop background, dock position and even Apple Mail now showed my old emails.
    Even if I sort of fixed things, I have iffy feeling about the whole process.
    I decided to start over. This time I will not have MainUser account on the new machine to avoid any further hassle. While I suggest everyone to avoid this situation and not to have users with same name or let Migration Assistant to run this overwrite -option, I would like to hear any speculation why or how this might have happened.
    If Apple is listening, you might check the latest Migration Assistant in the above case. There might be a bug. Thank you for listening.

    I think it is inadvisable to have the same user account on the target machine when using Migration Assistant - just from recollection this is known to cause problems.
    However, in my experience (and I have used MA many times across many machines), even when apparently completing successfully, MA simply does not work properly when it comes to permissions.
    For example, after using MA to import my previous user account to my new MBP 2.3 i7, I cannot drag anything out of the dock - it just doesn't work.
    Also, content of my desktop folder does NOT display on the desktop itself.
    I have tried applying specific permissions to this folder, for my user account AND "Everyone" - it makes no difference.
    I do not regard Migration Assistant as fit for purpose.

  • Migration Assistant won't do verification

    I have read the migration assistant tips and tricks, and questions on this matter and I cannot find an answer, please help.
    This is my first apple computer (MBP Retina) and I want to migrate email, calendar etc from my Windows 7 desktop PC.
    I installed Windows Migration Assistant (WMA) on the PC.
    I connected an ethernet cable directly from the PC ethernet port to the MBP thunderbolt port.
    I started the migration assistant software on both computers. On the MBP I select 'Migrate from PC to Mac'.
    The MBP recognises the PC by name, so I click on the displayed name and 'Continue'.
    The MBP throws up a 6-digit verification number and tells me to verify it on the PC.
    BUT.... the PC WMA software never displays the verification number. I can wait for hours. The migration assistant will not proceed without the verification number appearing on the PC.
    I have restarted both computers and the same thing happens.
    Please help me.
    If there is no solution, what is the 'unassisted' way to migrate from PC (Office 2010) to Mac?

    That isn't a valid link to your picture (it's a link to the file on your computer). You would need to post it to a serve (and remove the spaces in the name) and post that link here.
    However it would appear that your short name is 'dalechristiansen' so presumably you originally created a user with that short name and your full name as.. the full name (unless it was just 'Dale'. Whatever you did before when you created your account is what you should do now. Then you can copy the equivalent folder's contents. (You might have problems replacing some of the root level folders, in which case you shuld copy their contents into the equivalent folders).

  • Migration Assistant and permissions issues with new Mac Pro

    Hi There,
    I've not had any significant issues with Migration Assistant in the past but I can't create a reliable system with my new Mac Pro.
    After using Migration Assistant during the initial setup, my user account wasn't even transferred. I tried restarting but in the end, I followed these instructions to reset and run the assitant again: http://stationinthemetro.com/2013/11/10/make-mavericks-re-run-the-setup-assistan t
    I've just finished running it for a second time, and while the user account is now on my new system, there are so many permissions issues that the system is unusable (I can't even run Safari). Creative cloud, 1Password, safari, Dropbox are all apps that give me Disk i/o or permissions errors.
    If I look in the user folder, many directories within it have a red minus icon. I've tried fixing permissions using Disk Utility but something is not right.
    In the past, the new system just boots like the old one but this time round, it asked me to create an account after Migration Assistant had finished - is this normal? I used the same username and password as before but I'm not sure Migration Assistantis working properly.
    Does anyone know a full-proof way of fixing and transferring my account without having to spend hours downloading OSX for a full erase and install?
    Any help would be much appreciated.
    Cheers
    Ben

    Thanks for the reply,
    I didn't understand exactly what to put into AppleScript sorry (never used it before) - so I just ran the following from the Terminal:
    $ echo $UID
    $ sudo chown -R 503 ~
    And restarted - everything works now - thanks heaps.
    What had happened and is this something I did or did Migration Assistant just get confused?
    I have 3 new Mc Pros to setup on Monday so just want to ensure those are hassle free.
    Cheers
    Ben

  • Migration Assistant keeps locking up

    I have tried three times to migrate my PB17 to my brand new iMac 20" with iSight. All three times, the migration chokes when the iMac says I have 1 hour 35 minutes to go on the migration. At that same time, the PB17 (in target disk mode) appears to lock up (the firewire logo quits moving around on the screen).
    I "chatted" with Apple tech support last night and couldn't figure it out so I'm coming to you folks for help.
    Oh, another thing, since I have an accout as myself (Tark Bunch) on BOTH the iMac and the PB17, the migration assistant doesn't like this, so I have to re-identify the PB17 user as someone else before continuing with the migration (in this case I become TarQ Bunch). This seems to enable the migration to start, but never allows for a successful migration.
    Apple tech support asked if I had updated the firmware on the PB17 (I haven't, but assume it is up-to-date with the software updater). They also asked if I had the fileVault on (no I don't) and they thought I should run disk utility on the PB17 (which I haven't had time to do yet).
    looking forward to suggestions (better yet, solutions
    -Tark

    Royal Pain is right, but sadly, this was what I had to do to migrate.
    I took your advice, hooked the two computers together via Firewire, with my old computer in target mode.
    I then dragged directories over. By this approach, I ended up with the old computer locking up during the transfer. I finally traced it to a corrupt jpg.
    Since I had already moved a lot of files accross to the iMac, I then purged those files off of the old PB17.
    I emptied the trash, rebooted and attempted migration again. I deliberately did not migrage Applications and the Migration went off without a hitch.
    All my stuff was on the new system (except the files I had purged) and my iTunes database remembers what I played last and how many times
    It would be sweet if Migration assistant could run a diagnostic to find these files and save ourselves a lot of work, but maybe we are the rare exception (My wife's and kid's migrations went well with no hitches...)

  • Is there anyway that I can download just Migration Assistant?

    I deleted it a while ago, positive that I would never need it. Now I do, how can I get it back!?

    What are you going to use the Migration Assistant for?
    If it is to migrate between an Intel Mac and a PowerPC machine, that doesn't work well. Instead these directions have been made:
    http://discussions.apple.com/thread.jspa?threadID=435350
    Intel Macs have been the type of Macs that have been new since 2006.
    If it is between similar processor machines, usually a newer machine would come with discs that contain the Migration Assistant in anycase, making this whole point moot.

  • Migration Assistant Problem

    Bought a new iMac 24" 2.66 GHz. Tried to run Migration Assistant via Firewire from old iMac (Power PC G4 OSX 10.4.11). Tried it in the initial set up but didn't work. Then tried it after initial set up of new Mac and was prompted that I needed to change the name of the account in order to migrate since the main account on my old and new computers was the same. Didn't seem like I had another option. Transferred data but it is stored in a separate account from the main one I used to set up the new computer, and I have to log out of the main account to the other account to see it. Is there any way to make these 2 separate accounts to talk to each other? Should I just forget the initial account and use the new account even though the computer is set up through the initial account? Should I just find a way to start over and restore factory settings?
    Friends say Migration Assistant works seemlessly but this has been anything but.

    bdd95 wrote:
    Bought a new iMac 24" 2.66 GHz. Tried to run Migration Assistant via Firewire from old iMac (Power PC G4 OSX 10.4.11). Tried it in the initial set up but didn't work. Then tried it after initial set up of new Mac and was prompted that I needed to change the name of the account in order to migrate since the main account on my old and new computers was the same. Didn't seem like I had another option. Transferred data but it is stored in a separate account from the main one I used to set up the new computer, and I have to log out of the main account to the other account to see it. Is there any way to make these 2 separate accounts to talk to each other?
    no.
    Should I just forget the initial account and use the new account even though the computer is set up through the initial account?
    yes. just delete that account and use the migrated one.
    Should I just find a way to start over and restore factory settings?
    Friends say Migration Assistant works seemlessly but this has been anything but.

  • After using "migration assistant" from my old iMac to my new iMac, some tools stick while using Photoshop CS 6 Extended. My current operation system is 10.10 Yosemite. I was wondering if UN installing then RE installing CS 6 might solve the problem. If th

    After using "migration assistant" from my old iMac to my new iMac, some tools stick while using Photoshop CS 6 Extended. My current operation system is 10.10 Yosemite. I was wondering if UN installing then RE installing CS 6 might solve the problem. If this is recommended, I would need complete instructions on doing this. I have there serial number for the product.

    using migration assistant is problematic.
    at this point yes, you should uninstall everything migrated, clean and then reinstall properly using the installation files.
    cleaner:  Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
    installation files:
    Downloads available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  13 |12 | 11, 10 | 9, 8, 7
    Photoshop Elements:  13 |12 | 11, 10 | 9,8,7
    Lightroom:  5.7| 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5
    Contribute:  CS5 | CS4, CS3
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.
    window using the Lightroom 3 link to see those 'Important Instructions'.

  • Migration Assistant "Looking for other computers ..."

    After a new installation of Lion, I can´t restore my users from a Time Machine Backup with the Migration Assistant. In the Time Machine disk I have only the users backup, not the complete MacBook Pro. The back is from the same machine with Lion.
    See the image attach.

    Pondini wrote:
    DrSam wrote:
    One other caveat, which I learned in my search...  Apparently if you are restoring via Migration Assistant, you can't restore to a user account that you are currently on, and you can't restore to a user account with the same name as the one you are restoring, without replacing the former.
    Yes, other than using Setup Assistant when your Mac first starts up, that's the only workaround.
    See option #4 in Problems after using Migration Assistant
    And unbelievable that this would be the way Apple intended the process to go.  I still am not sure how I could have gotten this to work from the start within Setup Assistant, which obviously you're supposed to be able to do,
    That's not how it's supposed to work.  Setup Assistant should have found the sparsebundle and shown it in the Select the Source window.   Usually it does.
    It's possible the backups were slightly damaged.  It's also possible clicking Continue on that window might have, uh, kick-started it, as it did for a couple of other folks.
    I agree that Setup Assistant "should" have found it, but it didn't...  That was what my last sentence was referring to as well.
    For what it's worth, I had tried clicking on the grayed-out continue button like people here suggested.  For me at least, it acted like every other grayed-out button has, and did not respond.
    You may be right that my backup .sparsebundle was damaged or something, but I'm not really sure why that would be or how one might know, or even what to do about it if you did suspect that to be the case.  (It checks out on Disk Utility, and Finder has no problem with it.  Heck, even Time Machine recognizes it as an "Other Disk" backup and lets me browse it.  I just couldn't get the Setup & Migration Assistants to recognize it.)
    I figured now that I got it to work I'd document my experience here for the benefit of the next poor guy who has to spend his Christmas eve Googling for this thread...

  • Migration Assistant spins a wheel

    Just received back a repaired imac g5 (version A) with 10.4.11 installed on a "wiped" HD.
    I have an external drive with a clone of my imac before the repair. It was made with Prosoft Data Backup 3 with a Mac OS 10.3.9, and is FW bootable. I have tried to use Migration Assistant to transfer from this external drive to the "new" mac but keep getting hung at the first step : " Pick users to transfer..." just get a spinning wheel. Appreciate any help!

    Thank You! Checked my ownership on the external drive files and they were my "old" computer name; the "new" one has "system" as the owner of all the files. I assume I should change the external drive clone ownerships to "system"? Will try this and see if it works...

  • Manual Migration vs. Migration Assistant

    I am finally going to upgrade my Mac Pro to Mavericks. It is currently running SL 10.6.8. I will definitely perform a clean install and then reinstall all applications manually. But I can't decide if I should use the Migration Assistant to move my data over or if I should do it all manually.
    Reason for a completely manual migration:
    A clean start. My system currently contains over a decade's worth of clutter. My user library folder is several hundred GB in size and I have no idea what most of the stuff in there is. It's a mess and it doesn't feel right.
    Reason for using migration assistant:
    It basically guarantees that nothing important is forgotten and - more importantly - it automatically takes care of stuff that can be very troublesome to transfer manually, like Mail data for example. The Migration Assistant seems safer in this regard than a completely manual migration.
    What do you think?

    I would use neither of those, and use Setup Assistant instead. Setup Assistant is available right after you boot up from your newly upgraded system; it asks you if you want to transfer your data over. Answer yes. It will be quick and easy. Answering no and attempting to do it later, whether by Migration Assistant or by manual copying, is usually a mistake in my experience.

  • Migration Assistant vs. Cloning

    I apologize for spamming this forum a bit with the same topic but I'm not really getting the answers I need and the particulars of my problem keep changing. I have an G4 MDD DP 1.25 OS X 10.4.11 with a "master" 80 gig unix hard drive, and a 300 gig ATA "slave" mac os journaled extended drive. I'd like to transfer everything to my G5 DP 2.0 OS X 10.4.2 with 120 gig Mac os Journaled extended hard drive. Carbon Copy Cloner and SuperDuper will not work because both drives have to have the same format, or simply won't work with Unix. I just tried Migration assistant, which didn't work with two of the more important app's I was transferring (logic and Mlan connector for my digital mixer). So does anyone have any suggestions? Thanks so much for your time!
    p.s. All my app's are on the master hard drive, while all the audio files associated with Logic are on the slave drive. I also bought both machines used so there is no apple care.
    Also I have two external hard drives in case that could factor into a solution

    I'm not sure what you are calling Unix, but Mac OS X is itself a Unix based operating system. If you have a partition that is some form of Linux, while another Mac OS X that complicates matters though.
    Migration Assistant will take applications and data from one Mac of a chip series to another Mac of the same chip series (G3, G4, G5) (Intel Core Solo, Duo, Xeon). If they are of different chip series, Migration Assistant has a tendency to slow if not fail. It also has difficulty with migration of anything but to a newer or the same Mac operating system. Migration to an older operating system may not work, and doubtful if it works to anything but a Mac operating system.
    Cloning can only be done between two Macs of exactly the same vintage and series, and naturally with applications that have the correct number of licenses, as well as operating system.
    Barring those two, you'll be forced to do a piecemeal migration between Macs, such as described here:
    http://discussions.apple.com/thread.jspa?threadID=435350&tstart=0
    Message was edited by: a brody
    Message was edited by: a brody

  • Missing iTunes 9 songs after transfer with SL Migration Assistant

    I have a backup drive where I stored 82+ gigs of music, all imported from cd. They were saved using various versions of iTunes as AAC's. I transferred the Music folder from the external drive to a new iMac via OS 10.6.2 Migration Assistant.
    I noticed this morning that some music was missing from the iTunes library that were still contained in my iPod... which I didn't sync! Whole artist folders are missing, some songs of other artists are gone. I lost 3+ gigs of music. I checked the new iTunes music folders, these artists and songs are not present.
    Unfortunately, I didn't notice the difference in total storage when I opened iTunes after transfer, 8000+ songs, over 6 years of saving. And wiped the external drive and set it up as a clone backup for the new iMac.
    The only factor I'm seeing is that every artist I've identified as being gone was a fairly recent save under iTunes 9. I've been doing a lot of saving over the last 3 months.
    Anyone else losing MA transferred music with iTunes 9 and/or Snow Leopard?

    Hello there ronadrew,
    It sounds like you 2 libraries of content you want to move over to your new computer. As far as your iTunes library is concerned, you can certainly use File Sharing as an option if you like but you have to modify folder permissions and access to do that. This article should help you do that, named:
    OS X Yosemite: Share your files with other Mac users
    If these computers are both connected to the network via Wi-Fi, it may be faster to copy the iTunes library to an external drive, then copy the library over to another computer using this article:
    How to move your iTunes library to a new computer
    As far as your Calibre library you may be able to use one of the above methods to copy your library over, but I would check with the support and/or documentation available from the developer for the best way to go about that.
    Thank you for using Apple Support Communities.
    Regards,
    Sterling

Maybe you are looking for