Core Panel

Planning a cPanel Migration: What Must Move

SA
Written by Shakeel Ahmed Lead Architect · Published Aug 27, 2026 · 7 min read
Planning a cPanel Migration: What Must Move
On this page · 5 sections

A hosting migration fails when the team copies public files but overlooks the services and state around them. Build the inventory before selecting the transfer method.

Website and application state

Record domains, aliases, redirects, document roots, runtime versions, dependencies, writable paths, environment configuration, queues, workers, webhooks, and external storage.

Data and messaging

Inventory databases, users, privileges, mailboxes, aliases, forwarding, filters, queues, SPF, DKIM, DMARC, and any application that sends through the server.

DNS and certificates

Export every zone and custom record, note delegation and TTLs, identify provider-managed reverse DNS, and decide whether certificates will be transferred or reissued.

Automation and access

Capture cron jobs, SSH and SFTP users, reseller permissions, monitoring checks, backup schedules, API clients, and integrations that depend on the old host or IP address.

Cutover and rollback

Define final synchronization, validation owners, DNS changes, monitoring, rollback thresholds, and how long the source remains available. Never start without verified backups.

Continue with the complete cPanel migration guide, including test-server validation, cutover gates, rollback criteria, and the migration-planning contact path.

Related posts

More articles are coming soon.

Stay in the loop

New posts and release notes, delivered to your inbox. No spam.

Ready to switch?
14-day free trial
Get Started