Changing an account’s WHM package applies the limits and features of another server-side plan. Review the differences before proceeding so an intended storage upgrade does not unexpectedly remove a required feature.
IN THIS ARTICLE
Prepare for the change
Confirm the customer’s authorised service change and record the current package and any custom account settings. Check disk usage, mailbox counts, databases and other active resources against the target package.
01 Move an existing account to another WHM package
- Open Upgrade/Downgrade an Account, select the exact account and choose Modify.
- Inspect the available target package using its details or magnifying-glass control. Compare quota, bandwidth and feature-list settings.
- Check reseller resource limits and whether the target package is permitted for that owner. Resolve capacity issues before applying the change.
- Select the target package and use Upgrade/Downgrade. Read the result and record any warning instead of repeatedly submitting.
- Reopen List Accounts and the customer’s cPanel to verify effective limits and essential features. Check the billing system independently if it must reflect the change.
Confirm the expected result
The account should show the intended package and function within its new allowances. Existing website and mail operations should still pass representative tests.
If the change does not work
If the target is smaller than current usage, do not assume the panel will safely remove excess data. Arrange cleanup or a suitable package first. A package change does not move the account to a new server IP; that requires a separate supported action.
Should I edit the shared package to upgrade one customer?
Editing a package can affect other accounts assigned to it. Use an appropriate target package or a deliberate account-specific exception when the change belongs to only one customer.