Migration Assistant very slow

Anyone know if there is a way of speeding this up or is this just the norm.  Been doing this all week.  An older iMac with about 450gb to transfer onto a new macbook pro usb-usb ... took 28 hours.  Now doing an old iMac to a new iMac 1.6tb this time via ethernet.  Started this morning and its predicting 109hours.......Thoughts to speed this up very much sppreciated.

Welcome to Apple Support Communities
Wi-Fi and Ethernet are very slow ways and I don't recommend to use them unless you have to transfer small sizes. If they are big, don't use it.
What you can do is to make a Time Machine backup on your old hard drive, so get an external drive to do it. See > http://support.apple.com/kb/HT1427
After making the backup, connect the external drive to your new iMac and use Migration Assistant to restore your files. If you haven't set up your iMac yet, Setup Assistant will ask you to restore the backup.
You have to restart both iMacs before doing this, so migration will be stopped

Similar Messages

  • Windows Migration Assistant very slow via ethernet cable but after 36 hours .......

    I am using Windows Migration Assistant to migrate from my 3 year old HP laptop running Windows 8 to a brand new iMac using an ethernet cable..
    The pairing went well but, after 36 hours the laptop tells me there are 13 hors to go and iMac says 8 hours +. What am I doing wrong?

    Welcome to Apple Support Communities
    Wi-Fi and Ethernet are very slow ways and I don't recommend to use them unless you have to transfer small sizes. If they are big, don't use it.
    What you can do is to make a Time Machine backup on your old hard drive, so get an external drive to do it. See > http://support.apple.com/kb/HT1427
    After making the backup, connect the external drive to your new iMac and use Migration Assistant to restore your files. If you haven't set up your iMac yet, Setup Assistant will ask you to restore the backup.
    You have to restart both iMacs before doing this, so migration will be stopped

  • New I5 Imac, quit Migration Assistant system slow

    Hello All!
    I just bought a new I5 Quad Core Imac.  I was using Migration Assistant to transfer the files and data from my Core Duo Imac.  About 2 hours into it I noticed the Duo went to sleep adn I had to quit teh Migration.  I decided to reboot the new Imac and do everything on my own.  The mac works, but it is very slow on may tasks.  For example, my Itunes library is on an external HD and when I play a song it stops and pauses periodically.  There is also frequent messages when I move files saying I dont have permission.  I even think my WiFi is slow.  I used Disk Utility to reset the permissions and it says some of them cannot be repaired.
    Please help.

    I see, well in your haste I'm guessing you goofed up your OS some how. My recommendation is if you have all your critical data backed up on an EHD that you start over. In this case I would recommend doing a reformat and re--install of OS X and iLife, then move the data you want from the EHD to the internal HD. How you would do that is:
    Insert the OS X Install disc that came with the computer and restart holding down the Option Key. Then choose the Install Disc to boot from. Next choose the language then choose the Utilities menu and open Disk Utility. Once in Disk Utility select the internal HD on the left pane and click the Erase tab. Then ensure Format is set to Mac OS Extended (Journaled) and then click Erase. This will wipe the internal HD totally clean. Once that has been done (takes about a minute) exit Disk Utility and continue with the Install of OS X. Once OS X has been re-installed use the iLife Install Disc and reinstall iLife. Once iLife has been installed then run Software Update and let the system download and the updates for your system. Once you have all of that done then you can begin moving the information you want from the EHD to the Internal HD.

  • HT3231 Migration assistant is slow

    Why is this process so agonizingly slow!  I am trying to migrate data from a 3.06 Ghz iMac Core 2 Duo with 4GB RAM to a brand new MacBook Pro i7 quad-core with 8GB through a direct connect ethernet at gigabit speed.  It is taking forever!

    Just go ahead and quit the migration - force quit if you must. You're not likely to damage anything. It's best, if you can, to have the two Macs physically connected, even if it's just to the same router with Ethernet cables. Or using FireWire and Target Disk Mode. Once you have both Macs connected via Ethernet or FireWire, try Migration Assistant again. It's been a while since I last used MA, but I know that it didn't take more than 2 hours to completely move about 100GB from my PowerBook G4 to my 'new' (at the time) MacBook Pro.
    Good luck,
    Clinton

  • Mailbox migration is very slow

    Hi,
    Migration of mailbox from Exchange on premises to Exchange online is very slow, 1 GB mailbox took around 5 hours.
    Appreciate your quick response regarding same.
    Regards,
    Hakim. B
    Hakim.B Sr.System Administrator

    It depends on many factors, there's a long guide here:
    http://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
    If you have 30 minutes to spend, I also recommend watching the module 3 video from the Office 365 Performance Management course on MVA:
    http://www.microsoftvirtualacademy.com/training-courses/office-365-performance-management

  • Migration assistant really slow

    I also decided to use migration assistat to transfer files from my MacBook with tiger to my new
    MacBook with snow leopard. I had no cables so am doing it wirelessly. It has been going for about 10 hours and also seems stuck however mine is giving me no indication of time remaining. Just the status bar that hasn't moved for awhile. I would love to cancel it and just transfer the files using my external hard drive. Not sure if I did something wrong or if it just that slow. I can't be without a computer for numerous days.

    I used Migration Assistant to populate my data onto a new iMac being restored from a Time Capsule. I think it was about 250 GB. The restore was performed over ethernet (not wireless) but I should point out that it's true gigabit ethernet (1000 BaseT).
    The restore took almost exactly 3 hours.
    I should probably point out some math before you jump to conclusions. Regardless of network or bus speed, it's not possible to copy data faster than the maximum read or write speed of the hard drives. Most hard drives are going to have a maximum sustained transfer rate of maybe 45-50 MB/sec (some may advertise around 80 MB/sec this assumes completely contiguous data. Throw some randomized head-seek time in there and that will quickly degrade to about half of the max theoretical speed.
    If you divide 250 GB by 40 MB/sec, the transfer works out to about 1hr 45mins. My transfer really did take 3 hours which works out to an effective transfer rate of only about 23 MB/sec. I suspect this is probably due to overhead of all the traversal required to reconstruct the data from the Time Machine backup format.
    If you were to do the same transfer over 100 BaseT (100 Mbps ethernet) then the network would become the new bottleneck and it would not be possible to get a transfer faster than 10 MB/sec (and more likely 9). This would have turned a 3 hour transfer into a about 7h 40mins.
    But you're not even using 100 BaseT ethernet... you're doing wireless. If it's wireless G then the max theoretical speed is 54Mbps (5.4 MB/sec) BUT... it's half-duplex. You'd be lucky to get 4 MB/sec. At that speed a 250 GB transfer would take about 17 hr 20 mins.
    With that in mind... you said you've been waiting 3 days? Your transfer is hung. I helped a relative do the same thing several months ago, but after telling him what he needed to do he ended up trying to do the transfer over wireless. The sustained traffic load on his sub $50 wireless router ended up crashing the router and he was making no progress at all. The router had to be rebooted NUMEROUS times before he ultimately gave up, finally put the two machines in the same room so he could directly connect them and do the transfer via wired method. Over wire the transfer didn't take long at all (maybe 30 mins. But he didn't have much data.)

  • Migration Assistant Sooooo Slow

    I'm using migration assistant to transfer files from a Mac Book Pro with a 1/2 TB hard disk to a new iMac.  I'm doing this via WiFi because that was the only option offered me by migration assistant.  After running for 23 hours, it's barely 1/4 done.  Is there anything I can do to speed ths up?
    - Dan

    There is an adapter that has a FW800 on one end and a FW400 on the other, then you use a FW400 cable. I have one with my MacMini, but I can't remember whether it came with it or whether I bought it at the same time knowing that I had a FW400 iSight camera and a FW400 Epson scanner.
    http://store.apple.com/us/product/TW748LL/A?fnode=MTY1NDA3Ng
    This would be better if you don't have a FW400 cable: http://store.apple.com/us/product/H7041ZM/A?n=firewire&fnode=MTY1NDA3Ng&s=topSel lers
    P.S., if your MacBook Pro has an Ethernet port, you colud also use an Ethernet connection between the two. It would also be better than WiFi.

  • Should Migration Assistant be this slow?

    Hey gang-
    Just got a brand new late-2013 iMac to replace my mid-2007 iMac.
    Migration Assistant is currently in progress, but I'm amazed at how slow it is going.   It started about 30 minutes ago and is showing 36 hours 45 minutes remaining!   The source computer is a mid-2007 iMac and the new machine is a 27" late-2013 iMac Core i7.   The drive on the old iMac is 650 GB capacity with about 600 GB data total.   The new iMac has the 3TB fusion drive.
    The 2007 iMac is in Target Disk mode and connected via its Firewire 800 port to the new iMac's Thunderbolt port using an Apple Thunderbolt to Firewire adapter.
    I've done many such migrations over the years and never seen one this slow.   Any thoughts?
    Thanks!
    Dave

    Thanks everyone!
    As it turned out, the Migration actually took just over 6 hours.   For the first two hours, the 35+ hour estimate persisted.   Then suddenly it changed to about 3 hours.   Then back to 30+ hours!   Finally the estimate seemed to fall in line with the progress bar for about the last hour.   Not too bad I suppose for about 600GB of data and the move from Lion to Mavericks.
    All in all the migration seems to have worked very well.  I guess the bottom line is don't be too concerned by the time counter unless the progress bar seems stalled for a long time as well.
    Thanks again!
    Dave

  • MacBook Pro i7 running incredibly slow - could it be Migration Assistant?

    My new MacBook Pro i7 is running super slow - generally, everything is slow to open, it hangs, t stalls and crashes completely - I thought this could be something to do with Migration Assistant, any ideas?
    I used Migration Assistant to copy the user account, docs and apps from my Mac Pro. It's fantastic, the Migration Assistant, in that in copies everything and sets you up to hit the ground running - but this brand new laptop is seriously lagging behind.
    The only problem with my theory is that my Mac Pro isn't slow and as it is, although a lower spec than the MBP, the Mac Pro is faster - so what could Migration Assistant have copied across that makes it run slower?

    Alternatively, boot the MBP with the shipped install disc, reinstall the software, and then use the setup assistant to migrate your stuff from the MP. See Best Practices for details.

  • Time machine backup is very slow after migration to Mountain Lion

    After I migrated to mountain lion, Time machine backup is very slow. Time machine preference says there is no previous back up although I had Time machine on before migration. It did not help verymuch to connect an ethernet cable between my timecapsule and my Macbook Pro
    Here are the screenshots I see:
    Should I erase the previous backup made on Lion before backing up on Mountain lion? in this case how do I transfer the Lion backup file on another disk just in case something goes wrong before I have a good backup under Mountain Lion? just like any other file?

    After further reading on the forum, the problem was solved: I used the possibility to back up on a second disk (in the preferences Time Machine choose a disk and save on both disks) to make a back up on another usb disk, and then erased the old .sparsebundle file on my Time Capsule. I have then re defined time capsule as the back up disk and then the backup was muuuuuch faster (one night instead of less than 1 giga after 3 days.....)

  • SCVMM live migrations very slow

    I'm running Hyper V with SCVMM 2012 in my test environment. 2 hosts connected to a MD1200 and set up in a cluster. Everything works perfectly, except that live migrations take a super long time. By this I mean that when I start the Migration Wizard it takes up to 5 minutes to rate the hosts, and then when it finally completes and I start the migration, it can take up to another 5 minutes to complete the move.In my production clusters this doesn't work this way, there the Migration Wizard takes seconds to rate the hosts and usually less than a minute to move the VM.The only major difference between my test environment and my production environment is that test is using direct SAS connections to the SAN, where in prod everything runs through switches. In prod one cluster is all 1gig and one cluster is 10gig and both are about the same...
    This topic first appeared in the Spiceworks Community

    Hey guys,
    I have searched online and in MS forums, and cannot resolve my issue.
    I have checked through similar articles, without any resolution.
    Migrating
    Mailbox From Exchange 2007 to  Exchange 2010: Very Slow                        
    Exchange 2013 Mailbox Migration Rate/Speed ?                        
    Public Folders after migration
    to Exchange 2013 are extremly slow                        
    Exchange 2010 mailbox move to Exchange 2013                        
    Single Mailbox Very Slow after 2003
    to 2010 Migration
    I have also come across the most common solution which is written here
    http://support.microsoft.com/kb/2807668, however this is not my problem.
    My problem is that mailbox migrations are SLOW, I'm talking about < 15MB per minute.  I do NOT have any contentIndex errors on any of my databases, they are all healthy and stay healthy throughout the migrations.  Both Exchange 2010 and 2013
    are DAGs.
    When I 'view details' from the ECP migrations page, I see things like 'Stalled duration
    00:53:21 ', however like I said there is no errors, and nothing mentioned in the user report.
    Get-ClientAccessServer | Test-MRSHealth this checks out fine, no problems.
    I have disabled offloading on all of the NICs.
    Is there anything else I can do or monitor to find out why its so slow?
    Could it be because of DAG even though there are no errors and the state is healthy.  Would an idea be to take down the dag during migration then add that after all is done?
    Andrew Huddleston | Hillsong Church | Sydney

  • Migration Assistant stops at very end

    I just bought an iMac and have tried both with TimeMachine backup and direct Firewire Connection to my G4 PowerMac to use Migration Assistant - both times I end up with the following message at the VERY end while the message states something about transfering support applications:
    "There Might Be A Problem With Your Network
    The other MAC (or Time Machine) is not responding. Make sure that all of your network devices are connected and turned on. Also, make sure that your ethernet cables are still connected properly to your computer and to the network, or if using Airport, that the base station is in range and turned on."
    The first time I canceled migration and had to set up a user account and everything - my old MAC stuff was there, but I was not my original user like I wanted to be.
    Any ideas?

    if your home directory migrated that's all you need to worry about. set up the new user as it prompts you to and then check system preferences->accounts. if your old user is listed there it migrated successfully. try logging in as the migrated user. if it works, delete the temp user you've had to set up. If your migrated user is not listed in account preferences, create it using the same exact short user name as you had before. you'll get a popup saying that a home directory by that name already exists. say "yes".

  • "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.

  • Very slow performance, need assistance

    I have a program that has very slow performance (and I mean SLOW).  I was hoping somebody could tell me how to improve the performance.  I know where it hangs up (at LOOP AT it_detail INTO wa_detail.) but I'm not sure what I need to do to make it quicker.  Any help would be appreciated.
    TABLES: vbak,
            vbpa,
            adrc.
    TYPES: BEGIN OF ty_detail,
             vbeln TYPE vbak-vbeln,
             erdat TYPE vbak-erdat,
             vdatu TYPE vbak-vdatu,
             adrnr TYPE vbpa-adrnr,
             sa_name TYPE adrc-name1,
             sa_street TYPE adrc-street,
             sa_city TYPE adrc-city1,
             sa_state TYPE adrc-region,
             sa_zip TYPE adrc-post_code1,
             sa_tel TYPE adrc-tel_number,
             kunnr TYPE vbpa-kunnr,
             ag_name TYPE kna1-name1,
             ag_street TYPE kna1-stras,
             ag_city TYPE kna1-ort01,
             ag_state TYPE kna1-regio,
             ag_zip TYPE kna1-pstlz,
             ag_tel TYPE kna1-telf1,
             vkbur TYPE knvv-vkbur,
             we_num TYPE likp-kunnr,
             we_name TYPE kna1-name1,
             we_name2 TYPE kna1-name2,
             we_street TYPE kna1-stras,
             we_city TYPE kna1-ort01,
             we_state TYPE kna1-regio,
             we_zip TYPE kna1-pstlz,
             we_tel TYPE kna1-telf1,
           END OF ty_detail.
    DATA: it_detail TYPE TABLE OF ty_detail WITH KEY vbeln adrnr kunnr we_num,
          wa_detail LIKE LINE OF it_detail.
    DATA: addressnum TYPE vbpa-adrnr,
          temp_kunnr TYPE likp-kunnr.
    * S E L E C T I O N - S C R E E N
    SELECTION-SCREEN BEGIN OF BLOCK required WITH FRAME TITLE text-002.
    SELECT-OPTIONS:  s_vdatu FOR vbak-vdatu OBLIGATORY.    "Req delivery date
    SELECTION-SCREEN END OF BLOCK required.
    SELECTION-SCREEN BEGIN OF BLOCK temp WITH FRAME TITLE text-001.
    SELECT-OPTIONS:  s_auart FOR vbak-auart OBLIGATORY.
    PARAMETER:  p_parfun TYPE vbpa-parvw DEFAULT 'Z5' OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK temp.
    *INITIALIZATION.
    *  REFRESH s_auart.
    *  CLEAR s_auart.
    *  s_auart-sign = 'I'.
    *  s_auart-option = 'EQ'.
    *  s_auart-low = 'OR'.
    *  APPEND s_auart.
    *  s_auart-low = 'ZDT'.
    *  APPEND s_auart.
    * END OF SELECTION SCREEN
    * M A I N - B O D Y
    *Main select statement.
    SELECT a~vbeln a~erdat a~vdatu c~adrnr c~kunnr
        INTO CORRESPONDING FIELDS OF TABLE it_detail
        FROM vbak AS a
          INNER JOIN vbap AS b
              ON b~vbeln = a~vbeln
          INNER JOIN vbpa AS c
              ON c~vbeln = b~vbeln
    *          AND c~posnr = b~posnr
                   WHERE a~auart IN s_auart
                   AND a~vdatu IN s_vdatu
                   AND c~parvw = p_parfun.
    LOOP AT it_detail INTO wa_detail.
      SELECT SINGLE name1 street city1 region post_code1 tel_number
          FROM adrc INTO (wa_detail-sa_name, wa_detail-sa_street, wa_detail-sa_city, wa_detail-sa_state,
                            wa_detail-sa_zip, wa_detail-sa_tel)
          WHERE addrnumber = wa_detail-adrnr.
      SELECT SINGLE name1 stras ort01 regio pstlz telf1
          FROM kna1 INTO (wa_detail-ag_name, wa_detail-ag_street, wa_detail-ag_city, wa_detail-ag_state,
                            wa_detail-ag_zip, wa_detail-ag_tel)
          WHERE kunnr = wa_detail-kunnr.
      SELECT SINGLE c~kunnr INTO temp_kunnr
          FROM vbpa AS a
              INNER JOIN lips AS b
                ON b~vgbel = a~vbeln
              INNER JOIN likp AS c
                ON c~vbeln = b~vbeln
                WHERE a~vbeln = wa_detail-vbeln.
      wa_detail-we_num = temp_kunnr.
      SELECT SINGLE name1 name2 stras ort01 regio pstlz telf1
          FROM kna1 INTO (wa_detail-we_name, wa_detail-we_name2, wa_detail-we_street, wa_detail-we_city, wa_detail-we_state,
                            wa_detail-we_zip, wa_detail-we_tel)
          WHERE kunnr = wa_detail-we_num.
      SELECT SINGLE vkbur FROM knvv INTO wa_detail-vkbur
          WHERE kunnr = wa_detail-kunnr.
      MODIFY it_detail FROM wa_detail.
    ENDLOOP.
    PERFORM display.
    INCLUDE zpartner_displayf01.
    Regards,
    Davis

    Hi Davis,
      The culprit is the select inside the loop.
    YOu should use for all entries instead .
    I will show for one select, you do similar thing for others:
      SELECT addrnumber name1 street city1 region post_code1 tel_number
          FROM adrc INTO table itab_adrc
    for all entries in it_detail
          WHERE addrnumber = it_detail-adrnr.
    sort itab-adrc by addrnumber.
    LOOP AT it_detail INTO wa_detail.
    read table it_adrc with key addrnumber = wa_detail-adrnr.
    if sy-subrc = 0.
    move fiedls of it_adrc into wa_detail.
    endif.
    ENDLOOP.

  • Macbook pro mid-2012 13" has very slow disk access

    Until 3 days ago my macbook pro mid-2012 13" running OX 10.8.3 was running fine. Then, it showed very slow response anytime it had to access the hard disk. After doing the usual checks and disk first aid repairs to no avail, I booted from my external disk with an older copy of my hard disk and everything then worked as normal, except when I accessed the internal hard disk, then it crawled once again (spinning beach ball, took many seconds just to open a finder window and then several minutes to display the contents). I ran the Apple Hardware Tests and it said everything was fine, even though it tooks several minutes before the test would actually start. I also ran the program BlackMagic Speed Disk to find out if the disk was having transfer speed problems and it showed a respectible transfer rate (60MB/s), not great but not like the 0.3MB/s I was getting when I tried to back up the internal disk. I was using Carbon Copy Cloner to try to back up the internal disk but had to give up since at 0.3MB/s, it would take days to back up the 250GB on the disk. I found on the web that using "restore" in Disk Utility, I could do a disk copy without the file by file copy which allowed me to back up my disk in "only" 6 hours. Booting from my newly made copy on an external disk worked fine and ran at nearly normal speed (slightly slower since it was an external disk running through USB2). As a final attempt to prove this was a disk problem, I erased the internal disk and reinstalled OSX 10.8. I am still waiting for this install to finish, it has been 5 hours although the progress bar said it should be done in 20 minutes. This was fairly convincing evidence that it is not a software or settings problem. However, all my web searches could find no other case of a problem like mine. I presume I have a failed hard disk but as all the diagnostic programs say it is working fine, I was hesitating to bring it in without hard diagnostic evidence. If anyone knows what might be the problem, it would be much appreciated to hear from you.       

    It should not take 5 hours to install Mac OS X.  There is something wrong with the disk.  Try reformatting where you do a wipe of the drive (an select the option to write zeros which will remap bad sectors).   Then try to install MAc OS X.
    I got this information from here:
    http://reviews.cnet.com/8301-13727_7-20064489-263.html
    Back up your data.
    Use Time Machine or a system cloning utility to create a full and restorable backup of your data. If you suspect bad blocks, then when cloning you might consider not using a "block-level" copy process, since this will likely run into problems.
    Boot to the utilities DVD.
    If you have a boot DVD for a tool like Drive Genius or another drive utility, then boot to that; if not, use your OS X installation DVD (once you select your language, open Disk Utility from the Utilities menu).
    Format the drive.
    Using your selected utility, format the drive and check for bad blocks. If you are using Disk Utility, click the Erase tab, click the Options button, and then select the option to write zeros to the disk (you do not need to do multipass erase options, as this will provide no additional benefit for managing bad blocks). Writing to zeros may take a couple of hours depending on the size of the drive, but when done the drive will have remapped any blocks that were not reliably read.
    Restore the OS installation.
    If you have used Time Machine to create your backup, boot to your OS X installation DVD (if you are not using Disk Utility) and use the option in the Utilities menu to restore from backup. Attach your Time Machine drive and then proceed with the restoration, selecting the newest backup as the one to restore to your system. If you have used a system cloning tool, then attach the cloned drive and boot off of it (hold the Option key at start-up to select it from the boot menu). When you are booted to the cloned drive, run your cloning utility to copy the installation back to the computer's main boot drive.An optional approach here is to perform a full reinstallation of the OS from your installation DVD, and then migrate your data, applications, and settings from either the clone or the Time Machine backups using Apple's Migration Assistant.

Maybe you are looking for