How to Change the Primary Domain in cPanel

What 'primary domain' means in cPanel

You cannot change the primary domain from inside cPanel's own interface. cPanel labels it the Main Domain under Home » Domains, and only your hosting provider or an admin with WHM access can rename it — via WHM's Account Functions → Modify an Account or, on newer cPanel builds, a host-enabled Rename Domain option under Domains → Manage. Three routes, by access level:

1. Shared hosting — open a support ticket: "Please change the primary domain of cPanel account [username] from [old] to [new]." The provider renames the account, re-points public_html and updates the document root.
2. VPS/dedicated with WHM — log into WHM as root, go to Account Functions → Modify an Account, select the account, replace the primary domain, save.
3. Newer cPanel with the Domains interface — where the host allows it, Manage → Rename Domain renames the domain inside cPanel itself.
4. Before either — verify the new domain resolves to the server (A record) before requesting the change.
5. After — reissue SSL and rebuild redirects; email accounts for the old primary need re-pointing.

Files do not move — public_html contents simply serve under the new name. Full domain-change context sits in the change website domain guide, with SSL steps in cPanel SSL install.

What changes and what does not

Changing the primary domain relabels the account — it does not touch your data. Email, FTP and Web Disk accounts under the old primary, plus any subdomains of it, update to the new domain automatically, exactly as cPanel's own change warning states. Website files and the public_html document root stay where they were. What cPanel cannot fix lives inside your applications: hard-coded URLs, cron jobs and the WordPress siteurl/home pair must be updated manually before the site works on the new name. Allow up to 24 hours for the change to settle fully.

Method 1: request via hosting support (shared)

On shared hosting the primary domain sits above your cPanel login, so the provider makes the change. Two prerequisites first: the new domain must not already exist on the server — remove it if it is currently an addon domain, alias (parked domain) or subdomain — and its DNS must point at the server (an A record to the server IP, or the host's nameservers) before you ask. Then open a ticket that names all three facts: "Please change the primary domain of cPanel account [username] from [old] to [new]." The provider renames the account, re-points public_html and updates the document root. WebJi® customers email support@webji.services — staffed 24/7 in Hindi and English, and the Jaipur desk rechecks SSL and redirects once the rename lands.

Method 2: WHM Modify Account (VPS/dedicated)

With root or reseller WHM access — VPS and dedicated plans — you make the change yourself. The one rule cPanel enforces: the new domain must not already exist anywhere on the server, not even as another account's addon or alias.

1. Log into WHM as the root user.
2. Go to Account Functions → Modify an Account (or open List Accounts and click the + next to the account).
3. Select the account and click Modify.
4. Type the new domain name in the Primary Domain field.
5. Click Save at the bottom of the page.

WHM applies the new name to the account's mail, FTP and subdomain configuration immediately; reissue SSL and rebuild redirects afterwards as covered below.

Method 3: rename inside cPanel Domains (host-dependent)

On newer cPanel versions the Domains interface can rename a domain without WHM: open cPanel → Home → Domains, click Manage next to the domain, choose Rename Domain, type the new name in the Replace with a registered domain box and click Update. The cPanel documentation notes the rename option covers primary domains as well as addons — but your host can disable it in WHM's Feature Manager, so if Manage shows no rename option for the main domain, fall back to Method 1 or 2. The same Manage screen is where a domain's document root is edited.

Re-pointing document roots

The primary domain's document root remains public_html, so after a straight rename the same files simply serve under the new name — nothing needs to move. The case that needs work is promotion: if the new primary previously lived as an addon domain in its own folder (for example public_html/newsite), either copy its contents into public_html before the change, or edit the domain's document root afterwards under Domains → Manage. Check the site in a private browser window so cache does not hide the result.

Fixing redirects, SSL and email

Fixing redirects, SSL and email afterwards. SSL: cPanel → SSL/TLS Status → Run AutoSSL, or issue via your Let's Encrypt provider for the new primary and its www variant — browsers will not negotiate without it. Redirects: add a 301 from the old primary to the new one so bookmarks and search equity transfer; keep it permanent, not temporary.

Email: accounts under the old primary either move with the account (addresses now read @newdomain) or need new mailboxes plus forwarders from the old addresses — decide before cutover and update senders. Cron jobs, hard-coded URLs and the WordPress siteurl complete the sweep. Do the swap in a low-traffic window, never mid-migration.

WebJi® runs its shared, reseller and managed plans on cPanel, and the Jaipur desk performs primary-domain changes for customers on request — start on the WebJi® cPanel hosting plans page.