![\"How](\"https:\/\/www.plus.hr\/blog\/wp-content\/uploads\/2024\/12\/Untitled-design.jpg\")
<\/a><\/p>\nPreparing for cPanel to cPanel migration<\/h2>\n
One of the wisest proverbs known to mankind is most likely \u201cAssumption is the mother of all mistakes.\u201d. We highly advise you to do this as the first and foremost step when considering a host change, even before purchasing a new cPanel hosting package.<\/span><\/p>\n Check where your domain is registered. Do you have access to a portal where at the end you\u2019ll be able to change the NS records<\/strong> on your domain?<\/span><\/p>\n Confirm that your domain resolves as expected<\/strong> and that the website and email are really using the server\/cPanel you assume they are.<\/span><\/p>\n You can use online tools like Google’s Dig<\/a> to check your domain\u2019s A record<\/strong> (website) and MX record<\/strong> (mail). If they both resolve to the same IP, it means they\u2019re on the same server.<\/span><\/p>\n On the same page, you can see the NS records<\/strong>. This is where your DNS is and where you\u2019ll later need to make changes. If they\u2019re the Nameservers<\/strong> of your hosting provider, you can make changes to the DNS via your current cPanel.<\/span><\/p>\n In your current cPanel lower your TTL to 300 (seconds, meaning 5 minutes). Wait for the old TTL to expire (usually 14400 seconds, meaning 4 hours). We do this so that when we later update our IP\u2019s in the DNS after the migration, we only have to wait 5 minutes for the changes to propagate.<\/span><\/p>\n NOTE<\/strong>: Keep in mind that NS (nameserver) changes on your domain can take up to 24-48 to propagate, so this is a nice way to speed up the process.<\/span><\/p>\n If you\u2019d like to read up a bit more about DNS and the most common record types, feel free to take a moment to check out our blog post regarding DNS zones<\/a>.<\/span><\/p>\n In your current cPanel, review Disk Usage under Statistics<\/strong>. This ensures you have enough space to complete the migration.<\/span><\/p>\n On your current cPanel account, check the PHP version<\/strong> you\u2019re using as well as the extensions. Logon to your new cPanel and make sure to set up the same PHP version and compare extensions.<\/span><\/p>\n Depending on your CMS, determine if MySQL databases are in use<\/strong>. For WordPress<\/strong>, this information is in the Features vary from hosting provider to hosting provider, even if they both use cPanel. If unsure regarding any of the points mentioned above, don\u2019t hesitate to ask your current provider for clarification or confirmation about how your services are set up.<\/span><\/p>\n <\/p>\n You can transfer your files by either connecting via FTP<\/strong> (preferred method) or by compressing<\/strong> its contents via cPanel\u2019s Focus on the following folders:<\/span><\/p>\n You can easily export and download your database\/s<\/strong> via You can do this as mentioned before via FTP<\/strong> or you can again use File Manager<\/strong> and upload the ZIP<\/strong> archives you made before into the corresponding folders and hit Extract.<\/span><\/p>\n Ensure the following mapping:<\/span><\/p>\n On the new cPanel create the new database and database user. Don\u2019t forget to assign the database user to its database and assign privileges.<\/span><\/p>\n Not sure how? Check out our tutorial with video instructions<\/a>.<\/span><\/p>\n Use Depending on your CMS<\/strong>, you might need to update the paths in the database. <\/span><\/p>\n For example Joomla doesn\u2019t store its paths in the database, but WordPress does. If your application path has changed from, for example, Never done it before? Then we highly recommend you check out our blog post How to change domain name in WordPress web site<\/a>. Although you might not be changing the domain itself, the process is the same for updating your paths.<\/span><\/p>\n Update the following:<\/span><\/p>\n Check your Email Accounts<\/strong> list to confirm cPanel has detected all email accounts and their contents. <\/span><\/p>\n Under Email Routing<\/strong> make sure it\u2019s set to Local Mail Exchanger<\/strong>.<\/span><\/p>\n Before redirecting the domain to the new server, we always advise checking the website with the The purpose of using the hosts file is to \u201ctrick\u201d your computer into loading the website from the new server before the switch is live. Its location will depend on the OS you\u2019re using, for which you can find instructions here<\/a>.<\/span><\/p>\n Your line would look like this:<\/span><\/p>\n IP.OF.THE.NEW.SERVER youdomain.tld www.youdomain.tld<\/span><\/p><\/blockquote>\n If unsure, you will find your new server\u2019s IP on your new cPanel\u2019s frontpage on the right.<\/span><\/p>\n When this is setup, open your domain in a new browser window (remember to clear cache or use incognito mode) and test everything.<\/span><\/p>\n NOTE<\/strong>: Don\u2019t forget to delete the line from your When all is working as expected, login to the cPanel account you\u2019re migrating from and update all the IPs to the new one.<\/span><\/p>\n NOTE<\/strong>: Don\u2019t forget to add 5 minutes after the change, you can check if the domain is resolving correctly from the new server. You can again use, for example, Google’s Dig<\/a>.<\/span><\/p>\n Remember when at the beginning we asked Do you have access to a portal where at the end you\u2019ll be able to change the NS records on your domain? At your domain registry, you can now update the NS records to the new ones<\/strong>. If unsure, ask your new hosting provider how they\u2019re named exactly.<\/span><\/p>\n <\/p>\n Congratulations<\/strong>! You\u2019ve now successfully migrated from one cPanel account to another.<\/span><\/p>\n <\/p>\n Why migrate when you could be watching movies, reading a book or tending to your aquarium? Here at Plus Hosting we offer free migrations<\/strong> with every hosting package<\/a> purchased!<\/p>\n1. Check your domain<\/h3>\n
2.\u00a0Check your domain resolving<\/h3>\n
3.\u00a0Check your NS and lower TTL<\/h3>\n
<\/a><\/p>\n4.\u00a0Check Disk usage<\/h3>\n
<\/a><\/p>\n5.\u00a0Check the PHP Version You\u2019re Using<\/h3>\n
<\/a><\/p>\n6.\u00a0Check the MySQL Database(s)<\/h3>\n
wp-config.php file<\/code>, while for Joomla<\/strong>, it\u2019s in configuration.php<\/code>.<\/span><\/p>\n<\/a><\/p>\n7. Don\u2019t be afraid to ask<\/h3>\n
Phase One: Download<\/h2>\n
Collect your files\/folders<\/h3>\n
File Manager<\/code> and downloading<\/strong> the ZIP archive.<\/span><\/p>\n\n
public_html<\/code> – the root folder of your application<\/span><\/li>\nmail & etc<\/code> – these will be needed for having the emails on your new cPanel<\/span><\/li>\n<\/ul>\n<\/a><\/p>\nCollect your database(s)<\/h3>\n
phpMyAdmin<\/code>.<\/span><\/p>\n<\/a><\/p>\nPhase Two: Upload<\/h2>\n
Upload files\/folders to your new cPanel<\/h3>\n
\n
public_html<\/code> go to public_html<\/code>.<\/span><\/li>\nmail<\/code> go to mail<\/code>.<\/span><\/li>\netc<\/code> go to etc<\/code>.<\/span><\/li>\n<\/ul>\nPhase Three: Database Setup<\/h2>\n
Create a new database<\/h3>\n
Import your database<\/h3>\n
phpMyAdmin<\/code> to import the database.<\/span><\/p>\n<\/a><\/p>\nPhase Four: Web Cleanup<\/h2>\n
Update Paths in the Database<\/h3>\n
\/home\/someolduser\/public_html<\/code> to \/home\/hellonewuser\/public_html\/<\/code> and you use Wordress, you\u2019ll have to use a Search&Replace plugin to update.<\/span><\/p>\n\n
someolduser_wpdb<\/code> to hellonewuser_wp<\/code>, as well as the password, don\u2019t forget to update your wp-config.php<\/code>, configuration.php or corresponding configuration file depending on your CMS.<\/span><\/li>\n.htaccess<\/code> and update paths there if needed.<\/span><\/li>\n<\/ul>\nPhase Five: Email Checkup<\/h2>\n
Verify email accounts<\/h3>\n
<\/a><\/p>\nSet Email Routing<\/h3>\n
<\/a><\/p>\nPhase Six: Testing<\/h2>\n
Test your website<\/h3>\n
hosts<\/code> file<\/strong>.<\/span><\/p>\n<\/a><\/p>\nhosts file<\/code> after testing is done.<\/span><\/p>\nPhase Seven: Redirect<\/h2>\n
ip4:YOUR.NEW.IP.ADDR<\/code> at the end of the spf record before the \u201call\u201d keyword, where YOUR.NEW.IP.ADDR<\/code> is the IP of the new server. We wouldn\u2019t want our emails to be marked as SPAM, would we?<\/span><\/p>\n<\/a><\/span><\/p>\nPhase Eight: Update NS Records<\/h2>\n
Done!\u00a0<\/span><\/h2>\n
Did You Know?<\/h2>\n