cPanel to Webuzo: Self-Managed Import and Verification

Webuzo provides cPanel import tools, but the supported workflow depends on the Webuzo release and your source access. This is a self-managed cross-panel conversion, not InterServer’s complimentary migration service. That service is limited to matching cPanel or DirectAdmin web hosting transfers; VPS and dedicated-server migrations are not offered.

Separate current Webuzo from legacy Breadbasket instructions

The older Breadbasket/Webuzo v2 importer was a single-user workflow with version-specific username, overwrite and email limitations. Do not apply its paths or “email is not imported” statement universally to current multi-user Webuzo. Check the destination release, licensing and current importer documentation before transferring data.

Do not install a panel over a live server simply to begin a migration. Prepare a separate supported destination and protect its existing data. Inventory source accounts, domains, databases, mail and application requirements, then resolve username/domain conflicts and capacity limits.

Choose the appropriate current import route

The current Webuzo admin import guide distinguishes WHM-credential, end-user-credential and stored-backup routes. Use the route matching your actual permissions; a cPanel account login is not source-server root access.

1. Prepare a complete supported cPanel account archive when using a backup route. Keep it private and transfer through authenticated encryption; do not publish an HTTP backup link.
2. In the destination’s current admin import interface, identify the source or exact local backup and select only the intended users/plan.
3. Inspect collision and overwrite choices. “Delete and overwrite” is destructive, not a routine way to clear a warning. Preserve destination recovery copies and use an intentional replacement only when authorized.
4. Start the approved import and use its Logs tab to review progress, failures and omitted components. Do not infer success from an email notification alone.

Protect any temporary source credentials. Base64-encoding a password does not encrypt it or hide it from process arguments, logs or shell history. This guide does not reproduce CLI examples that expose root credentials as command arguments or enable overwriting by default.

Verify every required component

Check account ownership, application runtime/extensions, database access, domains, mailboxes and representative messages, certificates, DNS and jobs. Cross-panel conversion does not guarantee identical settings or credentials. Legacy imports may require separate email or FTP-account work; inspect the installed tool’s actual report and rotate temporary access afterward.

Preview using real hostnames before changing DNS. Prevent duplicate mail/payments from test copies and plan final database/mail synchronization. Keep the source and original archive until accepted, then remove temporary copies under your retention policy.

Reviewed October 14, 2026. Current vendor import guidance and legacy article scope were compared; no Webuzo import or customer-server change was executed.