Plan a cPanel move around the account’s actual services.

Map the account before exporting

List primary and additional domains, document roots, PHP requirements, database names/users, mailboxes, forwarders, filters and cron entries. Identify application data outside the visible website root.

Keep an original source backup and separate usable exports. cPanel’s own full-backup restoration path does not establish compatibility with another control panel. Do not upload a complete account archive into a website document root.

Rebuild the account’s destination services

Create the intended EzePanel account and package, then map every source domain to its intended document root. Check each application’s PHP version, extensions and database requirements before moving its content.

The current product provides the destination hosting tools. A dedicated cPanel archive importer or one-click account transfer is not currently provided; broader migration tooling is Planned.

Use the home and SQL exports for their own purpose

Keep the original cPanel account archive as source recovery material. Transfer the selected website files separately and create the target database and user before importing a usable SQL export. Update application paths and full database credentials.

Preserve the source copy and inspect the import result. The EzePanel SQL import accepts .sql/.sql.gz within its upload limits; it is not a full control-panel archive importer or a guarantee of atomic rollback.

Reconcile mail rules and public records

Inventory mailboxes, forwarders and filters separately from website files. Recreate supported target mailbox identities and DNS records; agree how message history and any unmatched mail behavior will be handled. Review cron and FTP/SSH access per account.

Do not assume portable password hashes, mail filters, forwarding rules, certificates or account paths. Reissue or install eligible SSL through the supported target process and verify coverage. Keep external registrar and DNS authority clear.

Use the shared cutover checklist.

Verify the target application and services, agree final synchronization, then change traffic with a recovery decision already prepared. Retain the source until preservation and recovery requirements are satisfied.