Migrate from HestiaCP to Jabali Panel: files, DBs, DNS, mail

Last updated

The HestiaCP ingest path. Status: partial, files, databases, DNS, and a subset of mail are supported. Complex Exim ACL rules require manual re-implementation.

Source archive

HestiaCP’s per-user backup produced by:

v-backup-user <user>

The resulting archive lands under /backup/<user>.<timestamp>.tar.

What gets migrated

AssetBehavior
User accountRecreated.
Home directoryCopied.
Web domainsCreated as Domain rows. The vhost is rendered fresh from the panel template, Apache/nginx fragments from the source are not preserved.
DNS zonesBIND zones translated to PowerDNS rows.
MySQL databasesRestored. Each 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, HestiaCP’s database users are also recreated with their original password hash (from each database’s db.conf), as database users of the account. A name that already exists on this server is not used; the migration report lists it.
PostgreSQL databasesNot migrated; the analysis and the migration report list each one.
Email accountsCreated in Stalwart with a new random password each, or with the source password when Carry over source passwords is on (Hestia’s bcrypt hashes carry over). The migration report lists the mailboxes that need a new password.
Forwarders / autorespondersTranslated to Stalwart.
Cron jobsTranslated to systemd-user timers via the allowlist filter.

What requires manual work

  • Exim ACL rules — HestiaCP often carries non-trivial Exim acl_smtp_data / acl_check_recipient rules. These do not translate directly to Stalwart’s expression filter syntax; rewrite under Server Settings → Mail → Stalwart expressions.
  • Per-domain webmail identities — Roundcube identities on the HestiaCP source are not migrated; the destination serves its own Bulwark webmail instead.
  • Spamassassin / rspamd thresholds — Stalwart spam scoring is independent, and its scores are not on the same scale. If mail lands in Junk too often after the move, raise the Junk threshold under Server Settings → Email → Spam filter (see Spam filter); a mailbox can also add trusted senders to its webmail contacts.

Operator workflow

  1. Produce a per-user backup on the Hestia host.
  2. Upload to /jabali-admin/migrations.
  3. Analyze → review the report for any Exim ACL warnings.
  4. Restore.
  5. For each Exim ACL warning, manually re-author the equivalent Stalwart expression filter.
  6. Set new passwords for the mailboxes the report lists, and send them to their owners.
  7. Issue SSL via the per-domain SSL toggle.

Limitations

  • Hestia Apache+nginx fronted setups: Hestia frequently runs nginx in front of Apache. Jabali serves nginx directly with PHP-FPM. Apache-specific directives in .htaccess files that depend on mod_rewrite translate; directives that depend on mod_php or mod_setenvif do not and must be rewritten.
  • Hestia firewall (iptables) rules: not migrated. Use UFW plus CrowdSec for the equivalent surface.

Audit

Standard per-phase audit rows.

Frequently asked questions

Can I migrate a HestiaCP account to Jabali Panel?
Yes. Jabali Panel's Migrations section accepts HestiaCP per-user backups produced by `v-backup-user `. Files, MariaDB and PostgreSQL databases, DNS zones (translated from BIND to PowerDNS), and a subset of mail configuration transfer. Complex Exim ACL rules require manual re-implementation as Stalwart expression filters.
What is the HestiaCP backup command?
`v-backup-user ` on the HestiaCP host produces `/backup/..tar`. It runs against a single user; for a whole-server move, run it once per user in a shell loop, then rsync the resulting archives to `/var/lib/jabali/migrations/incoming/` on the Jabali Panel host.
Which HestiaCP features do not migrate automatically?
Custom Exim ACL rules (`acl_smtp_data`, `acl_check_recipient`) do not translate directly and need to be re-authored as Stalwart expression filters. Per-domain Roundcube identities do not carry over (Jabali serves its own Bulwark webmail instead). Spamassassin/rspamd threshold overrides need recalibration in Stalwart's spam scoring config. Hestia iptables rules are not migrated — use UFW + CrowdSec for the equivalent surface.
Does Hestia's Apache+nginx setup translate to Jabali?
Jabali serves nginx directly with PHP-FPM — there is no Apache. `.htaccess` files with `mod_rewrite` directives translate (nginx supports rewrite via the panel's vhost template). Directives that depend on `mod_php` or `mod_setenvif` do not translate and need to be re-implemented in the nginx `location` block or the PHP-FPM pool config.
Are PostgreSQL databases migrated from HestiaCP?
Yes. HestiaCP is one of the sources that ships PostgreSQL alongside MySQL/MariaDB. The Jabali pipeline restores Postgres databases into the panel-managed PostgreSQL instance with role and password metadata intact where the hash format is compatible.