How to migrate from cPanel to intoPanel

A calm, step-by-step plan for moving websites, mail and DNS from a cPanel server, with no surprises for your customers.

Before you start#

A good migration is mostly preparation. Plan for three moments: preparing (a day or two before), moving (per batch of accounts), and switching DNS (after each batch is checked).

You need:

  • An intoPanel server, installed and licensed, with the PHP versions your websites use.
  • Root SSH access to the cPanel server, or cPanel backup files of the accounts.
  • Access to the DNS of the domains, or to the nameservers they use.

Step 1: Lower the DNS TTL#

A day before the move, lower the TTL of the domains' records to 300 seconds (5 minutes). When you switch, visitors and mail servers then follow the change within minutes instead of hours.

Step 2: Match packages and PHP versions#

On the intoPanel server, install the PHP versions the accounts use under Software → PHP Versions, with the extensions they need. Server Migration can copy cPanel's packages for you; accounts restored from backups are put on a package of the same name, or one made from their limits.

Step 3: Move the accounts#

Choose one of two ways:

  1. In the intoPanel admin area, open Migration and Restore → Server Migration.
  2. Enter the cPanel server's address and SSH port, and sign in with its root password or this server's SSH key.
  3. Click Connect and Scan, tick the accounts to move, and start. Several accounts are copied side by side, each with its own progress.

Server Migration brings websites, databases, mailboxes, DNS records, cron jobs, FTP accounts and the panel password.

From backup files#

  1. On cPanel, make full backups of the accounts (cpmove-user.tar.gz), or use the server's backup folder.
  2. Copy them to /var/backups/intopanel on the intoPanel server, keeping the folder layout, or upload single files on Restore Backups.
  3. Restore the accounts. Each restore has a log of what was brought across and anything left out.

Step 4: Test before you switch#

Point your computer at the new server with the hosts file, for example:

203.0.113.10  example.com www.example.com

Open the websites, sign in to WordPress, send a test form, and sign in to webmail. Check the restore log for cron jobs that were left out and any database warnings.

Step 5: Switch DNS#

Change the A records, or the domain's nameservers, to point at the intoPanel server. With the low TTL, traffic moves within minutes. Automatic SSL issues free certificates as soon as each domain points at the server.

Step 6: Clean up#

Raise the TTL back to its normal value, check Mail Deliverability for SPF, DKIM and DMARC, run the Security Checkup, and set up backups to a remote destination. When every account is confirmed working, cancel the old server.

Frequently asked questions

How long does a migration take?

Mostly as long as copying the data takes. Small accounts move in minutes; large mailboxes and databases take longer. Moving several accounts side by side shortens the total time.

Will my customers need new passwords?

No. Panel passwords, mailbox passwords and database user passwords come across.

Are SSL certificates moved?

Certificates are issued again, free, by Automatic SSL once the domains point at the new server.

Can intoPanel migrate from DirectAdmin or Plesk?

Server Migration connects to cPanel & WHM and intoPanel servers. From other panels, move websites and databases by hand or convert backups to cPanel's format first.

Try intoPanel on your own server

A free trial licence unlocks every feature. Install on a fresh AlmaLinux, Rocky Linux, Ubuntu or Debian server and see it for yourself.