Primary Domain Change in cPanel / WHM – Complete Guide Print

1. Core Principle

• Changing the primary domain does not create a new website

• The active website normally exists in /public_html

• Files and databases remain unchanged unless the client explicitly approves a replacement

2. Rule on Data Replacement Permissions

Explicit client permission is required only when existing data in /public_html will be removed or overwritten.

Reason

• /public_html contains the current live website

• Replacing its contents is a data-destructive action

• Client approval is required for correctness and accountability

3. Scenario Handling (All Valid Cases)

A. New Domain NOT Added

Action

• Change primary domain

Files

• /public_html remains unchanged

Permission Required

• ❌ No

B. New Domain is PARKED (Alias)

Action

• Remove parked domain

• Change primary domain

Files

• /public_html remains unchanged

Permission Required

• ❌ No

C. New Domain is ADDON Domain

Addon domains always use a separate document root.

Typical structure:

/public_html/
   ├── current-site-files
   └── addondomain/

4. Mandatory Decision (Addon Domain Case Only)

One clarification is required:

Should the existing website in /public_html remain, or should the addon website become the main website?

C1. Existing /public_html Website Should Remain (Most Common)

Action

• Remove addon domain entry

• Do NOT move any files

• Change primary domain

Files

• /public_html remains intact

• Addon folder may be deleted or archived if not required

Permission Required

• ❌ No (since main website data is untouched)

C2. Addon Website Should Become the Main Website

⚠️ This is the ONLY scenario involving data replacement

Mandatory Client Approval

The client must explicitly confirm that:

• Existing /public_html data will be removed or overwritten

• Addon website will replace it

Action Steps

• Remove or archive existing /public_html data

• Move contents of /public_html/addondomain/ → /public_html/

• Remove addon domain entry

• Change primary domain

• Reissue SSL and verify website

Result

• Addon website becomes the main website

5. What Never Happens Automatically

• /public_html data is never deleted without approval

• Addon data is never merged automatically

• Files are never replaced silently

6. Execution Notes

• Primary domain change is a WHM-level operation

• File movement requires explicit approval

• Website and SSL must be verified after the change

7. Golden Rule

Keep /public_html by default. Replace it only when an addon website is explicitly promoted as the main website.

8. Client Explanation (When Needed)

Changing the primary domain keeps your existing website unless you explicitly request to replace it.

End of Guide