| Changing from one web hosting provider to another | | | | site. Use a temporary URL to test the site to ensure |
| can cause downtime if you do not have the | | | | that everything is working correctly. Are you able to |
| necessary skills and experience. Here is a step by | | | | connect to the database? Are the links and images |
| step guide to help you make a transfer without any | | | | displaying correctly? If everything has been tested to |
| downtime. | | | | work fine, it's now time to make changes to the |
| Step 1: Back up all your files. | | | | DNS. |
| This must always be your first step. Before you do | | | | Step 5: Changing the DNS. |
| anything else, backup all your files from the old | | | | The moment you change your DNS, you are |
| server. Back up your text files, image files, and | | | | instructing the registrars that you are changing web |
| database. This may take several hours, depending on | | | | hosting providers. Your top level domain name will |
| the size of your website. | | | | then point to the domain name servers. Go to your |
| Use FTP to transfer all files to your local hard drive. | | | | registrar, and update your DNS servers. There must |
| For databases, you may need to use a third party | | | | be at least 2 domain name servers. Once the DNS |
| software, or you can use PhpMyAdmin. PhpMyAdmin | | | | has been updated, it takes a few hours for the |
| is available within your Cpanel control panel. | | | | changes to take place. |
| Step 2: Upload all files to the new server. | | | | Some webmasters make the mistake of changing |
| Once you have backed up everything, upload all files | | | | the DNS first. This is a mistake. When you change |
| to the new server. Make sure the directory structure | | | | the DNS, the site starts to migrate. Some of your |
| is correct. For example, if "www" is the root folder, | | | | visitors may be unable to access your site because |
| all files that belong to the root folder must be | | | | the new site is not ready yet. In other words, |
| uploaded correctly to that folder. Otherwise, you | | | | making changes to the DNS before the new site is |
| may encounter lots of errors when you migrate your | | | | ready can cause unwanted downtime. |
| website. Use your database software to upload the | | | | Step 6: Wait 48 hours for the changes to take place. |
| database as well. | | | | Usually, the migration happens within hours. Allow up |
| Step 3: Add email accounts to your new server. | | | | to 48 hours for the DNS updates to be completed. |
| Log in to your control panel, and add your existing | | | | You can see that the transfer has been completed |
| email accounts. When your new site is ready, your | | | | by using a WHOIS domain tool. The new name |
| POP email accounts should be working as well. | | | | servers will be reflected when you make a search |
| Step 4: Test your mirror site. | | | | for your top level domain. Finally, check to see that |
| You have just created a mirror site for your existing | | | | your email accounts are working correctly. |