Combined with the need to transfer website files, restore important databases, and get every software installation and subdomain configuration in working order, it can take up to a day of inactivity before your site is fully functioning again.<\/p>\n
There are, however, some pretty great tricks to avoid disaster when transferring a website to a new host server<\/strong>.<\/p>\n Note:<\/strong> These tips are relatively easy to do as long as the site\u2019s administrator has a general understanding of cPanel<\/a><\/strong>, IP addresses, and more advanced FTP login routines that will enable them to work on a new web hosting plan\u2019s configuration before DNS is altered and transferred to the new host.<\/p>\n At the end of the day, if the average customer is completely unaware of any changes behind the scenes, the mission is a success!<\/p>\n Do not cancel an existing web hosting plan before the move is complete<\/strong>.<\/p>\n The most common mistake made by web tie administrators who are new to web hosting in general or new to transferring their websites between servers is that they almost immediately contact their old host to inform them of their decision to move their services to a new company\u2019s servers.<\/p>\n While it\u2019s certainly a good idea to inform the old web host promptly about future changes, doing so before the transition has been expertly executed can result in not just downtime but a complete loss of files and database information from the moment a cancellation is requested.<\/strong><\/p>\n Web hosting companies generally cancel a plan almost immediately \u2013 as soon as the customer\u2019s call has ended \u2013 without waiting for the expiry of the current month\u2019s service or subscription fee. This is seen as serving the consumer\u2019s best interest, as they get an immediate and prorated refund of any remaining fees<\/strong>.<\/p>\n However, it also means that the company will virtually trash every shred of information that has been uploaded <\/strong>to the server during their time with the company. In many cases, there will be no opportunity to retrieve these files and move them to the new web hosting company\u2019s server or shared hosting plan in time.<\/p>\n That\u2019s the kind of downtime that is extremely hard to recover from, as it potentially means a loss of all content and subscriber data, as well as commercial losses and customer payment details for some websites.<\/p>\n Once a new hosting plan has been secured, transfer all files before canceling the existing hosting plan<\/strong> held by the old company. It might be a good idea to allow the website to run on the new company\u2019s servers for a few days just to ensure that nothing was overlooked during the move.<\/p>\n When everything has been verified as properly transitioned, only then should the old hosting plan be canceled.<\/p>\n Login to cPanel and obtain compressed backups<\/a> of website files and database information<\/strong>.<\/p>\n For pure ease of use, customers moving to a new web host should ensure that both the new and old hosting companies employ the same web-based administration technology. Typically, this will be a choice between cPanel<\/strong> and the slightly less-popular PleskPanel<\/strong> website control panel.<\/p>\n Aligning the technology employed by both hosts is the easiest way to ensure that data can be quickly backed up and restored<\/strong> in just as quick a fashion.<\/p>\n For the cPanel control panel option, which is virtually the standard in web hosting, customers should navigate to their domain with the 2082 port number attached.<\/p>\n For reference, it looks like this in a web browser\u2019s address bar: After successfully logging into the cPanel interface, locate a group of settings and control panel pages labeled \u201cBackup.\u201d This contains tools to back up the site\u2019s main Additionally, the tools here will assist web hosting customers in the backup of their MySQL databases<\/a> for restoration to the new server<\/strong>.<\/p>\n Find the \u201cDownload Backups\u201d option within this grouping, and click through to the relevant cPanel administration page.<\/p>\n On this page, cPanel will break down the available backups by type. A full-site backup is available; they should download that file so that it can be uploaded to a different host later.<\/p>\n There will also be backup files specific to every subdomain<\/strong> within the website. These are generally optional since the full website backup will contain all of that information, but to be safe, you can download these as well.<\/p>\n In a separate area on the same backup downloads page, customers can secure a compressed backup of every MySQL database individually. Each database should be downloaded in its compressed format.<\/strong><\/p>\n These will be uploaded to the new server to create matching database names at a later time.<\/p>\n During this process, be sure not to decompress any of the downloaded backup files. This is because this process will be completed by the new server when the file is uploaded by the customer.<\/p>\n For Mac users, ensure that Safari is not set to automatically open so-called \u201csafe\u201d file extensions after download. Doing so will ensure that the file remains uncompressed and ready for quick restoration<\/strong>.<\/p>\n When all of the compressed backup files are secured, log out of the old host cPanel installation and head over to the new host\u2019s version of the popular website administration software.<\/p>\n Begin uploading the compressed backup files to the new server.<\/strong><\/p>\n Virtually every web hosting company will, after receiving the first month\u2019s fee, send an email bearing information like the domain name servers and IP address details<\/strong> for the new hosting plan.<\/p>\n This IP address can be used to view the website\u2019s content before DNS propagation<\/a> and to access the individual FTP account and cPanel administration interface before changes are made.<\/p>\n Find this email and look for the relevant IP address. If a cPanel link has not been specifically included, assume that either Upon logging into the new server\u2019s cPanel iteration, locate the backup tools mentioned in Step 2, then navigate to the Backup Downloads page. At the page, locate the file-upload box associated with the full-site backup.<\/p>\n This will often be labeled as a \u201cBackup Restore\u201d feature. Select the full-site backup file that was downloaded from the old web hosting company<\/strong> to begin the upload process.<\/p>\n After the file is completely uploaded, the webpage will refresh, and file-specific details will be displayed on a line-by-line basis as each file is moved into place. When this second page stops loading, the process is complete. Locate the browser\u2019s \u201cback\u201d button to return to the previous page and begin the database restoration process in pretty much the same fashion.<\/p>\n When all of the information is transferred, it\u2019s time to adjust some settings and begin the actual seamless transition process behind the scenes.<\/p>\n One thing to note is that the database backup files do not contain information about the usernames, passwords, and permissions associated with each MySQL database.<\/p>\n This information will need to be entered within the MySQL Databases interface within cPanel.<\/p>\n Also, note the prefix assigned to each database within cPanel. In case of discrepancies (e.g., \"jsmith_wordpress\" vs. \"jsm_wordpress\"), the prefixes will need to be changed in the configuration file of each software application that connects to that database.<\/p>\n Add all of the relevant users, passwords, and permissions, and then make any necessary edits to system files by logging into the FTP account via the website\u2019s IP address.<\/p>\n This will ensure the smooth operation of the software<\/strong> once the domain name has been transferred to show the new host\u2019s files instead of those located at the old company. Once that is done, everything is in place and ready to function perfectly.<\/p>\n All that needs to be changed now is the information that tells the domain which of the two hosting accounts\u2019 files to display to the end user.<\/p>\n Tell the domain registrar to use new domain name servers<\/strong><\/p>\n The final step of the process is simply to tell the domain name to show files and data on a different server than the one in current use. This is done by logging into the domain registration control panel<\/strong> provided by the domain registrar (services like GoDaddy<\/a> or Hover<\/a>, for example).<\/p>\n Within this control panel, a heading or sidebar item named \u201cDomain Name Servers\u201d should show up, and the current information placed in that area should look like this:<\/p>\n These need to be replaced with the new name servers<\/strong> (also found in the email) for the new host. (If this information is not found, navigate to the host\u2019s support section, browse their documentation or get in touch with a representative who can provide the server details.)<\/p>\n Changes to the DNS records will take effect in 12 to 24 hours in most cases, though some have experienced as little as six hours. During this time, both the new and old websites will function properly, and customers will see identical content no matter which hosted files are presented.<\/strong><\/p>\n Do keep in mind that posting content before propagation is complete might result in lost content or data after the new host files are active. While downtime won\u2019t be an issue, website owners should refrain from making any changes<\/strong> to a site\u2019s design, files, or content until they\u2019re completely sure that the process is complete<\/strong> and they\u2019re accessing the new host server.<\/p>\n When that becomes the case, the process of transferring a website seamlessly to a new web hosting provider is complete and users will have survived the transition without a second of downtime.<\/p>\n Be sure to test the website and ensure that all features are working properly; when everything is working just like it used to, then you can cancel the old hosting plan. That\u2019s all there is to it!<\/p>","protected":false},"excerpt":{"rendered":" Numerous emerging technologies make it exceedingly easy to move a website from one host to another. However, no matter how fast the speed of the transfer is, the average customer may experience some downtime during the transfer process. Depending on what goes on behind the scenes, the transfer of DNS servers between the old and…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3400],"tags":[4655,4668,4656,467,2189],"topic":[4521],"class_list":["entry-content","is-maxi"],"acf":[],"yoast_head":"\n1. Move first, cancel later<\/h2>\n
![\"work](\"https:\/\/assets.hongkiat.com\/uploads\/website-migration-guide\/work-on-progress.jpg\")
<\/figure>\nHold that call<\/h3>\n
What to do?<\/h3>\n
2. Download backup files<\/h2>\n
![\"backup\"](\"https:\/\/assets.hongkiat.com\/uploads\/website-migration-guide\/backup.jpg\")
<\/figure>\nhttps:\/\/my-site.com:2082<\/code>. Alternatively, https:\/\/my-site.com\/cpanel<\/code> might work for some websites:<\/p>\nLocate the backup page<\/h3>\n
public_html<\/code> folder<\/strong> as well as any subdomains.<\/p>\nDownloading the backup files<\/h3>\n
Do not decompress!<\/h3>\n
3. Making the transfer<\/h2>\n
Logging In<\/h3>\n
\/cpanel<\/code> or the :2082<\/code> port suffix can be added to that IP address in order to enable an administrative login.<\/p>\n![\"restore](\"https:\/\/assets.hongkiat.com\/uploads\/website-migration-guide\/restore.jpg\")
<\/figure>\n4. Ensure the database is working<\/h2>\n
Prefix matters<\/h3>\n
All the relevant info<\/h3>\n
5. Switch nameservers<\/h2>\n
\r\nNS1.OLD-WEBHOST.COM\r\nNS2.OLD-WEBHOST.COM<\/pre>\n
Wait for nameserver propogation<\/h3>\n
Summary<\/h2>\n