Skip to main content

How to Convert an Addon Domain Into a Separate cPanel Account

This guide explains how to convert an existing Addon Domain into a standalone cPanel account within WHM. This process allows an administrator to move a domain from a shared account environment into its own dedicated account with its own resources and...

This guide explains how to convert an existing Addon Domain into a standalone cPanel account within WHM. This process allows an administrator to move a domain from a shared account environment into its own dedicated account with its own resources and settings.

Before you begin

You will need:

  • Root access to the WHM server

  • The specific domain name currently configured as an Addon Domain

  • The desired username and password for the new cPanel account

  • The desired hosting package for the new account

Convert an Addon Domain to a New Account

  1. Log in to WHM.

  2. Navigate to Move_Addon_Domain_To_New_Account (or search for "Move Addon Domain" in the sidebar).

  3. Select the Addon Domain you wish to convert from the list.

  4. Enter the New Username for the account.

  5. Enter the New Password for the account.

  6. Select the Package for the new account.

  7. Click Move Account.

Warning: This process will move the files, email accounts, and databases associated with the Addon Domain to the new account. The original Addon Domain entry will be removed from the source account.

Confirm the result

  • The Addon Domain will no longer appear in the original account's list of Addon Domains.

  • A new cPanel account will be created with the domain as the primary domain.

  • You can verify the migration by logging into the new cPanel account and confirming the files and email accounts are present.

Limitations

  • This process does not automatically update DNS records. After the conversion, you must update the domain's nameservers or DNS records to point to the new account's IP address if it differs from the original.

  • Any internal links or hardcoded paths within your website's code or database may need to be updated if the internal pathing changes during the move.

  • This procedure does not move items that are not part of the standard cPanel migration (such as specific third-party application configurations).

Did this answer your question?