How long does a WHM to WHM migration take?

Migration time depends on the number of accounts and data volume. A single cPanel account with a small website takes 15–30 minutes. Full server migrations with 20+ accounts and large databases can take 4–12 hours. Testing and DNS propagation add another 24–48 hours.

Will my website go down during a WHM migration?

Not if done correctly. Using the hosts file testing method, DNS TTL lowering, and the WHM Transfer Tool, migrations can be performed with zero downtime. Users continue accessing the old server until DNS is switched to the new one.

Can I migrate from one hosting provider to another using WHM?

Yes. As long as both servers run WHM/cPanel, the WHM Transfer Tool works regardless of hosting provider. You need root access or SSH credentials on both servers. This is common when switching from GoDaddy to LiquidWeb, for example.

What happens to my email during a WHM server migration?

Email accounts and data are migrated by the WHM Transfer Tool. However, you must update MX records when switching DNS. During the brief propagation window, emails may be delivered to either server. Lower TTL beforehand to minimize this window.

Do I need to reinstall SSL certificates after migrating WHM?

The WHM Transfer Tool copies existing SSL certificates. However, after DNS changes, you should run AutoSSL on the new server to issue fresh certificates. This ensures certificates are properly validated against the new server IP.

How to Migrate WHM to WHM the Right Way

Why Migrate WHM to WHM?

Migrating a server from WHM to WHM isn't just a file copy — it's infrastructure orchestration. If you're moving cPanel accounts between servers (for performance, security, compliance, or consolidation), the process must protect DNS, SSL, email, databases, permissions, SEO, and ensure zero downtime.

At Hatty AI, we migrate WHM environments regularly for agencies, eCommerce brands, and compliance-driven organizations. Below is the exact framework we use to perform clean, production-grade WHM → WHM migrations.

Common reasons to migrate include:

Upgrading to a newer server (AlmaLinux 9, better CPU/RAM)
Moving from shared/dedicated to VPS
Escaping overloaded servers
Reorganizing multi-account infrastructure
Compliance hardening (NIST, HIPAA, CMMC alignment)
Consolidating client accounts under one master WHM

⚠️ If you're running multiple WordPress + WooCommerce sites, getting this wrong can mean broken email, payment failures, and lost revenue.

Phase 1: Pre-Migration Planning

Before touching anything, validate these items:

1. Confirm WHM Version Compatibility

Both servers should run:

Compatible cPanel versions
Compatible OS (AlmaLinux 8 → AlmaLinux 9 is fine)
Matching PHP versions

In WHM:

WHM → Server Information → Apache Version / PHP Version

2. Lower DNS TTL (Critical)

24 hours before migration, lower TTL in DNS to:

300 seconds

This ensures fast propagation when switching IPs later.

3. Full Backups

On the source WHM:

WHM → Backup → Generate Full Backup

Or for specific accounts:

WHM → Transfers → Copy an Account from Another Server

Phase 2: The Proper WHM to WHM Migration Method

There are two ways to migrate:

Method 1 (Recommended): WHM Transfer Tool

This is the cleanest and safest method.

On the NEW Server:

WHM → Transfers → Transfer Tool

Enter:

Source server IP
Root credentials or SSH key
Select accounts to migrate

Enable:

Express Transfer (optional)
Copy reseller privileges (if applicable)

Click Copy. WHM will automatically migrate:

Home directories
Databases
Email accounts
SSL certificates
DNS zones
Cron jobs
Subdomains
Addon domains

✅ This is the preferred enterprise method.

Method 2: Manual Backup & Restore (Less Ideal)

From source server:

/scripts/pkgacct username

Transfer the backup file to new server:

/scripts/restorepkg username

This works but requires more oversight.

Phase 3: Testing Before DNS Switch (Zero Downtime Strategy)

Never switch DNS blindly.

Use the Hosts File Method

On your local machine:

Windows:

C:\Windows\System32\drivers\etc\hosts

Add:

NEW_SERVER_IP domain.com
NEW_SERVER_IP www.domain.com

Now only YOU see the new server.

Test:

WordPress login
WooCommerce checkout
Forms
Email sending
SSL status
API integrations (Stripe, Mailgun, etc.)

💡 This prevents downtime and SEO damage.

Phase 4: SSL & AutoSSL Validation

On new WHM:

WHM → Manage AutoSSL → Run AutoSSL

Ensure:

All domains show valid certificates
No mixed content errors
No redirect loops

Phase 5: DNS Cutover

When fully validated, update DNS A records:

domain.com → NEW_SERVER_IP
www        → NEW_SERVER_IP

If using external DNS (Cloudflare, GoDaddy, etc.), update there.

Because TTL was lowered earlier, propagation should complete within minutes.

Phase 6: Post-Migration Validation Checklist

After propagation:

✅ Remove hosts file entry
✅ Test from mobile network
✅ Verify email delivery
✅ Confirm SPF/DKIM/DMARC
✅ Check cron jobs
✅ Monitor error logs
✅ Run Google Search Console inspection
✅ Confirm sitemap loads
✅ Verify robots.txt

Common Migration Pitfalls (Avoid These)

❌ Using mod_userdir (~username)

Breaks WordPress sessions and SSL.

❌ Forgetting Mail Routing

If MX isn't moved correctly, email breaks.

❌ Not Checking PHP Versions

Different PHP builds can break plugins.

❌ Forgetting to Reissue AutoSSL

Old certificates won't automatically carry over if DNS changed.

Enterprise-Level WHM Migration Enhancements

At Hatty AI, we add:

Pre-migration performance benchmarking
Database optimization during move
Malware scanning before restoration
Hardened firewall reconfiguration
ModSecurity rules review
Automated Mailgun / SMTP validation
AI-based log anomaly scanning

For WooCommerce clients, we also:

Put checkout in maintenance briefly
Freeze order processing during final sync
Perform final DB delta validation

When NOT to Use WHM to WHM

Consider alternatives if:

You're moving to Kubernetes or containerized hosting
You need decoupled architecture (React + API)
You want object storage (S3) offloading
You're scaling to multi-region infrastructure

In those cases, migration strategy changes significantly.

Final Thoughts from Hatty AI

WHM to WHM migration is straightforward — but only if executed with a proper process.

The key principles:

Plan
Lower TTL
Transfer using WHM tools
Test via hosts file
Validate SSL
Cut DNS
Monitor

Done correctly, users will never know the server changed.

📖 Continue Reading

How to Set Up GitHub with VPS Hosting via WHM & cPanel — Deploy your pipeline to a VPS with SSH keys and cPanel Git Version Control.

Managed Hosting Services — Learn about our WordPress maintenance and VPS optimization services.

Need Help Migrating Your WHM Server?

Fill out the form below and our team will reach out to discuss your migration needs — from single-account moves to full multi-server consolidation.

Ready to Migrate Without Downtime?

Hatty AI handles full-stack WHM migrations including WordPress, WooCommerce, multi-account clusters, compliance-ready environments, and AI monitoring.

Schedule a Strategy Call

How to Migrate WHM to WHM the Right Way

Featured Article