Control panel migration is complex: accounts, email, DB, and files. Use official migration tools or third-party scripts. Backup everything first; test in staging. Plan DNS and MX cutover.
What you are migrating
- Accounts: Each cPanel/Plesk account (domain, user, home dir). Map to the target panel's account structure. Passwords may need reset or sync; document which account maps to which.
- Web files: Document root, subdomains, addon domains. Preserve permissions and ownership. Watch for symlinks or paths that differ between panels.
- Databases: MySQL/MariaDB databases and users. Export (dump) and import on target; recreate DB users and grants. Test app connectivity after migration.
- Email: Mailboxes, forwards, filters, and DNS (MX, SPF, DKIM if stored in panel). Email data (IMAP/POP) must be copied or synced. Plan MX cutover so mail flows to new server after cutover; reduce TTL in advance.
- DNS: Zones hosted in the panel. Export zone files and import to target (or to external DNS). Ensure all records (A, AAAA, MX, TXT, CNAME) are present. If DNS is external, no zone migration but MX/glue may change.
Backup and tools
- Backup first: Full backup of source (cPanel backup or Plesk backup, or manual: files + DB dumps + mail). Keep a copy off the source server. Verify backup restores (e.g. to a test box) before you rely on it.
- Official tools: cPanel and Plesk offer migration tools (e.g. Plesk Migrator can pull from cPanel). Run in staging first; fix any failures or missing data. Document steps and options (e.g. sync vs one-time).
- Third-party: Scripts or services (e.g. CMS2CMS for sites, or custom rsync + import scripts) can fill gaps. Test thoroughly; some settings (e.g. PHP version per domain, cron jobs) may need manual re-creation.
Staging and cutover
- Staging: Migrate to a staging server with the target panel. Verify sites load, DBs connect, and email works (or at least credentials and structure). Fix compatibility issues (PHP version, extensions, paths). Use staging to train and document the cutover runbook.
- DNS and MX cutover: Lower TTL for relevant records (e.g. 300 s) days before. At cutover, point A/AAAA (and MX if mail is on the same server) to the new server. Or use a migration tool that syncs and then you switch DNS once. Monitor for resolution and mail delivery.
- Rollback: If something goes wrong, you can point DNS back to the old server if you have not decommissioned it. Keep old server and backups until you are confident the new setup is stable.
Summary
Control panel migration is complex: accounts, email, DB, and files. Use official migration tools or third-party scripts. Backup everything first; test in staging. Plan DNS and MX cutover; document and have a rollback plan.
