Support » Plugin: SiteGround Migrator » Siteground migrator stuck

  • Resolved rwhitmire

    (@rwhitmire)


    We have been trying to migrate a website and the migrator has been running for over two days now with just this on the screen:

    Website Migration in Progress

    Transfer started. Creating archives of files…

    Help?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter rwhitmire

    (@rwhitmire)

    it’s still showing the same thing. it has been 4 days now.

    epha

    (@epha)

    I ended up using chat on the Siteground website to talk to them directly. The rep placed me on a few minutes’ hold. Then he came back and said that my site had transferred. He gave me a sketchy-looking link (which was legitimate) to check that my site had transferred. Because the migrator plugin didn’t completely work, not all of my pictures were showing. He also instructed me to do a find and replace by going to Site Tools>WordPress>Search to replace https://i1.wp.com with my domain name. After that, everything looks good.

    The exact way I explained my problem in chat was:

    I have tried twice to migrate my site to SiteGround using the Siteground Migrator.  Both times the Siteground Migrator gets stuck at "Downloaded 603 out of 4465 files..." The last entry in the Siteground migrator log is: [26-Apr-2021 19:53:56 UTC] INFO: Transfer request has been sent to SiteGround server.  
    
    I see at least some files were transferred. There are multiple people posting about this issue on https://wordpress.org/support/plugin/siteground-migrator/. But a Siteground rep did not respond to my question there.  My website is relatively small and is not a multisite. I increased my PHP memory limit to 128M. Still sticks at 603 files downloaded.
    Thread Starter rwhitmire

    (@rwhitmire)

    Thank you so much, I will give that a shot!

    Plugin Author Stoyan Georgiev

    (@stoyangeorgiev)

    Hey there @rwhitmire,

    Make sure that you are using a valid migration token and check to see if it has not expired. If that is the case, generate a new migration token and start the migration again with the new token.

    Make sure you are copying it as it is and without any spaces or other characters.

    If the issue still persists, feel free to reach back to us.

    Kind regards,
    Stoyan

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.