11 Responses

  1. Paul
    Paul April 8, 2014 at 10:05 | | Reply

    Excellent points made in this post. It’s often not as easy as people make out and can get messy very quickly if something goes wrong.

    Command line is powerful, but not everybody will feel comfortable rolling up their sleeves and diving into the terminal.

    Liz – not sure what happened for you there. I’ve migrated plenty of Genesis sites and not had that issue before. Hope you got it sorted ok.

  2. Liz
    Liz April 8, 2014 at 07:46 | | Reply

    I just lost widgets and their content, plugins and more on a recent site migration from a /url test to the full url (different url names though).

    I read a whole ton of posts on the issues and had hoped to avoid them, but I still lost content. Thank goodness it was a small site, with site-wide widgets not page by page. All the same, I’ll devour this post and checklist to ensure it won’t happen again.

    I was on Siteground hosting and using Genesis framework + theme. I am sure that the Genesis thing caused some issues. Has anyone else found Genesis widgets disappear on migration? I did the config and .htaccess all correct, so can’t fathom out why I lost widget content and all my plugin activation.

    1. Hristo Pandjarov
      Hristo Pandjarov April 12, 2014 at 01:09 | | Reply

      Probable there were options stored in the database relying on the previouse URL (/test). In such cases It’s a good idea to run a search for the old URL in your entire database, just to be sure that there are no links or options that are still using the old URL. If you’re still having issues, I can take a look into the site too, just tweet me @pandjarov and I’ll send you my email 🙂

    2. Ross McKay
      Ross McKay April 16, 2014 at 06:12 | | Reply

      Liz, you lost a bunch of data because of differences in the lengths of strings that were serialised and stored in WordPress options. When that happens, doing a search / replace on the .sql file breaks the serialised data because the string lengths really matter. e.g. “http://example.com/test” is 23 characters, “http://example.com” is 18 characters. PHP serialises arrays of string with the string length, and just throws that data away when the lengths don’t match.

      Best off using a tool that understands this, e.g. WP Migrate DB.

  3. Hiral Patel
    Hiral Patel April 8, 2014 at 11:37 | | Reply

    I’ve been using xcloner for years now with great success and identical Duplication

  4. Dmytro Lazarchuk
    Dmytro Lazarchuk April 10, 2014 at 04:54 | | Reply

    I think this article and service could be useful for WP migration.
    https://wpmayor.com/joomla-to-wordpress-website-migration/

  5. Craig Cameron
    Craig Cameron April 14, 2014 at 12:32 | | Reply

    I’ve tried using Xcloner and the transfer works fine – but I get a Cannot connect to database error – even after editing the wp-config.php file. I gather this is a common problem but have yet to find a solution. Any thoughts?

  6. Sylvain
    Sylvain September 2, 2014 at 17:07 | | Reply

    Hi, I just found this article because I’m having a strange issue trying to export my local site to Siteground using Xcloner or Duplicator. All the steps go fine and give no error, but when I try my live installation, no users, no post, pages and medias are there. I’d be really grateful if someone could give me some kind of solution to resolve this.

    Thank you very much

  7. Craig Cameron
    Craig Cameron August 17, 2015 at 01:06 | | Reply

    These days I use all-on-one-wp-migration, it does everything simply and works!

  8. Richard Lloyd
    Richard Lloyd August 17, 2015 at 01:00 | | Reply

    I *hate* that WordPress stores absolute URLs all over the database – surely there should be one master URL (and is that even needed – the home URL should surely be constructed from PHP env vars?) and the rest should be relative URLs.

    If I have to move a site (e.g. dev to UAT to live) or even just convert it to SSL (http to https), all the URLs have to be search and replaced and – as people have said – it’s *not* a simple text string replacement of an SQL dump either – arrgh!

    I now use WP-CLI:

    cd
    wp search-replace old_url new_url

    It’s *very* fast, even if there’s 10,000’s of URLs to replace (which can happen, believe you me).

  9. Bibin Xavier
    Bibin Xavier April 2, 2018 at 03:24 | | Reply

    Good suggestions. I would like to add a few things.
    before taking a decision on whether someone should use wordpress
    plugins or doing migration manually, you have to know the pros and cons of using plugins for wordpress migration.
    1. First and Foremost, Security!
    According to the statistics of CMS users among the World Wide Web, WordPress is being used by 38% of the website owners. Before feeling proud that you are one among them, know that Hackers and Spammers usually target WordPress websites making your site more vulnerable to security hacks & malicious attacks. There are hundreds of plugins configured by Hackers who intend to steal your login information and much more.
    2. Incomplete and inconsistent data transfer
    Issues that arise as a result of a faulty migration can lose your money and
    time. For example, when your site goes disconnected, you lose deals. It
    can hurt your business badly. While you might think that using plugins as a migration tool will improve efficiency by reducing the time, know the fact that most of these migration tool plugins are designed to do the basic transfer of files, which transfer only the files from your document root and not from other folders. For some website owners, they use their emails for many purposes and these emails may contain valuable data which are also required to be transferred along with the website files.
    To know more, read https://www.supportsages.com/not-use-plugins-wordpress-migration/
    Choose a wise decision!

Leave a Reply