Home > Just the Video Tutorials, Move WP > How to Move WordPress to a Different Server and Web Address

How to Move WordPress to a Different Server and Web Address

January 4th, 2009 Leave a comment Go to comments

How to Move Your WordPress Blog to a Different Server and Web Address — Part 1 of 2

How to Move Your WordPress Blog to a Different Server and Web Address — Part 2 of 2

Get Noticed with a $7.99 .CO!
  1. January 4th, 2012 at 04:00 | #1

    Be carefull when moving site and using dropbox (when moving from one computer to another). For me it costed 5 hours until I find out that dropbox was not finished to copy all the files, and I was alreadyt then copying to htdocs directory and of course with not all files and then very frustrated that I cannot find why site does not work after moving.

  2. Daniel S.
    February 28th, 2012 at 11:45 | #2

    Thanks so much for the tutorial! It seems like the wordpress codex is written by and for people with mild autism. I guess I needed to be guided by the hand!

  3. March 6th, 2012 at 14:25 | #3

    Thank you again for sharing your knowledge in a complete step-by-step way. I return here everytime I run into a wordpress glitch. A new question related to this tutorial, “How to Move WordPress to a Different Server and Web Address”: I have been using your method (updated to preserve the plugins now that the databases are serialized — thanks hugely on that!) when I move a site from development to make it live.

    When I create a site for a client, I usually put up a nice temporary home page (or leave the old site up when making a new one) while I develop the new site in a subdirectory. This was a great technique when I was coding html and php. With WordPress, it’s a bit more complex, partly because often I cannot just develop the site using MAMP on my harddrive, because the client needs access to add content. So, seems I have 2 choices when it’s time to go live:

    Create a redirect to the subdirectory, which then makes the site appear to be in the root, but makes other things more complex, like creating and linking to subdirectories to hold large tif files for media access, for example.

    What I usually do is follow your instructions above, moving the site to the root and also removing all the old htm and php and image files associated with the old site.

    My question today is: would there be a better practice for this, a more elegant solution, such as changing something simple with the htaccess file, or using the natural heirarchy (priority load order) of the default files, so that I could develop the hidden wordpress site in the root directory, while the temporary or old site still shows to the public? (e.g., what could I name the .htm or .php file that I want public and still have the home.php or index.php file that WP shows working and a blink URL for me and the client while developing?

    Then, making it live would be more staightforward. Possible? Thank you.

  4. March 6th, 2012 at 19:08 | #4

    @LynnW: I’m glad you have found the videos useful. As to your question about leaving the old site in root while you develop WP in root also, I’m not sure of a “clean” way of doing that. If old site consisted of simply an homepage and few other pages, then it may not present such a problem, but it could get real cluttered and confusing if you had a lot of files/directories in the old site intermingled with your WP source code. Typically, what I do is create WP in a subdirectory and when it’s time to move, just create an empty folder in root called something like OLD_BACKUP to drag all the old files into…doesn’t take a great deal of time to just drag them in there. Then follow the process of moving all WP files out to root and changing the urls like I demo in the video. It is a few more steps than what you are looking for, but I’m not sure there is a cleaner way to do it.

  5. March 6th, 2012 at 19:26 | #5

    @figaro
    Yes, we do similar things to develop then make the site live. I was just thinking about the priority load order of default files, and thought perhaps there was a way to use that, say, for example, if welcome.htm (temp page or small old site) would load before index.php (from WP), then we could develop in the same directory and not have to deal with the hassle of steps when finally making the new WP site live… thanks for your response.

  6. May 18th, 2012 at 16:05 | #6

    Thanks a lot for this tutorial, very clear and easy to follow.

  7. May 29th, 2012 at 14:13 | #7

    My old wp site host does not have cPanel but the new one does. I am not changing the wp domain name for my blog. Can you outline the differences please?

  8. babychai
    June 30th, 2012 at 07:52 | #8

    do you have tutorial for change to new domain but still using the same host?

    Thanks.

  9. June 30th, 2012 at 07:54 | #9

    Just do everything you see in this video except for the actually moving part.

  10. October 22nd, 2012 at 04:46 | #10

    Is there another tool to use instead of cPanel? I didn’t want to purchase for one time use…

  11. S-Mac
    March 13th, 2013 at 12:47 | #11

    Thankyou for the great tutorial. Looked everywhere for something to explain this transfer. Just one question if anyone can help. I noticed when editing the database you changed all the URLs from the old to new but never changed the name of the database from the old to the new. Should I change this or do you just leave the old database name in the SQL file?

  12. March 16th, 2013 at 11:08 | #12

    No need to change the name of the database as long as you have it entered correctly in the config file.

  13. Jake More
    July 29th, 2013 at 23:47 | #13

    Thank you for this tutorial.
    It was very helpful.

    I was moving a premium theme over, and I noticed that everything moved over, except for the specific theme options.
    I had to go in and manually recreate the specific options.
    I wonder where those settings live so that I would not have to manually recreate them.
    Any ideas?

    thanks again,
    Jake

  14. August 29th, 2013 at 14:53 | #14

    @figaro

    This is a great tutorial for working on a PC. I am wondering how different the steps might be when working on a MAC. I am finished building the Web site and am now ready to publish it, but I don’t want to continue using my computer as the server/host and would much rather have wordpress (which is what I am working with) host the site. Any ideas on doing this will be greatly appreciated!

    Best,
    David

  15. September 15th, 2013 at 14:09 | #15

    Wow! The difficult made simple with step by step explanations and nothing taken for granted. Thank you so much.

Comment pages
1 2 3 50
  1. January 20th, 2009 at 14:43 | #1
  2. May 9th, 2009 at 16:08 | #2
  3. May 2nd, 2012 at 08:12 | #3
  4. May 19th, 2013 at 14:40 | #4
  5. August 6th, 2013 at 16:24 | #5
  6. November 14th, 2013 at 23:08 | #6
*