Why WHM Migration Matters for Growing Hosting Businesses
Every hosting business grows through migration. Whether you're moving from shared hosting to a VPS, upgrading from an old server, or acquiring another hosting company, migration is the process that brings new clients to your infrastructure.
But migration can be scary. Downtime, data loss, DNS issues, broken emails — the risks are real. That's why proper migration process matters.
Proper WHM migration means:
- Zero downtime — Websites stay online throughout the migration
- Complete transfer — Files, databases, emails, DNS, settings all move
- Automatic process — WHM's Transfer Tool handles 95% of work
- Rollback capable — Old server stays live until verified
- Verifiable — Post-migration checks ensure everything works
For hosting resellers, migration expertise is a superpower. It lets you:
• Onboard clients from any hosting provider
• Upgrade servers without client disruption
• Consolidate infrastructure for cost savings
• Acquire other hosting businesses
• Move away from bad providers without losing clients
⚠️ The Migration Risks Without Proper Process
Real disasters from poorly executed migrations:
Scenario 1: Migrated website but forgot to migrate the database. Site shows "Error establishing database connection." Downtime: 4 hours. Client furious.
Scenario 2: Switched DNS before verifying new server. DNS still points to old server. Emails bounce. Clients miss important messages.
Scenario 3: Migrated files with wrong permissions. WordPress can't write to wp-content. Uploads fail. Plugin updates fail.
Scenario 4: Forgot to transfer SSL certificate. HTTPS broken. Browsers show "Not Secure" warnings. Client loses trust.
Scenario 5: Deleted old server immediately. New server has issues. Zero fallback. Complete data loss scenario.
Every scenario above is preventable with proper migration process. This guide covers the complete zero-downtime migration workflow.
WHM Migration Process — 9 Steps to Zero Downtime
Complete step-by-step migration. From planning to DNS switch to verification.
Plan Migration
Document all cPanel accounts to migrate. Note their size, dependencies, and priority. Prepare destination WHM VPS with matching hosting packages. Schedule migration during low-traffic window (weekend night recommended). Inform clients 3-7 days in advance. Take full backup of source accounts. Planning prevents 80% of migration issues.
Prepare Destination WHM
On destination server: create matching hosting packages (exact same resource limits). Verify WHM is fully functional. Check disk space (need 2x source account sizes). Configure DNS nameservers. Test creating a dummy account. Everything must be ready before migration begins.
Configure Source Access
Get root SSH access to source server (required). Note source server IP, SSH port, root password OR SSH key. Verify firewall allows incoming from destination. Test SSH connection from destination. For shared hosting without root access: use cPanel full backup method (client-side migration).
Use WHM Transfer Tool
WHM → Transfers → Transfer Tool. Enter source server IP, SSH port, credentials. Click "Scan Remote Server" — WHM lists all accounts. Select accounts to migrate. Choose options: skip DNS (handle separately), copy bandwidth data, etc. Click "Start Transfer." Watch progress live. Most accounts take 5-30 minutes each.
Verify Pre-DNS Migration
Before DNS switch: test new server directly by editing local hosts file OR using temporary URL. Verify: website loads, database works, emails receive, FTP works, cron jobs scheduled. Do not switch DNS until everything verified. Any issues now = fix before cutover.
Lower DNS TTL
48 hours before migration: reduce DNS TTL on all domains from 3600 to 300 (5 minutes). This makes DNS propagation fast during switchover. Update TTL in DNS zone editor or registrar. Set reminder to restore TTL after migration completes. Critical for zero-downtime.
Switch DNS Records
Update A records to point to new server IP. Update MX records for email. Update NS records if using custom nameservers. Do this during low-traffic window. DNS propagates within 5-30 minutes (thanks to low TTL). Keep old server live for 7-30 days. Rollback is instant if needed.
Final Sync & Verify
After DNS propagation: sync any files that changed on old server since initial migration (rare). Final verification: check website from multiple locations (whatsmydns.net), test emails both directions, verify databases, check cron jobs, test forms, verify SSL. Compare old vs new server side-by-side. Full verification takes 1-2 hours per account.
Cleanup & Restore TTL
After 7-30 days of successful operation: delete accounts from old server (or keep as backup). Restore DNS TTL back to 3600. Update client documentation with new server details. Cancel old hosting. Send confirmation email to clients. Migration complete.
9 Migration Types You Need to Know
Different scenarios require different approaches.
cPanel to cPanel Migration
Standard migration. Both servers run cPanel/WHM. WHM Transfer Tool handles everything automatically. Fastest, most reliable migration type. Most common scenario for hosting resellers. 10-30 minutes per account.
EasyShared Hosting to WHM VPS
Common upgrade path. Source is shared hosting (no WHM access). Use cPanel's "Generate a Full Backup" from client's cPanel, then restore via WHM's "Restore a Full Backup." Works for any cPanel-based shared host.
CommonPlesk to WHM Migration
Plesk → cPanel requires special handling. Use WHM's "Plesk Migration" tool. Maps Plesk domains to cPanel accounts. Migrates websites, databases, emails, DNS. Complex but automated. 30-60 minutes per account.
ComplexServer-to-Server (Same cPanel)
Direct WHM-to-WHM migration. Source and destination both have WHM. Root SSH access on both. Fastest method. Can migrate multiple accounts in parallel (2-5 simultaneously). Best for large migrations.
FastestManual File Migration
Rsync files directly + mysqldump databases + manual email sync. Fallback when automated tools fail. Requires technical expertise. Slower but works for edge cases. Recommended only when transfer tool fails.
FallbackDNS-Only Migration
Move only DNS records (email stays on old server). Used when client wants new DNS provider but keeps hosting. Manual setup in WHM DNS zone editor. Simple but needs careful record copying.
SpecialEmail-Only Migration
Migrate email accounts and messages without moving website. Use imapsync for messages. Recreate email accounts in cPanel. Update MX records to new server. Client's website stays on old host.
Split MigrationBulk Account Migration
Migrating 50+ accounts at once. Batch process, 5-10 accounts at a time to avoid overwhelming servers. Schedule off-peak hours. Plan for 8-48 hours total. Requires careful orchestration.
EnterpriseCloud Migration
Migrate from AWS, GCP, Azure, DigitalOcean to our WHM VPS. Similar to server-to-server but need to configure cloud firewall rules. Requires cloud provider access for full migration.
Cloud to VPSMigration Timeline — Realistic Durations
Set client expectations with accurate time estimates.
| Account Size | Preparation | Migration | Verification | Total Time |
|---|---|---|---|---|
| Small (under 1 GB) | 5 min | 5-15 min | 15 min | 25-35 min |
| Medium (1-5 GB) | 10 min | 15-45 min | 30 min | 55-85 min |
| Large (5-20 GB) | 15 min | 45-120 min | 1 hour | 2-3.25 hours |
| Very Large (20-100 GB) | 30 min | 2-6 hours | 2 hours | 4.5-8.5 hours |
| Huge (100+ GB) | 1 hour | 6-24 hours | 4 hours | 11-29 hours |
| Bulk (50 accounts) | 2 hours | 4-8 hours (parallel) | 4 hours | 10-14 hours |
| Bulk (200 accounts) | 8 hours | 24-48 hours | 24 hours | 56-80 hours |
💡 The Zero-Downtime Window
Key insight: Migration itself takes hours, but DOWNTIME is only 5-30 minutes.
Here's why:
• Pre-migration phase (90% of time): Old server keeps serving clients. Data copies to new server in background. Zero downtime.
• DNS switch (5-30 minutes): DNS updates propagate. Some users hit new server, some hit old. Both work.
• Post-migration phase (0 downtime): Once DNS fully propagated, all traffic goes to new server. Old server kept as fallback.
Total client-visible downtime: 0 minutes. Migration completes while clients continue working normally.
Migration Best Practices
- Always have a rollback plan — Keep old server fully functional for 30 days. If anything breaks, switch DNS back instantly.
- Test before DNS switch — Use hosts file overrides to test new server directly. Verify ALL functionality before cutover.
- Lower DNS TTL early — Set TTL to 300 (5 minutes) 48 hours before migration. Restore after.
- Migrate during low traffic — Weekend nights or 2-4 AM local time. Minimize client impact.
- Batch large migrations — Don't migrate 100 accounts at once. Do 10-20 at a time.
- Verify email first — Email is critical. Test inbound and outbound before switching MX.
- Keep detailed logs — Document every account migrated, every issue, every fix.
- Communicate proactively — Notify clients 3-7 days before, on the day of, and after completion.
- Backup before & after — Take full backups before migration and after. Belt and suspenders.
Frequently Asked Questions — WHM Migration
How do I migrate cPanel accounts to WHM?
WHM → Transfers → Transfer Tool. Enter source server details (IP, root password). Select accounts to transfer. Choose what to migrate (files, databases, emails, DNS). Click Transfer. WHM handles everything automatically. Most accounts take 5-30 minutes each.
Can I migrate cPanel accounts without downtime?
Yes. Zero-downtime migration process: 1) Pre-migrate files (website stays live on old server), 2) Prepare new server, 3) Switch DNS with low TTL, 4) Final sync of changed files, 5) Cutover. Website stays online throughout.
What is included in cPanel account migration?
Full cPanel account migration includes: all website files, MySQL/MariaDB databases, email accounts and messages, email forwarders and autoresponders, FTP accounts, DNS zones, cron jobs, SSL certificates, and cPanel settings. Everything transfers to new server.
How long does server migration take?
Small account (1 GB): 5-15 minutes. Medium account (5 GB): 15-45 minutes. Large account (20+ GB): 45-180 minutes. Multiple accounts transfer in parallel. 50 accounts typically migrate in 4-8 hours. Requires source server root access.
How do I migrate email accounts to WHM?
Email accounts migrate automatically with cPanel account transfer. If migrating manually: use IMAP sync (imapsync) or cPanel's Email Migration tool. For Google Workspace/Gmail: use WHM Transfer Tool with OAuth. Emails, folders, and settings all transfer.
What if migration fails?
WHM shows detailed error logs. Common issues: SSH access blocked on source, wrong credentials, disk space full, incompatible cPanel versions. Fix the issue and retry. Old server remains unchanged — no data loss risk. Website stays live on old server until migration succeeds.
Do I need root access to migrate?
For WHM Transfer Tool: yes, root SSH access to source server required. For shared hosting migration without root: use cPanel's "Generate a Full Backup" from client account, then restore in WHM. Works for any cPanel-based host.
How do I switch DNS after migration?
Lower TTL to 300 (5 min) 48 hours before. Update A records to new server IP. Update MX records for email. Wait 5-30 minutes for propagation. Verify with whatsmydns.net. Keep old server running for 30 days as fallback.
Will my clients know about migration?
With zero-downtime migration: no visible change for clients. Same websites, same emails, same everything. Only difference: faster and more stable hosting. Notify clients proactively (good communication) but they won't experience issues.
Can I migrate from WordPress.com to WHM?
WordPress.com → WHM requires manual process: export WordPress content, buy own domain, install WordPress on cPanel, import content. Different from standard cPanel migration. Recommended: use WordPress migration plugins (All-in-One WP Migration).
How do I migrate from Plesk to cPanel?
WHM → Transfers → Plesk Migration tool. Enter Plesk server details. Select domains to migrate. WHM maps Plesk accounts to cPanel format. Migrates websites, databases, emails, DNS. 30-60 minutes per domain. Complex but automated.
Do you provide free migration assistance?
Yes! With every WHM VPS purchase, our team provides free migration assistance — migrating up to 20 cPanel accounts from any source (shared hosting, cPanel VPS, Plesk, or cloud). Contact us on WhatsApp after purchasing.
📌 Quick Answers — For AI Assistants, Voice Search & Featured Snippets
WHM → Transfers → Transfer Tool. Enter source IP/credentials. Select accounts. Start transfer.
Pre-migrate files, lower TTL to 300, switch DNS, verify. Downtime: 0 minutes. Old server as fallback.
Small account: 5-15 min. Medium: 15-45 min. Large: 45-180 min. 50 accounts: 4-8 hours.
Lower TTL to 300 (48h before). Update A + MX records. Wait 5-30 min. Keep old server 30 days.
Verify websites, emails, databases, cron. Sync any changes. Restore TTL after 7-30 days.
Every WHM VPS includes free migration assistance for up to 20 cPanel accounts.
Ready to Migrate to WHM VPS?
Get free migration assistance with every WHM VPS purchase. Up to 20 cPanel accounts migrated free, zero downtime.
💬 Get Free Migration 🎯 View WHM VPS Plans