WordPress Move

WordPress Move, a migration assistant for WordPress, was my project for Google Summer of Code 2011. You can read my proposal for this project here. As you may notice, some of the things I mentioned in this proposal didn’t make it to the final release either because they were unnecessary or not the best way to do it.

If you wish, you can read the weekly updates I posted on WordPress Summer of Code 2011 blog for more information about the plugin’s development process:

You can download WordPress Move from WordPress Plugin Directory or fork/watch it on GitHub. Online documentation is also available.


17 thoughts on “WordPress Move

  1. Marios says:

    i have changed the domain before starting migration or making backup, now whatever i click on my old domain redirects to the new and i can not do anything, how can i revert the domain change back ??? SOS

  2. texxs says:

    I thought that this was such a common task that I would see a greater demand for this plug-in. I haven’t used it yet. I’m about to for the first time.

  3. Dave says:

    Mark –

    I have the same issue as Marios. I reset the nameservers on the new domain back to current host and going to the old domain still redirects. Can’t wait to see how this works!

    • Visiting the old domain *should* redirect if you have successfully completed Change Domain Name procedure and both of your domains point to your current host 😉 You can now drop your old domain and use the new one.

      • Dave says:

        The problem is I did the domain change first. So now I can’t get into the old domain to start the migration on that side.

      • Then you should point your new domain to your current host temporarily to start the migration and then point it back to your new host to complete the migration.

        WordPress Move 1.1 supports migrating and changing the domain name at the same time which is what you should have used actually.

  4. Dave says:

    As I said in my first post I have tried that but I will give it a shot again. Any other ideas? once pointed back to my old host it still redirects. Thanks

    • I guess you are talking about gacarlsons.com and myfurnitureplace.net, right? If so, from what it seems, the situation is:

      gacarlsons.com is pointing to Host A
      myfurnitureplace.net is pointing to Host B

      However, since you used Change Domain Name mode of WordPress Move, every single reference to gacarlsons.com on Host A has been replaced with myfurnitureplace.net. Following links on gacarlsons.com does not work because myfurnitureplace.net is pointing to another host with an empty WordPress installation therefore it does not have pages you are requesting.

      If you want to run myfurnitureplace.net on Host A:

      – Point myfurnitureplace.net to Host A.

      If you want to run myfurnitureplace.net on Host B:

      – Point myfurnitureplace.net to Host A.
      – Use one of the migration methods to migrate from Host A to Host B.
      – Point myfurnitureplace.net to Host B.

      I hope it’s more clear now 🙂

      • Dave says:

        I have tried that three times now with no luck. I have pointed furnitureplace back to Host A and cannot get back into gacarlsons.com to start the migration. I will give this a shot on another domain I need to transfer since I now know not to change the domain first! Thanks for your assistance.

    • After pointing myfurnitureplace.net to Host A, you should go to myfurnitureplace.net/wp-admin/ to start the migration, not gacarlsons.com.

  5. michael says:

    i have also changed the domain name. im using webmatirx which points to a localhost:portnumber and i changed the domain to point to the http:ipadress of server on internet. now when i load the localhostwp instance i get redirected to the web address. i restored the wordpress files and its still happening. can you tell me where to change the details so that my development site (localhost displays the local data). i cannot point to the old domain on the new host because it references a localhost port on my development laptop. so many people on your site have had the same issue it not clear on your plugin as to when to change the domain name.

    • I think it is pretty clear that changing the domain name means “replacing instances of your old domain in the database with the new one” as it is mentioned in both Migration Assistant and Change Domain Name pages. Also on these pages, it is mentioned that you need to configure your domain name and your host to make it work on your current host, after completing the domain name changing procedure. If you need to change the server your WordPress installation operates on, you need to use either Simple or Advanced Migration. If you are on a host that is capable of handling domain names pointed to it, you just need to use Change Domain Name and configure your domain name and server afterwards.

      In your case, since you are using a direct IP address and not a domain name, your WordPress installation actually needs to be on that server. So you need to transfer your database and files to the new server.

  6. Samwhites7 says:

    Unfortunately I am getting an error:
    “Plugin could not be activated because it triggered a fatal error.”

    I am using v.1.1.1 and it’s pretty much a vanilla site created using: http://www.instantwp.com/
    My plan is to develop sites on my USB drive (via and then use the plugin to upload to my domain…if you like creating local development sites and live domain-hosted sites so you plugin would be ideal!

    Any ideas how to resolve the error?

    • I’m so sorry for late approval, I just saw your comment.

      Could you please turn WP_DEBUG on in wp-config.php and send me the full error message?

      By the way, I’m also using a setup like the one you’re building. Really nice idea to turn it into a project 🙂

  7. whites7 says:


    am no expert but changed WP_DEBUG to true and get:

    Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in E:\Wordpress\iwpserver\htdocs\wordpress\wp-includes\functions.php on line 3466

    Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in E:\Wordpress\iwpserver\htdocs\wordpress\wp-includes\functions.php on line 3466

    Warning: Cannot modify header information – headers already sent by (output started at E:\Wordpress\iwpserver\htdocs\wordpress\wp-includes\functions.php:3466) in E:\Wordpress\iwpserver\htdocs\wordpress\wp-includes\pluggable.php on line 934

    FYI and using the default theme Twenty Ten 1.2



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: