A WHMCS server group determines which configured server receives a newly provisioned service for a product. It is useful when a product can be delivered on several compatible servers or when different product families must use separate infrastructure.
IN THIS ARTICLE
01 Build a compatible group
- Configure and test each server connection in System Settings and Servers. Confirm that the provisioning module and credentials support the intended product.
- Create the required hosting packages or service plans on every eligible server. Use the exact package names expected by the product's Module Settings.
- Select Create New Group, enter a clear operational name and choose the allocation method.
- Add the intended servers to the group and save it. Exclude servers that are reserved for existing customers or are not ready for new accounts.
- Open the product, select its Module Settings and assign the appropriate Server Group. Save and review the automatic setup timing before testing an order.
02 Choose the allocation method
The least-full option uses the account count relative to the configured maximum number of accounts. It does not automatically evaluate CPU load, storage latency or each customer's resource consumption. Set account limits using your own capacity assessment and monitor server health separately.
The fill-first approach places accounts according to the group's selected behavior until the applicable limit is reached. Review the default server where that allocation method depends on it. For a group with one server, WHMCS documents using the least-full option.
03 Example: calculate which server is least full
Assume both servers are eligible, connected and contain the required package. These numbers illustrate the allocation calculation; they are not recommended server capacities.
| Server | Recorded accounts | Configured maximum | Account capacity used |
|---|---|---|---|
| Server A | 80 | 100 | 80% |
| Server B | 100 | 200 | 50% |
With the least-full method, Server B has the lower proportion used even though it contains more accounts. The comparison is based on the configured account limits, so an inaccurate maximum can produce an unsuitable placement decision.
Check the assigned server after a test order and continue monitoring real resource use separately. A 50% account count does not establish that CPU, memory or storage is only 50% used.
How do I confirm which server receives a new account?
Place a controlled test order and inspect the resulting service's assigned server and the remote account. Confirm that the package, nameservers and welcome message match that server. Remove the test account through a deliberate cleanup process after checking that it is not linked to a real customer.
Changing a product's server group affects future allocation. It does not migrate existing hosting accounts or move their files and databases. Plan existing-service migrations as separate tasks and update WHMCS only after confirming the destination account.