cPanel migration: move accounts from cPanel to Jabali Panel
Last updated
The cPanel ingest path. Status: production-supported.
Source archive
The standard cpmove-<user>.tar.gz produced by cPanel’s Backup Wizard or pkgacct. Either format works.
For server-wide migration, produce a separate cpmove per account or feed a WHM-level dump through the WHM pipeline.
What gets migrated
| Asset | Behavior |
|---|---|
| Linux user account | Recreated under the destination panel; UID may differ. |
| Home directory contents | Copied to /home/<user>/. |
| Hosted domains | Created as panel Domain rows; vhosts rendered by the reconciler. |
| Subdomains | Created as Domain rows (or aliases, per heuristic on the cPanel addon_domains map). |
| DNS zones | Translated to PowerDNS schema rows. |
| MySQL databases | Restored via mysql against panel-managed MariaDB. |
| MySQL users | Each restored database gets its own database user, <user>_<database>, with a new password, and WordPress, Joomla, Drupal, Magento and ITFlow configs are pointed at it. With Carry over source passwords on (--preserve-source-state on the CLI), the source’s MySQL users are also recreated with their original password hash and their grants on the restored databases, so app configs keep their credentials. They become database users of the account: the panel shows them, can change their passwords, and removes them with the account. The import never takes over a MariaDB account that already exists on this server, other than one it made for this account: such a database gets no user of its own, such a source user is not recreated, and the migration report lists each one. |
| PostgreSQL databases | Not migrated; the migration report lists each one. |
| Email accounts | Created in Stalwart. By default each mailbox gets a new random password, which is not shown; the migration report lists every mailbox that needs a new password. With Carry over source passwords on, a mailbox keeps its source password when Stalwart can verify the source hash; otherwise it gets a new password too. |
| DKIM keys | Imported as-is so mail flow is uninterrupted. |
| Mailing lists | Not migrated, Mailman is not currently in the panel; the affected accounts surface in the migration report. |
| FTP accounts | Mapped to SFTP via Match Group + the user’s SSH key vault. cPanel FTP-only passwords do not transfer (FTP is plaintext; the panel does not host FTP). |
| Cron jobs | Translated into systemd-user timers if the command passes the Cron allowlist. Disallowed commands surface in the report; the operator may add them to the allowlist and re-run. |
| SSL certificates | Re-issued by the reconciler via Let’s Encrypt; the cPanel cert is not migrated (paths and renewal hooks differ). |
What is not migrated
- WHMCS / Reseller-only configuration (Jabali has no reseller construct).
- cPanel “Backup Manager” snapshots (use the new panel’s Backups going forward).
- Spamassassin per-mailbox rules (Stalwart handles spam scoring server-side).
- Apache
.htaccessfiles referencing modules nginx does not have (mod_rewrite is supported via the nginx vhost template; mod_php directives are dropped).
Commands cheat sheet
Every command below is run on the source cPanel/WHM host unless noted:
# Per-account archive (Backup Wizard equivalent, headless)
/scripts/pkgacct <username>
# -> /home/cpmove-<username>.tar.gz
# Whole-server dump (one cpmove per account)
/scripts/cpbackup
# Copy archive to Jabali Panel host with resume
rsync --partial --progress cpmove-<username>.tar.gz \
root@<jabali-host>:/var/lib/jabali/migrations/incoming/
On the Jabali Panel host:
# Offline restore of one cpmove (creates the job, stages the archive, runs the pipeline)
jabali migrate restore --cpanel --file /var/lib/jabali/migrations/incoming/cpmove-<username>.tar.gz \
--source-user <username> --target-email <email> --target-password <password>
# Run it again to resume; wipe the job and start over from the analyze step
jabali migrate restore --cpanel --file <archive> --retry-from-scratch
# Also carry source passwords (MySQL user hashes, and Stalwart-verifiable mailbox hashes)
jabali migrate restore --cpanel --file <archive> --preserve-source-state
# List sites in sites-enabled that have no panel row, then delete them
jabali domain prune-orphans
jabali domain prune-orphans --apply
The wizard at /jabali-admin/migrations runs the same pipeline with an Analyze step before Restore.
Cutover playbook (minimise DNS-propagation downtime)
The general shape of a low-downtime cutover:
- T-48h — Lower TTLs. At the DNS provider (Cloudflare, Route 53, Namecheap, whichever hosts the zone), drop the record TTLs on the domains you’re moving to
300seconds. Wait 24h so resolvers pick up the shorter TTL. - T-1h — Freeze writes on the source. Put the source cPanel account into maintenance (or ask the tenant to stop posting/uploading). Prevents split-brain between old and new hosts.
- T-1h — Generate the cpmove.
pkgacct <user>on the source host. - T-45min — Ship the archive.
rsync --partialto the Jabali Panel host. - T-30min — Restore. Analyze, then Restore. Watch the per-phase log.
- T-15min — Smoke-test on the new host. Hit the new server IP directly with a
Host:header override:
Load WordPress admin, log a mailbox in via Bulwark webmail, runcurl -sI --resolve example.com:443:<new-ip> https://example.com/ | headmysql -u <migrated-user> -p<pw> -e "SELECT 1;". - T-0 — Repoint DNS. Update A/AAAA/MX at the registrar. Given the 300s TTL, most of the world sees the new host within 5-10 minutes.
- T+1h — Issue SSL. Once DNS resolves, toggle the per-domain SSL switch. Certbot issues via the panel’s HTTP-01 challenge on port 80.
- T+24h — Restore original TTL. Bump TTLs back to
86400at the DNS provider.
The end-to-end guide on the blog tells the same migration as a narrative and links back to this page for the playbook.
MySQL users and passwords
By default each restored database gets its own database user, <user>_<database>, with a new password, and the WordPress, Joomla, Drupal, Magento and ITFlow configs are pointed at it. Apps with credentials hardcoded elsewhere need those updated.
Turn on Carry over source passwords (--preserve-source-state on the CLI) and the source’s MySQL users are also recreated with their original password hashes (bcrypt in cPanel ≥ 11.96) and their grants on the restored databases. Then:
- Legacy PHP apps whose DB user is hardcoded in a config file keep working.
- The users become database users of the account: the panel shows them, can change their passwords, and removes them with the account.
- The import never takes over a MariaDB account that already exists on this server, other than one it made for this account. The migration report lists each one it skipped.
- Only the DB host in the app config may need updating (from
localhostto the panel’s socket path or127.0.0.1).
Migrating multiple cPanel accounts at once
For >1 account, produce one cpmove per user and restore them one after another, or use the WHM pipeline:
# Source: one archive per account
for user in $(ls /var/cpanel/users/); do
/scripts/pkgacct "$user"
done
# Batch-ship
rsync --partial --progress /home/cpmove-*.tar.gz \
root@<jabali-host>:/var/lib/jabali/migrations/incoming/
# On Jabali: restore each account in turn
for f in /var/lib/jabali/migrations/incoming/cpmove-*.tar.gz; do
jabali migrate restore --cpanel --file "$f" --target-email <email> --target-password <password>
done
Run them one after another: the MySQL import is the CPU hotspot.
Operator workflow (short version)
- Produce the
cpmove-<user>.tar.gzon the cPanel host. - Upload to
/jabali-admin/migrations(web) or SCP to/var/lib/jabali/migrations/incoming/. - Click Analyze on the row. Review the report.
- Click Restore.
- After completion, set a new password for each mailbox the report lists and send it to the owner through a channel you trust.
- Update DNS at the registrar to point to the new panel.
- Issue SSL via the per-domain SSL toggle.
Troubleshooting
“Analyze” fails with unrecognized cpmove format.
The archive was produced by an unsupported cPanel version (< 11.90 has legacy format differences). Regenerate on the source with pkgacct --version ≥ 11.90.
MySQL restore fails: Error: Duplicate entry '<db-name>' for key 'PRIMARY'.
The destination already has a database with the same name. Either drop the destination DB first (DROP DATABASE <db-name>;) or rename the incoming DB in the Analyze report before Restore.
Mailboxes restore but IMAP shows “authentication failed”.
Expected, unless the mailbox kept its source password. Migrated mailboxes get a new random password, which is not shown, and the Restore report lists them. Set a new password for each listed mailbox and send it to its owner. To keep source passwords, run the migration with Carry over source passwords (--preserve-source-state); it carries hashes Stalwart can verify.
Certbot fails after cutover with no valid A record.
DNS hasn’t propagated. Run dig example.com A @1.1.1.1 and wait until the answer matches the new IP. Then retry the SSL toggle.
A domain restored but the site shows a “Welcome to nginx” page. The vhost render is queued in the reconciler (60-second interval). Wait one interval, then reload. If it persists, check the domain’s status in the panel.
Audit
Each phase emits an audit row; the per-domain creation also writes one domain.create row per domain.
Related reading
- cPanel migrations to Jabali Panel: end-to-end guide — narrative walkthrough of the migration. The cutover playbook and the MySQL users and passwords reference are on this page.
- An open-source cPanel alternative for Debian 13 — the case for leaving cPanel and what Jabali replaces it with.
- DirectAdmin migration — same pipeline, DirectAdmin
da backup-userarchive as input. - HestiaCP migration — same pipeline,
v-backup-userarchive as input. - WHM migration — server-wide dump, iterates the cPanel pipeline per-account.