How to migrate a website to cPanel

By /

Migrating your website doesn’t have to be nerve-wracking. Whether you’re switching hosts, moving from another control panel, or consolidating multiple sites into one dashboard, this Migrate to cPanel guide walks you through every possible route. Over this article, you’ll explore everything from the powerful WHM Transfer Tool (ideal for full cPanel-to-cPanel moves) to manual migrations with rsync, backups, and database imports. We’ll also cover application-specific tools like Installatron and hPanel exports, plus post-migration must-dos such as DNS updates, SSL reinstallation, and smoke-testing your sites.

You’ll learn best practices for minimizing downtime, ensuring compatibility, and avoiding common pitfalls. By the end of this guide, you’ll have the confidence to migrate with precision and minimal disruption—whether you’re managing a portfolio of WordPress sites or a mission-critical business app. Let’s get your site safely to its new home on cPanel, step by step.

Preparing for Migration

Before you dive into the migrate to cPanel process, a little prep goes a long way toward a smooth transition. First, conduct an inventory: note your files (including hidden .htaccess files), databases, email accounts, SSL certificates, cron jobs, and any non-standard configurations (PHP extensions, .htaccess rules, custom DNS templates). This ensures nothing gets left behind during transfer.

Next, check compatibility. Are your PHP, MySQL (or MariaDB), and Apache versions on the target cPanel server compatible with your website? If you’re running older PHP, you might need to update or patch, especially since many modern hosts default to PHP 7.4+ – Liquid Web cautions that mismatched CMS versions can introduce errors if ignored

Now, create full backups. Depending on your chosen method, you may need full account backups (cpmove), partial file archives, or DB dumps. And don’t skip the TTL hack: lower DNS TTL to ~300 seconds a day before migration to expedite switchover. Want zero-downtime feel? Use your computer’s /etc/hosts (or Windows C:\Windows\System32\drivers\etc\hosts) to preview the site on the new IP before DNS propagates—Liquid Web recommends this trick for safe testing Liquid Web.

Finally, ensure you have required access. For full migrations via WHM Transfer Tool, you need root or sudo privileges on both source and destination servers. If you’re doing backups only and you’re on shared hosting, you’ll rely on cPanel-level tools or manual FTP/DB migrations. Plan accordingly- GoDaddy’s Installatron approach, for instance, works without root access, but still requires correct FTP and path info.

By covering your bases – backups, compatibility checks, access plans – you’re setting yourself up for a stress-free, successful migration with confidence.

Method 1 – WHM Transfer Tool

When you have server-level access, the WHM Transfer Tool is hands-down the cleanest method to migrate to cPanel with minimal manual work. With both source and target servers accessible via root or sudo, WHM lets you scan, select, and send entire accounts—configurations, email, files, and databases—all in one go.

To start, log into the WHM interface on the destination server and navigate to Transfers → Transfer Tool. Add your source server’s IP, SSH port (typically 2087), and authentication (password or SSH key). Click “Scan Remote Server” to discover available cPanel accounts. When that’s ready, choose what to migrate—single or multiple accounts, plus options like AutoSSL settings, feature modules, email routing, and package definitions cPanel & WHM Documentation.

If you want minimal disruption, enable “Live Transfer.” This smart feature keeps the old server running, proxies web and mail traffic to the new server, and ensures incoming mail is delivered correctly throughout. It even updates A and MX records behind the scenes – translation: users may never notice the shift.

Beware limitations. Don’t run system updates during transfer, disable FrontPage if present—it isn’t supported, and watch out for custom DNS templates or 2FA settings, which may not copy over.

Unique insight: if your sites use legacy CMS versions that rely on outdated PHP functions, consider temporarily installing a containerized environment with older PHP versions on the cPanel server using CloudLinux or CageFS. Liquid Web suggests this helps maintain compatibility effortlessly through migration.

Once complete, WHM gives you a log. Verify all accounts transferred and test via temporary URL or hosts file. If everything checks out, switch DNS and retire the old server.

Quick Takeaways

  • Backup everything—site files, databases, emails, SSL.
  • Use WHM Transfer Tool when possible for fastest, lowest-downtime migration.
  • Manual rsync + DB import works well if you lack root access.
  • Lower DNS TTL and use hosts file preview to test the new server before going live.
  • Reapply SSL and verify DNS/zone file settings post-migration.
  • Watch for compatibility issues—PHP/MySQL versions can break legacy sites.
  • Finalize with thorough testing—confirm mail, links, apps, and performance.

Method 2: Manual Migration Process

Here’s a detailed, move site to cPanel manually step by step guide:

Backup everything

  • In your current cPanel, go to File Manager, compress everything under public_html, download the ZIP.
  • Use phpMyAdmin to export the WordPress database as an SQL file.

Login to your cPanel account

  • If you don’t already have a cPanel account, you can look at some of our options before deciding which host to use.

Upload to new cPanel account

  • Log in, open File Manager inside the target public_html, upload the ZIP, and extract it.

Create and import the database

  • In MySQL Databases, create a new DB and user; assign privileges.
  • Use phpMyAdmin to import the SQL.

Configure WordPress

  • Edit wp-config.php to update DB name, user, password, and any table prefixes.

Test before pointing DNS

  • Use hosts file mapping or temporary URL to test your site before making it live.

Update DNS records

  • Point your domain to the new server’s nameservers or A record, then wait 24–48 hours for propagation.

Ensuring Zero Downtime & Safe Restoration

Downtime fears often paralyze site owners—but with proper steps, you can execute a cPanel migration without downtime:

  • Backup and staging: Always keep full backups pre-transfer; use staging environments to test migration before going live.
  • DNS TTL reduction: Lower the Time-to-Live (TTL) value on your DNS records a few days before migration (e.g., to 300 seconds) to speed up propagation.
  • Maintenance mode: Enable WordPress maintenance mode during migration to prevent content changes mid-transfer.
  • Monitor traffic and site health: Use tools or server logs to ensure users land on the new site immediately once DNS updates complete.
  • According to Bluehost’s migration checklist, a well-prepared transfer preserves SEO, minimizes broken links, and ensures mobile responsiveness post-migration Bluehost.

Quick Safety Checklist for Beginners

For added peace of mind:

  • Full site backup (files + database)
  • Staging test of migrated site
  • Updated wp-config.php with correct DB credentials
  • Temporary URL or hosts file preview
  • DNS TTL lowered pre-migration
  • Migration done during off-peak hours
  • Post-migration: Check SSL, permalinks, plugins, broken links, site speed

Conclusion

Migrating WordPress to cPanel doesn’t have to be daunting—by following this step-by-step tutorial, you’ve learned how to back up your site, manually transfer files and databases, implement safety measures for zero downtime, and verify everything post-migration. Now that you’re equipped to migrate safely, why stop here? Test out your new site, explore cPanel features, and let me know how the process goes!

Still not too sure if you’re doing the migration correctly? We’ve got you covered! Get in touch with our Migration Team and we can handle the migration on your behalf.

Scroll to Top