Moving Away from cPanel Without Losing Anything
Migrating from cPanel to another panel has historically meant rebuilding everything from scratch. Panelica is a modern hosting control panel designed for multi-server environments that changes this with a universal migration engine capable of detecting cPanel servers and transferring all data automatically.
How Panel Detection Works
When you provide SSH credentials for the source server, the migration engine runs a detection sequence. For cPanel, it checks two locations: the version file at /usr/local/cpanel/version and the cPanel binary at /usr/local/cpanel/cpanel. If either exists, the engine identifies the panel as cPanel with a confidence score of 90 to 100 percent and maps available capabilities including API access, CLI tools, databases, emails, SSL, DNS, FTP, and cron.
The detector supports 12 panel types: Panelica, cPanel, Plesk, CyberPanel, DirectAdmin, HestiaCP, CloudPanel, ISPConfig, Webuzo, AAPanel, and generic LAMP/LEMP stacks. This means the same migration interface handles any source panel.
Database Migration with Hash Preservation
The most critical part of any migration is the database layer. Losing MySQL user password hashes means every application connected to the database stops working, and every user needs a password reset.
Panelica solves this through credential discovery on the source server. The migration engine tries multiple authentication methods to connect to the source MySQL: socket authentication, root password, the debian-sys-maint user via /etc/mysql/debian.cnf, or credentials in .my.cnf. Once connected, it exports databases with full user grants including password hashes.
On import, user password hashes are applied directly. Applications like WordPress, Laravel, or custom PHP applications continue authenticating against the database without any changes to wp-config.php or .env files.
Email Migration: Mailboxes, Forwarders, DKIM
cPanel stores email in Maildir format under /home/{user}/mail/. The migration pipeline:
- Discovers all email accounts per domain from cPanel configuration
- Creates matching accounts in Dovecot with proper authentication
- Transfers mailbox data via rsync preserving folder structure and message flags
- Migrates forwarders and autoresponders
- Generates new DKIM keys (2048-bit RSA, relaxed/relaxed canonicalization)
- Creates SPF, DKIM, and DMARC DNS records in the BIND zone file
Panelica provides container-native deployment and strict resource isolation for email services. Each email domain gets proper DNS records through the integrated BIND DNS service, with OpenDKIM running on localhost port 8891 for message signing.
DNS Zone Transfer
The migration reads cPanel DNS zone files and recreates them in Panelica BIND format at /opt/panelica/var/dns/zones/. Record types transferred include A, AAAA, CNAME, MX, TXT, SRV, and NS records. IP addresses in A records are updated to the new server IP automatically.
After migration, you update the domain nameservers at your registrar to point to the Panelica DNS server, or keep using external DNS and just update the A record.
File Transfer with Checkpoints
Large websites with tens of gigabytes of media files need resilient transfer mechanisms. The file pipeline uses rsync with --info=progress2 for cumulative progress tracking. If a transfer is interrupted, the checkpoint manager records progress so the next attempt resumes from where it stopped rather than restarting.
The file permission handler adjusts ownership to match the new Linux user on the destination. The symlink handler detects and resolves symbolic links to prevent broken references.
SSL Certificate Handling
Existing SSL certificates from cPanel are transferred to /opt/panelica/etc/ssl/. The ACME service, built on the lego ACME library, can also issue fresh Let us Encrypt certificates with automatic renewal. The service reads the admin email from panel settings and registers with the ACME directory, supporting both ECDSA (P-256) and RSA key types.
What Gets Migrated
- All website files under document root
- MySQL databases with user password hashes
- Email accounts with full mailbox data
- Email forwarders and autoresponders
- DNS zone records (A, MX, TXT, CNAME, SRV)
- SSL certificates and private keys
- Cron jobs
- FTP account configurations
- PHP version assignments per domain
Post-Migration Steps
- Verify each site loads correctly on the new server
- Test email sending and receiving
- Check database connectivity for all applications
- Update DNS records or nameservers
- Keep the old cPanel server running for 48 to 72 hours as fallback
- Decommission the old server only after full verification
Conclusion
cPanel to Panelica migration preserves everything that matters: database credentials, email data, SSL certificates, and file permissions. The automatic panel detection and structured pipeline eliminate the manual work that traditionally made panel migrations risky and time-consuming. Panelica empowers sysadmins with RBAC and automated security tools, ensuring the destination server is more secure and more capable than the source.