Migrations

Last updated

The hub for every migration source is Migrate to Jabali Panel, which links each source’s own guide. This page keeps the source matrix and per-source notes. It lives at /jabali-admin/migrations.

Supported sources

A source can be ingested from an uploaded archive or, for the control-panel sources, pulled live over SSH (the panel reads the source with the vendor’s own read-only CLI, then rebuilds destination-side).

SourceFormatStatus
cPanelcpmove-<user>.tar.gz or live SSH✅ — each database gets its own database user with a new password; with Carry over source passwords on, the source’s MySQL users and password hashes are recreated too, so migrated apps keep working.
DirectAdminDA backup tarball or live SSH✅ — see docs/user/directadmin-migration.astro (legacy) for source-side prep notes.
HestiaHestia v-backup-user tarball (<user>.<ts>.tar[.gz]) or live SSH✅ — files, DBs, DNS (incl. SRV + CAA), and apps (e.g. Nextcloud) restore end-to-end; the account Contact Name (FNAME/LNAME) carries onto the user. Mail is the Exim→Stalwart subset (see below).
WHMWHM-level dump (multiple cpmoves in one)🟡 — same caveats as cPanel per-user.
Plesklive SSH (subscriptions)✅ — reads databases, DNS, and reseller customers + service plans via plesk bin / wp-toolkit read-only CLI, then rebuilds destination-side. Read-only on the source. PostgreSQL databases are not migrated.
CloudPanellive SSH (site users)✅
CyberPanellive SSH (websites)✅
Jabali → Jabalilive SSH (accounts)✅ — move accounts between Jabali servers.
IMAP (Gmail, M365, generic)Live IMAP over TLS✅, per-mailbox. Messages + folders + flags via FETCH into staging Maildir, then JMAP import into Stalwart. Requires an app-password.

Workflow

  1. Either upload an archive to /jabali-admin/migrations (or scp to /var/lib/jabali/migrations/incoming/), or point the wizard at a live SSH source (host, port, credentials) for the control-panel importers.
  2. The pipeline runs four phases:
    • Analyze: inspect the archive, list users / domains / DBs / mailboxes / DNS zones / cron jobs.
    • Fix-perms: apply chown / chmod normalisations expected by Jabali’s per-user pool layout.
    • Validate: DB password hashes parseable, DNS zone files valid, mail accounts consistent.
    • Restore: create the panel user, ingest each domain / DB / mailbox / cron, hand off to the reconciler.
  3. Watch progress at /jabali-admin/migrations/<id>.

Per-source notes

cPanel

  • 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. Turn on Carry over source passwords (--preserve-source-state on the CLI) to also recreate the source’s MySQL users with their original password hashes (bcrypt in cPanel ≥ 11.96) and grants, so apps that hold those credentials keep authenticating. PostgreSQL databases are not migrated; the migration report lists each one.
  • Email accounts: cPanel uses Dovecot+Exim, Jabali uses Stalwart. Each mailbox gets a new random password, which is not shown, unless Carry over source passwords keeps a source hash Stalwart can verify. The migration report lists the mailboxes that need a new password: set one for each (Rotate password) and send it to its owner.
  • DKIM keys: imported.
  • DNSSEC: not migrated automatically (key formats differ); re-enable per-domain in Jabali.

DirectAdmin

  • See docs/user/directadmin-migration.astro for the source-side prep (run da backup-all etc.) before upload.

Hestia

  • BIND zones translated to PowerDNS schema rows — A/AAAA/CNAME/MX/TXT/SRV (priority in the pdns prio column) / CAA all import; the source SOA is dropped (pdns generates its own).
  • Hestia’s web/<domain>/public_html docroot layout is handled for both the file split and the app-config scan (differs from the native domains/<domain>/public_html).
  • Resource types are preserved per source facet: Hestia lists web dirs and DNS zones independently, so a web dir with no source zone imports as a Web Domain only (dns_disabled, no managed PowerDNS zone), a DNS zone with no web dir imports as a DNS Zone only (web_disabled, no nginx vhost/PHP), and a domain in both imports full-facet. Other importers (cPanel, DirectAdmin, Plesk, CloudPanel, CyberPanel) create every domain full-facet unchanged.
  • The account Contact Name (user.conf FNAME/LNAME) carries onto the created jabali user’s name.
  • Exim → Stalwart routing rules: forwards + autoresponders ported; complex Exim ACL rules need manual re-implementation.

Offline restore (CLI):

jabali migrate restore --hestiacp --file /path/<user>.<ts>.tar --source-user <user> \
  --target-email <email> --target-password <pw>
  • A low-disk host aborts before staging or creating the user (disk preflight).
  • Re-run the same command to resume; add --retry-from-scratch (alias --fresh) to wipe the job and re-run the whole pipeline (recreates a deleted target user).
  • A restore that leaves a site returning 5xx (a crashing app) ends degraded, not done; a transient 0 during nginx/FPM convergence does not degrade it.

Plesk

  • Live SSH pull — no backup tarball required. Jabali runs plesk bin subscription --list to enumerate subscriptions, then plesk bin domain --info, database --info, dns --info, mail --info, and reads WordPress installs via WP Toolkit for each one.
  • Read-only on the source: every command Jabali executes on the Plesk host is --list / --info / -format json. Nothing is created, modified, or deleted on the source panel — you can safely dual-run until you cut DNS over.
  • What imports: subscriptions → panel users, domains, MySQL databases (dumped over SSH), DNS zone records, mailboxes (via IMAP APPEND / Maildir where reachable), WordPress installs (with detected wp-config credentials rewritten), and per-subscription cron jobs (imported disabled, for you to review).
  • What is deferred: PostgreSQL databases are not migrated; the migration report lists each one. Reseller hierarchies are flattened — every subscription becomes a top-level Jabali user.

WHM

  • Splits into per-cpmove jobs internally; each runs through the cPanel pipeline.

IMAP (Gmail / Microsoft 365 / generic)

  • Per-mailbox, not per-account. A single job carries one or more (remote_host, remote_port, remote_username, remote_secret) tuples plus the local target mailbox. Bulk moves use a CSV (--csv on the CLI).
  • Credentials: Gmail and M365 both require an app-password: a plain password with 2FA on will fail at LOGIN. The secret is stored in the encrypted migration-secrets vault, never in a DB row.
  • Folder mapping is automatic for INBOX / Sent / Drafts / Trash / Junk / Archive via IMAP SPECIAL-USE. Custom folders are recreated with the same name.
  • Resumable: last-seen UID is tracked per folder, guarded by UIDVALIDITY, so a re-run continues instead of restarting. Message-ID dedup is performed at JMAP import time.
  • What migrates: messages, folders, flags and INTERNALDATE. Aliases, contacts, calendars and shared-mailbox ACLs are not migrated.
  • CLI: jabali migrate imap --host imap.gmail.com --port 993 --user [email protected] --to alice@panelhost --password-stdin. Runs the same 4-stage pipeline (connect+validate → fetch → import → verify).

Limitations

  • Each pipeline is “stop-the-world” for the destination user while it runs.
  • Plesk / CloudPanel / CyberPanel / Jabali are live-SSH-only — the panel reads the source over SSH; there is no offline backup-archive import for them.
  • No CSF/LFS rule translation. CrowdSec is the IP-trust source on Jabali; carry over allowlists manually.
  • PostgreSQL databases are not migrated. cPanel / WHM / Plesk sources may hold PostgreSQL databases; the migration report lists each one so you can move them by hand.

Frequently asked questions

cPanel
Each database gets its own new database user and password, and app configs such as WordPress are pointed at it. With 'Carry over source passwords' on, the source MySQL users and hashes are recreated instead. Mailboxes get new random passwords unless a source hash can be carried over, and the migration report lists the mailboxes that need a new password. DKIM keys are imported. DNSSEC is not migrated; re-enable it per domain.
DirectAdmin
Do the source-side prep before upload, for example by running `da backup-all`.
Plesk
Live SSH pull, no backup tarball needed. Subscriptions, domains, MySQL databases, DNS, mailboxes, WordPress installs and cron jobs are imported. Every command run on the source is read-only (`--list` / `--info`), so nothing changes there. PostgreSQL databases are skipped for now.
Hestia
BIND zones become PowerDNS records, including SRV and CAA. Exim forwards and autoresponders are ported to Stalwart; complex Exim ACL rules need manual re-implementation.
IMAP (Gmail / M365 / any provider)
Migration runs per mailbox, not per account. Provide the remote host, port, username and an app password, since a plain password fails when 2FA is on. Standard folders map automatically and custom folders are recreated as-is. Re-runs resume from the last seen UID in each folder.
WHM
WHM dumps are split into one job per cpmove, and each job runs through the cPanel pipeline.