You cannot change your cPanel username directly through cPanel itself
Your cPanel username is tied to your hosting account and server user at the system level. cPanel does not provide a built-in tool to rename it. If you want a different username, you will need to contact your hosting provider's support team — they can create a new account with the username you want, then migrate your files and settings to it. This takes a few hours to a day depending on your host.
The reason for this limitation is technical: your cPanel username controls file ownership, email routing, database permissions, and SSH access across your entire account. Changing it requires updates at the operating system level that only your host can perform safely.
Key Takeaways
- cPanel usernames cannot be changed through the cPanel interface — your hosting provider must do this at the server level.
- You will need to contact your host's support team and request a new account with your desired username.
- Your host will migrate your files, databases, email accounts, and addon domains to the new account.
- During migration, your site may be offline for 30 minutes to a few hours depending on your account size.
- Your old username will typically be deleted after the migration is complete, so update any scripts or backups that reference it.
What your hosting provider needs from you
When you contact support, have your current cPanel username and the new username you want ready. Your host will check whether the new name is available on their server — usernames must be unique, and some hosts reserve certain names for system use.
You should also let them know if you have any active backups, cron jobs, or third-party tools connected to your account. Some hosts ask you to pause automated backups before migration to avoid conflicts. If you run any scripts that reference your username in file paths or database connection strings, you will need to update those after the migration is complete.
What happens during the migration
Your host will create a new cPanel account with your requested username, then copy your files, databases, email accounts, addon domains, and SSL certificates to it. The exact process varies by host, but most follow this order: create the new account, copy the data, test that everything works, then point your domain to the new account's IP address or update DNS records.
Your site will typically be offline during the DNS update step, which usually takes 15 minutes to an hour. Some hosts do this during off-peak hours to minimize disruption. Ask your support team when they plan to do the migration and whether you should notify your users.
Updating your SSH and FTP connections
After the migration, any SSH or FTP client you use will need the new username. If you connect via SSH, update your connection command from ssh oldusername@yourserver.com to ssh newusername@yourserver.com. Your password stays the same unless your host changes it as part of the migration.
For FTP clients like FileZilla or Cyberduck, edit the saved connection profile and change the username field. Test the connection before you delete the old profile to make sure the new one works.
Updating scripts and configuration files
Any script that references your old username in a file path will break after migration. Common places to check: WordPress wp-config.php files that reference absolute paths, custom PHP scripts with hardcoded paths like /home/oldusername/public_html, and cron job commands that call scripts by full path.
Search your files for your old username before the migration and note where it appears. After the migration is complete, use your host's file manager or SSH to replace the old username with the new one. If you use a version control system like Git, update the paths there too.
Database and email account considerations
Your databases will be migrated with the same names and passwords, so you do not need to update database connection strings unless they include the full username in the path. Email accounts created under your cPanel username will move to the new account automatically — users can keep using the same email addresses and passwords.
If you have email forwarding rules or filters set up, those will transfer as well. Test a few email accounts after migration to confirm they are receiving mail correctly.
If you want to keep your old account temporarily
Some hosts will keep your old account active for a few days or weeks after migration so you can verify everything works before they delete it. Ask your support team about this when you request the migration. Having both accounts active briefly lets you test your site, check that all email is routing correctly, and update any external services that connect to your account.
Once you confirm the new account is working, ask your host to delete the old one. Do not leave old accounts active indefinitely — they consume resources and create security risk if you forget about them.
Frequently Asked Questions
Will my domain name change when my cPanel username changes?
No. Your domain name stays the same. Only your cPanel username and server user change. Your site will be accessible at the same domain after migration.
Do I need to update my SSL certificate when I change my username?
No. SSL certificates are tied to your domain name, not your cPanel username. Your host will migrate your existing certificates to the new account automatically.
What if my host says they cannot migrate my account?
Some smaller hosts may not offer migration services. In that case, you can manually back up your files and databases through cPanel, create a new account with your desired username, and restore the backups to it. This takes longer but gives you the same result.
Can I change my cPanel username myself through SSH?
No. Changing a system username requires root access and updates to multiple system files and databases that only your host can safely perform. Attempting it yourself will break your account.
How long does the migration usually take?
Most migrations take 30 minutes to a few hours depending on how much data you have. Your host will give you a time estimate when you request the change. Larger accounts with many databases or gigabytes of files may take longer.