1. Introduction
The Convert Addon Domain to Account interface in WHM allows administrators to convert an addon domain into a standalone cPanel account. This guide outlines which data is migrated, which data is not, and how the conversion process handles specific components.
Note: This feature is still under development and may change in future releases. If the origin account has an assigned IPv6 address, the conversion will fail. Disable IPv6 before proceeding.
2. Data Migrated During Conversion
The conversion tool migrates the following data types:
- DNS records
- Website configuration
- Document root contents
- VirtualHost include files
- Installed SSL certificate
- Email accounts
- Email autoresponders
- Email user filters
- Email forwarders
- Domain forwarders
- Mailing lists
- Webmail (application data)
- MySQL
- Databases
- Database users
- Redirects
- Subaccounts
- FTP accounts
- Web Disk accounts
3. Data Not Migrated
The following data types are not migrated during the conversion process:
- Installed applications
- MultiPHP settings
- Subaccounts (certain types)
- Subdomains
- Any additional data not listed in the migrated section
Important: You must delete all subdomains associated with the addon domain before converting it. Otherwise, the conversion will fail.
To preserve subdomain data, create a full backup of the cPanel account before deleting the subdomain. After conversion, restore the backup to the new account.
4. Detailed Migration Behavior
4.1 DNS Records
- The system copies the DNS zone file before removing the addon domain.
- After creating the new account, it restores the zone file and updates the IP address to match the new account.
4.2 Email Accounts
Email account data is copied to the new account. The original account retains its email data, but new incoming messages will only appear on the new account.
4.3 Email Autoresponders
Autoresponder data is copied. The original autoresponders remain intact after conversion.
4.4 Email Forwarders
Forwarder files are copied and restored for the new account. Because forwarders are tracked outside the user’s home directory, only one copy can exist on the server.
Forwarder file locations:
- Email forwarders:
/etc/valiases/domain.name - Domain forwarders:
/etc/vdomainaliases/domain.name
4.5 Mailing Lists
Mailing lists are not affected. They continue to function normally after conversion.
4.6 Webmail Data
The system copies address book, calendar, notes, and signature data. The original data remains untouched.
Note: This does not apply to Roundcube.
4.7 MySQL Databases
- Copied: Original databases remain unchanged.
- Moved: The system updates database grants to reflect the new account ownership.
4.8 Subaccounts
FTP and Web Disk accounts are copied. The original accounts remain intact.
4.9 Website Configuration
The system copies:
- Document root contents
- VirtualHost include files
- Installed SSL certificate
The original data remains on the source account after conversion.
5. Conclusion
The Convert Addon Domain to Account feature provides a powerful way to separate addon domains into independent cPanel accounts while preserving key data such as DNS records, email, MySQL databases, and website configuration. Understanding which data is migrated—and which is not—helps ensure a smooth and predictable conversion process.