Terminating an account deletes it. Files, databases, mailboxes and their contents, cron jobs, the DNS zone, all of it, immediately and permanently. WHM asks once and then does it. There is no trash, no recovery window, and no version of this you can undo without a backup you took beforehand.
Because of that, the useful part of this page is not the button. It is the short list of things to do before you press it, and the reasons to reach for suspension instead.
Before you terminate anything
Take a backup and keep it. Generate a full cPanel backup of the account and download it somewhere off the server. Keep it for a few months. Disk is cheap; the message that arrives six weeks later asking whether anything can be recovered is not, and with a backup the answer is yes.
Offer the client their data. Whether or not they are leaving on good terms, and whether or not they have paid. Sending someone their own site is a small courtesy that costs nothing and prevents a genuinely bad ending. It is also, in many places, simply what you are required to do.
Check the domain is not staying with you. If the domain was registered through you, or its DNS is served from your nameservers, terminating removes the zone and the domain stops resolving anywhere. That can take down email the client thought was separate. Move DNS first if the domain is continuing.
Confirm you have the right account. Usernames are short and similar. Read the domain, not the username, and read it twice. This is the single most expensive typo available to a reseller.
Check nothing else depends on it. Other clients' subdomains, a shared mail route, a database another site connects to. Rare, but the time to discover it is now.
Terminating the account
In WHM, open Account Functions then Terminate an Account. Select the account, read the domain shown, and confirm.
There is an option about keeping the DNS zone. Keep it if the domain is moving to another host and you are still providing DNS during the transition; remove it if the domain is leaving entirely. Removing a zone that is still in use makes the domain unreachable, which will be reported to you as a problem you caused after the client had already left.
WHM reports each step. Read the output rather than closing the tab; a partial termination that failed halfway leaves an account in an odd state.
After termination
Cancel it in your billing system. WHM and billing do not automatically agree. An account terminated in WHM but still active in billing keeps generating invoices for hosting that does not exist, which is the kind of mistake that turns a neutral parting into a complaint.
Check your allocation. The account slot and its disk return to your pool immediately. If you terminated to make room, confirm it actually appeared.
Remove it from monitoring. Uptime checks and backup jobs pointed at a site that no longer exists will keep failing and keep alerting, and after a week you will start ignoring the alerts, including the ones that matter.
When termination is not what you want
Non-payment, recently. Suspend. Most clients pay once the site goes down, and you cannot recover a deleted account when they do.
Suspected abuse or a compromise. Suspend. It stops the damage immediately and preserves what you need to understand how it happened. Terminating destroys the evidence along with the problem.
An account you do not recognise. Suspend and find out. A suspended account you were wrong about costs a few minutes; a terminated one costs a client.
To free up space on your plan. Only if the account is genuinely finished. Suspended accounts still occupy a slot, so it is a real reason to terminate, but terminate the dead ones deliberately rather than whichever is oldest.
A sequence that avoids most of the bad endings
- Reminder with a specific date.
- Suspend on that date, with the reason recorded on the account.
- Hold suspended for at least thirty days.
- Notify the client that the account will be deleted, with a date, and offer them a backup.
- Take your own backup and store it off the server.
- Terminate, then cancel in billing and remove from monitoring.
Steps three and four are the ones under pressure to skip, and they are the ones that prevent the outcome where a client returns to find their business website gone and no copy anywhere.
If the client is leaving for another host rather than disappearing, hand them a full cPanel backup rather than telling them to download files. Their new host can restore it in one operation with email and databases intact. The same mechanism described in adding new client accounts, in the other direction.