WHM has a screen for creating many hosting accounts in one operation, and most resellers never find it because it sits below the single-account form they land on first. If you have thirty domains to set up, this is the difference between an afternoon and about two minutes.
There are actually four ways to create accounts in bulk, suited to different situations, and choosing the wrong one is how people end up doing avoidable manual work.
Create Multiple Accounts
In WHM, open Account Functions then Create Multiple Accounts.
You paste a list of domains, one per line, choose a single package to apply to all of them, and WHM generates usernames and passwords and creates every account in one run.
clienta.com clientb.net clientc.org clientd.co.uk
Pick the package before submitting. Every account in the run gets the same one, so if you are creating accounts on two different plans, that is two runs rather than one.
Then submit and stay on the results page. This is the part that catches people: WHM generates a password for each account and displays it once, on that screen. Navigate away and they are gone, and you are resetting forty passwords by hand.
Copy the whole output somewhere before you do anything else. The usernames are generated too, so if your naming convention matters, review what it produced while you still have it in front of you.
Check your allocation before the run
Bulk creation does not stop you exceeding what your plan holds. It will happily create twenty accounts on a plan that allows ten, or promise 200GB of quota out of a 60GB allocation.
Your reseller plan gives a fixed number of cPanel accounts and a fixed disk allocation. Ahosting's tiers are sized by account count (R Bronze 5, R Silver 10, R Gold 20) and that count is usually what binds first.
Look at your current usage against your allocation before submitting a large run. It is a ten-second check that prevents a situation where every client is over quota simultaneously.
Settle the username convention first
WHM generates usernames from the domains, and a username cannot be changed later without recreating the account. It becomes the Linux user, the database prefix and the FTP login.
So decide your convention before the first bulk run, not after forty accounts exist with machine-generated names you cannot reason about. If the generated names are unacceptable, create those accounts individually instead. It is slower once and permanent.
Bringing accounts in from another host
If the accounts already exist somewhere else, do not recreate them here and copy files across. That loses email, forwarders, cron jobs and DNS, and the absences surface days later as "my email stopped working".
Use Transfer or Restore a cPanel Account. Given a cPanel backup file, it restores the entire account: files, databases, email accounts with their messages, cron jobs, DNS zone and settings, in one operation.
WHM can also pull directly from the old server if you have root access there, which handles many accounts in sequence without downloading anything by hand.
Either way, restore first and test with a hosts file entry while DNS still points at the old host. Change DNS only once it works.
Driving it from the API
For a genuinely large batch, or accounts that each need different packages, the API is the next step. This creates one account:
whmapi1 createacct username=clienta domain=clienta.com plan=web-5gb
Loop over a file of domains and packages and you have a bulk creation that handles cases the web form cannot: different packages per account, dedicated IPs for some, custom settings.
The API is also what billing software uses underneath, which is worth knowing: if you find yourself scripting account creation regularly, you are rebuilding something that already exists.
Stop creating accounts by hand entirely
For an ongoing hosting business, the right answer is that account creation stops being a task you do.
Billing software connected to WHM provisions the account when an order is paid, emails the client their details, and suspends the account automatically if an invoice goes unpaid. Bulk creation becomes irrelevant, because accounts create themselves one at a time as people buy.
This is the difference between reselling as a side activity and as a business: the administrative work stops scaling with client count. Integrating billing and automation deals with connecting it.
One habit matters afterwards. Once billing is connected, create accounts through billing even when doing it directly in WHM feels quicker. An account created by hand never gets invoiced, works perfectly, and is discovered a year later.
After a bulk run
Send each client their details, and include the nameservers: it is the step clients get stuck on, and omitting it generates a support message every time.
Then spot-check a few accounts. Open one from List Accounts, which needs no password, and confirm the limits match the package you applied. A package quota entered in the wrong unit looks fine in the package list and fails the moment a client uploads anything.
What fails during a bulk run
"Domain already exists." That domain is on the server already, possibly as a parked or addon domain under another account. WHM skips it and continues with the rest, read the output instead of assuming everything succeeded.
Account limit reached. The run stops partway. You now have some accounts created and some not, so check the output carefully before retrying.
Username already in use. Usernames are unique across the whole server, not just your accounts. WHM adjusts or skips depending on the situation.
For adjusting accounts after creation, editing cPanel account resources deals with changing one without disturbing its package.
Bulk creation is only as good as the package behind it, since every account in the batch inherits the same limits. How to Create and Manage Hosting Packages in WHM goes into getting those right before you run it.
