Convert a cPanel Addon Domain into a Separate Account Carefully

WHM’s Convert Addon Domain to Account creates a separate cPanel account from an existing addon domain. This is not simply changing the original account’s primary domain, and it is not a promise that every application setting moves automatically.

Review eligibility and recovery first

The operator needs the appropriate WHM privileges and an approved destination package/account. Preserve a recoverable original account backup, inventory the site’s dependencies and allow sufficient temporary disk space because data can remain on the source.

Read the installed release’s conversion limitations before proceeding. Current vendor documentation warns about assigned IPv6 and addon subdomains, and lists data/settings that are not migrated. Do not disable networking or delete subdomains blindly to satisfy a prerequisite: preserve their data, understand the impact and plan the supported conversion/recreation sequence first.

Configure the conversion deliberately

1. Use verified HTTPS WHM and Transfers > Convert Addon Domain to Account.
2. Select the exact eligible addon domain and review its source account.
3. Set the new account identity, contact and package, using appropriate unique credentials.
4. Review website, email, database and subaccount selections. Copying versus moving databases has different ownership/grant and space consequences; application credentials and dependencies need verification.
5. Save the reviewed selections and start only within an approved maintenance/recovery plan. Inspect conversion history and detailed results.

Validate more than List Accounts

An account appearing in the list does not prove the website, PHP configuration, database grants, mail, TLS, scheduled jobs or application paths work. Test those dependencies independently before retiring old data. Installed applications and MultiPHP settings are among the documented exclusions; confirm the current conversion list instead of assuming an all-inclusive migration.

Do not delete the source data just because the job finished. Establish which copies remain required, preserve recovery and remove only independently verified obsolete data. The former one-line API example omitted these decisions and is no longer presented as a complete safe procedure.

This is documentation for an authorized same-server cPanel administration feature, not an InterServer VPS or dedicated-server migration offer. Hosted-service assistance must follow the actual plan and owner-confirmed matching-panel web-hosting migration scope.

References: conversion workflow and prerequisites and included/excluded data.

Reviewed October 16, 2026. No account conversion, database move, IPv6 change or source cleanup was performed.