cPanel to CWP: Private Backup Import and Recovery Checks

CWP (Control Web Panel, historically called CentOS Web Panel) has a cPanel account-import workflow. Treat this as an administrator-managed cross-panel conversion, not a guaranteed full copy or an InterServer migration service. Matching-panel web hosting transfers are the only complimentary migration scope; VPS and dedicated-server migrations are not offered.

Prepare a separate destination and rollback

Check the currently supported CWP operating system, release, licensing and import requirements. Do not install a panel over the only live server or rely on old CentOS-era/free/open-source claims to choose a supported stack.

Inventory accounts, domains, databases, mailbox data, software requirements and existing destination content. Confirm username/domain collisions and package capacity before starting. Preserve independent source and destination backups.

Transfer a supported cPanel archive privately

Generate a completed full cPanel account archive through an authorized backup route. Use authenticated encrypted transfer to the destination’s approved private staging location. A random filename, altered permissions or a backup under public_html is not access control.

The former articles recommended an anonymous HTTP download or supplying a destination root password for an ordinary transfer. Those shortcuts are withdrawn. Use scoped access where available and an administrator-approved secure route.

Check the importer-supported archive format and filename for your installed release. Renaming an arbitrary ZIP or partial backup to cpmove-user.tar.gz does not convert its contents. Preserve the original archive when a supported account backup requires a filename adjustment.

Review the CWP import selections

Use the installed panel’s cPanel Migration/account-import interface and select the intended archive, destination package and required components. Follow current account-creation rules and investigate collisions rather than deleting an existing user to make the import proceed.

When the importer requests new account or mail credentials, use strong distinct secrets and deliver them privately to authorized owners. Do not assume source mailbox passwords survive conversion or set a single shared password without an approved recovery plan.

Verify before DNS cutover

Inspect import failures and omitted data. Preview sites with their real hostnames, check database-backed functions and required extensions, and verify mail folders/messages separately. Test in a way that does not send real customer email or take payments from a duplicate site.

Preserve third-party mail DNS, plan final synchronization and test delivery after the agreed cutover. Keep the source and private archive until the result is accepted. An import-completed banner does not prove every setting, recent write or message migrated.

Reference: CWP cPanel account-import documentation. Some legacy vendor instructions publish archives over HTTP; this guide deliberately does not recommend that unsafe transfer method. Reviewed October 14, 2026. No CWP installation, conversion or customer migration was tested.