Moving a server to a new control panel used to mean nights of manual work: exporting databases one by one, re-creating DNS zones by hand, resetting every MySQL password because the hash format changed, and hoping you did not miss a Cron job. Panelica's built-in migration tool handles all of this, including something most panels do not support at all -- reseller account hierarchies.
- cPanel -- full account migration including databases, DNS, email, and SSL
- Plesk -- supported on both Debian/Ubuntu and RHEL-family servers (AlmaLinux, Rocky Linux)
- CyberPanel
- CloudPanel
- DirectAdmin
- Panelica to Panelica -- for moving between your own Panelica servers
This is the part that matters if you run a reseller hosting operation. When you migrate from a source panel, Panelica does not flatten everything into a single user level. It reads the reseller-to-customer relationships from the source and recreates them correctly:
- Reseller accounts become RESELLER-role users in Panelica, with their own resource quotas and the ability to manage their own end-users.
- Customer accounts under each reseller become USER-role accounts associated with the correct reseller.
- The source mapping is presented as a selection card during the migration setup -- you review the discovered hierarchy and confirm before anything is created.
If your source panel does not distinguish resellers from regular users, Panelica maps all accounts to USER-level and you can adjust roles after migration.
Two things commonly break during a panel migration: database access and application configuration files.
MySQL password hash preservation -- Panelica transfers MySQL user hashes directly from the source server using the External API. Application database passwords are not reset. WordPress, Joomla, Magento, and custom applications continue to connect to their databases immediately after migration without any file edits.
wp-config.php and .env files are untouched -- Configuration files are copied as-is. Panelica does not rewrite database names, usernames, or connection strings in application files.
Resumable file transfer -- Files are transferred using rsync. If the connection drops mid-transfer, the migration resumes from where it left off rather than starting over.
Domain-scoped database discovery -- The migration engine correctly identifies which databases belong to which domain (up to 32 databases per domain), including cases where the database name does not obviously match the domain name.
DNS and SSL transfer -- DNS zone records are imported and recreated in Panelica's BIND zone. SSL certificates are re-issued via Let's Encrypt after migration, so sites are served over HTTPS immediately.
- Connect -- enter the source server's address and credentials in Migration > New Migration.
- Health Check -- the panel verifies it can reach the source server and read account data.
- Discover -- the migration engine inventories all accounts, domains, databases, and email on the source.
- Map -- review the discovered hierarchy and confirm how accounts should map to Panelica roles.
- Migrate -- the panel creates users, provisions domains, transfers files, imports databases, imports email, and issues SSL certificates.
- Verify -- a post-migration check confirms that web and mail are responding correctly on the destination server.
Each step is checkpointed. If migration is interrupted at any point, you can resume from the last completed step.
The migration tool is available under Migration in the panel sidebar. You will need SSH credentials for the source server and, for database hash preservation, the source server must be reachable on port 3002 (Panelica-to-Panelica) or via its control panel's export API.
If you are migrating from a specific source panel and run into something unexpected, post a reply with the source panel name, OS, and what step it failed on. We will take a look.
The Panelica Team