This article is intended for customers who want to understand how addon domains can be converted into full cPanel accounts, and why converting a full cPanel account into an addon domain or moving an addon domain into another existing cPanel account is usually not recommended.
Converting an Addon Domain to a Full cPanel Account
In most cases, it is possible to convert an addon domain into its own standalone cPanel account. This gives the domain its own file structure, databases, email accounts, DNS zone, and resource usage separation.
Only our technical support team can perform this process, as the cPanel/WHM tool used for conversions is only accessible to server administrators.
Important: Converting an addon domain into a full cPanel account is usually a one-way process. Once the domain becomes its own account, reversing the process (or moving it into another cPanel account) is not supported by any automated tool and requires extensive manual work by the customer. For more details, please see the next section: Converting a Full cPanel Account Back Into an Addon Domain (or Moving an Addon Domain Into Another Existing cPanel Account).
Additionally, multiple addon domains cannot be converted at the same time, nor can multiple addon domains be converted into the same cPanel account. Each addon domain must be converted individually into its own separate cPanel account.
What Happens During the Conversion
When converting an addon domain into its own account, the conversion tool will normally:
-
Copy the website files of the addon domain
-
Copy web server settings (if needed)
-
Copy DNS records
-
Copy email accounts, forwarders, filters, mailing lists, and webmail data
-
Copy databases and database users
-
Copy FTP accounts associated with the addon domain
-
Copy FTP and Web Disk accounts
Some items may need a bit of extra manual work, such as website applications installed outside the addon domain’s folder or certain PHP settings. Subdomains of the addon domain also need to be removed first and manually re-added.
Step 1: Contact Technical Support
Please open a support ticket with us. Our team will review your setup and confirm whether the addon domain can be safely converted.
Step 2: We Perform the Conversion
A technician will:
-
Check that the addon domain has no active subdomains
-
Verify available disk space
-
Review database naming and compatibility
-
Run the conversion once all technical aspects have been checked and clarified
The conversion typically takes approximately 1 hour, but this always depends on the size of the addon domain. Once complete, we will provide the new cPanel login details.
Step 3: Update Nameservers or DNS Records
After the conversion, you may need to:
-
Update the nameservers at your domain provider, or
-
Adjust DNS records if your domain uses external DNS services (e.g., Cloudflare)
We will advise you on the correct steps.
Converting a Full cPanel Account Back Into an Addon Domain (or Moving an Addon Domain Into Another Existing cPanel Account)
While this can be done in theory, it is not supported by any automated tool in cPanel or WHM, and usually involves a lot of manual work. The same applies when moving an addon domain from one cPanel account into another: it requires a large number of manual steps and involves downtime. Because of the amount of manual work involved, this option is often not practical or worthwhile.
Simplified Example Steps
Before any transfer can begin, the domain must be temporarily removed from the original (source) cPanel account so it can be added as an addon domain under the target account. During this period the website, email and other services related to the domain will be offline. The downtime can range from several minutes to several hours, depending on the size of the site, database, and email data being moved.
To give you a clearer, more customer-friendly idea, the manual steps usually include tasks such as:
-
Backing up the source account, removing the domain from it, and setting it up in the target account
-
Removing the addon domain from the source cPanel account
-
Recreating the addon domain in the target cPanel account
-
Manually downloading the website files and re-uploading them into the new addon domain folder
-
Reconnecting the website’s database in the new account
-
Recreating database users and linking them to the database
-
Recreating all email accounts, forwarding settings, auto-responders, email/spam filters, etc.
-
Rebuilding DNS records in the new account
-
Updating the website configuration where needed so it works correctly in its new location inside CMS applications
-
Ensuring file and folder permissions are correct
Even after completing all of the above, issues may still occur depending on how the site and email systems were originally configured.
For these reasons, we strongly do not recommend converting a full cPanel account into an addon domain or moving an addon domain to a different existing cPanel account.
Summary
-
Converting an addon domain to a full cPanel account is usually possible and can be completed by our technical support team.
-
Converting a full cPanel account into an addon domain or moving an addon domain to a different existing cPanel account is technically possible but requires extensive manual work and is rarely advisable.
If you would like us to review your hosting structure or check whether a conversion is suitable, please open a support ticket — we’ll be happy to help.
Updated by SP on 17/11/2025
