I have seen many requests online on how to<\/a> move a WordPress<\/a> blog to a new server or host- including requests from some of my readers.<\/p>\n While there are other tutorials available online, many seem to lack clear instructions on how to<\/a> move your blog. In this tutorial, I\u2019m going to take you step-by-step and show you exactly how to<\/a> move your WordPress<\/a> blog to a new server or host. <\/p>\n So, are you ready? Here we go:<\/strong><\/p>\n Open either your FTP program or your file manager through your hosting company and browse to your home or public_html directory. With WordPress<\/a> installed, it should look something like this:<\/p>\n You want to download all the files and folders to a convenient location on your computer, then upload all the files and folders to your new server\/host.<\/p>\n Once you have all the files on your new server\/host, you need to download a copy of your original WordPress database from your original host.<\/p>\n (All of the following screenshots were taken from cPanel, but if your host uses a different administration panel, the steps will be the same- they may just look slightly different.)<\/p>\n Once logged in to your administration panel, go to phpMyAdmin.<\/p>\n Once you click phpMyAdmin, in the left column click on the database that is used for your original WordPress blog.<\/p>\n You should now see the name of the WordPress database in the drop-down box and all the WordPress tables listed underneath. The tables you have can be different than mine because the WordPress plug-ins you use will determine what tables you have in your blog\u2019s database.<\/p>\n Regardless, it should look something like this:<\/p>\n Now in the main window, click the tab at the top of the screen that says \u201cExport\u201d. In the \u201cExport\u201d box, all of your WordPress database tables should be highlighted.<\/p>\n Underneath that, check the box that says \u201cSave as file\u201d and name it whatever you want, then click \u201cGo\u201d to download your blog\u2019s database.<\/p>\n Click the \u201cSave\u201d button to save a copy of your WordPress database to a convenient location on your computer.<\/p>\n Congratulations!<\/strong> Now you\u2019re done with your old server\/host! It\u2019s time to move on to the new server\/host.<\/p>\n Login to your new server\/host\u2019s control panel. The first step is to create a new database that will be used for your new WordPress Blog.<\/p>\n Click on \u201cMySQL Databases\u201d.<\/p>\n Under \u201cCreate New Database\u201d, enter a name for your new WordPress database, then click the \u201cCreate Database\u201d button.<\/p>\n Now that your new WordPress database has been created, we need to make a new user for that database. Usually on the same screen you\u2019re at, you have the option to create a new user.<\/p>\n Enter a name and password for the WordPress database user and click the \u201cCreate User\u201d button.<\/p>\n Now you have to give that user permission to use your blog\u2019s database. Again, usually on the same screen you will have the option to add that user to the database. Select your WordPress database and the user you just created, then click the \u201cAdd\u201d button.<\/p>\n On the next screen, you have the option to grant which permissions this user has to your blog\u2019s database. Be sure to grant this user total access to the WordPress database by checking \u201cAll Privileges\u201d, then click the \u201cMake Changes\u201d button.<\/p>\n You should get a confirmation telling you that the user has been successfully added to the database.<\/p>\n Now that your new database has been created, we need to import your old WordPress blog\u2019s database contents into your new database.<\/p>\n Back in the main window of your control panel, click on \u201cphpMyAdmin\u201d.<\/p>\n In the drop-down box in the left column, select your new WordPress database that you\u2019ve just created. It should say that there are no tables in the database yet, since it\u2019s a blank database that you\u2019ve just created.<\/p>\n In the main window, click the \u201cImport\u201d tab. Under \u201cFile To Import\u201d, click the \u201cBrowse\u201d button and select the .sql file that you downloaded from your old WordPress database, then click the \u201cGo\u201d button.<\/p>\n After waiting for the entire blog\u2019s database to import, you should get a confirmation telling you that the tables have been successfully imported. Again, the number of queries that were executed may be different than mine, depending on which plug-ins you have installed.<\/p>\n Now in the left column, you should be able to see all the WordPress tables that were just imported.<\/p>\n If your new WordPress blog is using a different domain name than the original, we need to modify three values, and they are all located in the \u201coptions\u201d table.<\/p>\n Even if you are using the same domain name, there is one option you may have to change. I would recommend you continue to follow along, even if your new WordPress blog is using the same domain name as the original blog.<\/p>\n All of the changes we need to make are located in the options table. My options table is named \u201cwp1_options\u201d, but yours may be a little different (probably \u201cwp_options\u201d), just as long as the suffix is \u201coptions\u201d.<\/p>\n After you click on the options table, click the \u201cBrowse\u201d tab at the top of the page.<\/p>\n One of the option names will be \u201csiteurl\u201d. You will see that your original domain name is listed. If your new WordPress blog is on a new domain name, you need to edit that value to your new domain name.<\/p>\n You can do so by clicking the \u201cEdit\u201d button, which looks like a pencil.<\/p>\n Once you click the \u201cEdit\u201d button, just enter your new blog\u2019s URL and then click the \u201cGo\u201d button to save the changes.<\/p>\n The next two values we need to change are usually located on page 2 of the options. At the top and bottom of the main window, you should see the heading \u201cPage number\u201d with a drop-down box. Select page 2.<\/p>\n Scroll down until you see the \u201chome\u201d option. Again, you will see your old WordPress blog\u2019s URL. Click the \u201cEdit\u201d button which looks like a pencil to modify the old blog\u2019s URL.<\/p>\n After you click the \u201cEdit\u201d button, enter your new WordPress blog\u2019s URL, then click the \u201cGo\u201d button to save the changes.<\/p>\n The third and final value we need to change is the upload path. This is the location where WordPress will upload all of your images.<\/p>\n Scroll down until you see the \u201cupload_path\u201d option, and again click the \u201cEdit\u201d button that looks like a pencil to modify this value.<\/p>\n Now you need to enter your new upload path. The only part of your new upload path that you need to modify is the username that your hosting company gave you for your domain name.<\/p>\n This is usually just after \u201c\/home\/\u201d, and in my case is \u201cjrivnet\u201d. Replace this with your new username. This is usually the username you use to login to cPanel, or your domain\u2019s control panel.<\/p>\n If you are still unsure as to what it is, take a look in the left column. Your username is the prefix of your WordPress database. Notice how mine is \u201cjrivnet\u201d.<\/p>\n Once you\u2019re done with that, click the \u201cGo\u201d button to save.<\/p>\n WHEW!<\/strong> You\u2019re finally done with all the database stuff! Your final step is to go to your wp-config.php file of your new WordPress blog. This is in the root folder of your WordPress blog (usually \/home\/ or \/public_html\/). You can do this with your FTP program or the file manager for your new WordPress blog through your hosting company.<\/p>\n Find the file \u201cwp-config.php\u201d and click \u201cEdit\u201d.<\/p>\n Once the \u201cwp-config.php\u201d file is opened, the first things you will see are:<\/p>\n DB_NAME, DB_USER, and DB_PASSWORD.<\/p>\n Enter your new WordPress blog\u2019s database name, username and password between the \u2018 \u2018. Look at the 13th image in this article above just below where I said \u201cYou should get a confirmation telling you that the user has been successfully added to the database\u201d. That was my new WordPress database and username that I created. The 10th image in this article is where I created the user\u2019s password.<\/p>\n This IS NOT your WordPress admin username and password!<\/strong> This is your database\u2019s<\/strong> name and password which you just created for your new host\/server.<\/p>\n Once you enter the new information, save the updated \u201cwp-config.php\u201d file.<\/p>\n You\u2019re done!<\/strong><\/p>\n You can now go to your new WordPress blog\u2019s URL admin login (i.e. example.com\/wp-admin) and login using the same username and password you were using on your original WordPress blog.<\/p>\n That\u2019s about as simple as I can explain the process of moving your WordPress blog to a new server or host. If you have any problems, feel free to post your comment below and we can all do our best to help you along.<\/p>\n","protected":false},"excerpt":{"rendered":" This was by far the most useful page I found for transferring WordPress to a new host. Originally posted here. I have seen many requests online on how to move a WordPress blog to a new server or host- including requests from some of my readers. It seems as though the easy part is transferring … Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[55],"tags":[252,253,251],"class_list":["post-787","post","type-post","status-publish","format-standard","hentry","category-wordpress","tag-wordpress-database-transfer","tag-wordpress-to-new-host","tag-wordpress-transfer"],"_links":{"self":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/787","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=787"}],"version-history":[{"count":5,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/787\/revisions"}],"predecessor-version":[{"id":792,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/787\/revisions\/792"}],"wp:attachment":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=787"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"wordpress](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/wordpress-logo_thumbnail.png\" "\\"How"){kind=logo}
It seems as though the easy part is transferring the files. What most people find difficulty with is moving their WordPress<\/a> database to the new server or hosting company.<\/p>\n
\n
\nIt may look difficult at first with all the steps I\u2019ve included, but I assure you- it\u2019s easier than it looks- especially after you move a blog a few times. It may seem like there are many steps to moving your WordPress<\/a> blog to a new server, but there really aren\u2019t that many. I\u2019ve just broken each step down to make it very clear even to beginners exactly how to move their WordPress<\/a> blog.<\/p>\n![\"sqla](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqla.gif\" "\\"How")
<\/p>\n![\"sqlb](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlb.gif\" "\\"How")
<\/p>\n![\"sqlc](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlc.gif\" "\\"How")
<\/p>\n![\"sqld](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqld.gif\" "\\"How")
<\/p>\n![\"sqle](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqle.gif\" "\\"How")
<\/p>\n![\"sqlf](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlf.gif\" "\\"How")
<\/p>\n![\"sqlg](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlg.gif\" "\\"How")
<\/p>\n![\"sqlh](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlh.gif\" "\\"How")
<\/p>\n![\"sqli](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqli.gif\" "\\"How")
<\/p>\n![\"sqlj](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlj.gif\" "\\"How")
<\/p>\n![\"sqlk](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlk.gif\" "\\"How")
<\/p>\n![\"sqll](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqll.gif\" "\\"How")
<\/p>\n![\"sqlm](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlm.gif\" "\\"How")
<\/p>\n![\"sqln](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqln.gif\" "\\"How")
<\/p>\n![\"sqlo](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlo.gif\" "\\"How")
<\/p>\n![\"sqlp](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlp.gif\" "\\"How")
<\/p>\n![\"sqlq](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlq.gif\" "\\"How")
<\/p>\n![\"sqlr](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlr.gif\" "\\"How")
<\/p>\n![\"sqls](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqls.gif\" "\\"How")
<\/p>\n![\"sqlt](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlt.gif\" "\\"How")
<\/p>\n![\"sqlu](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlu.gif\" "\\"How")
<\/p>\n![\"sqlv](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlv.gif\" "\\"How")
<\/p>\n![\"sqlw](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlw.gif\" "\\"How")
<\/p>\n![\"sqlx](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlx.gif\" "\\"How")
<\/p>\n![\"sqly](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqly.gif\" "\\"How")
<\/p>\n![\"sqlz](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlz.gif\" "\\"How")
<\/p>\n![\"sqlaa](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlaa.gif\" "\\"How")
<\/p>\n![\"sqlab](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlab.gif\" "\\"How")
<\/p>\n![\"sqlac](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlac.gif\" "\\"How")
<\/p>\n![\"sqlad](\"http:\/\/blog.triphp.com\/wp-content\/uploads\/2008\/12\/sqlad.gif\" "\\"How")
<\/p>\n