Planning package changes across several reseller accounts

Export account details and record each current package and custom exception. Confirm the new package is compatible with current usage, features and reseller resource allowances.

1. Create a reviewed list of exact usernames and intended target settings. Keep unrelated accounts out of the change scope.
2. Apply the target package to one authorised test or low-risk representative account and verify website, mail and panel features.
3. Open Modify/Upgrade Multiple Accounts and select only the approved accounts. Review the checked rows after filtering or pagination.
4. Choose the intended package or supported shared setting and submit once. Save the result and any per-account failure messages.
5. Compare every target account with the plan. Investigate failures individually and confirm no unselected account changed.

All intended accounts should show the correct effective configuration, while exceptions are clearly recorded. Reconcile server-side changes with the separate billing records when necessary.

If one account cannot accept the new package, inspect its usage, owner and privileges instead of rerunning the entire batch blindly. To recover from an incorrect assignment, use the saved per-account package map and verify each restoration.

If you operate more than one reseller account, the same package label may refer to different limits on different servers. Maintain a comparison of each package's name, owner prefix, storage, bandwidth and relevant feature list before connecting it to your billing system.

Test provisioning on each intended server with a controlled account. Confirm that the created account receives the package and limits you advertised. An order that reaches Active in a billing system is not sufficient proof that the remote account has the right configuration.

How should I change a package later?

Record which products and existing accounts use it. Review how the panel applies package changes and test the effect on a non-production account before changing a widely used plan. Avoid reducing a storage allowance below a customer's current usage without an agreed migration or cleanup plan.

Contact us with the reseller service, exact remote package name and intended limits if you need provisioning help. Do not send your WHM password or API token. Your own product descriptions and billing prices should be checked separately from the hosting package's technical limits, as one does not automatically prove the other was updated.

It can affect every account assigned to that package, which may be a broader group than your approved list. Choose the workflow whose scope matches the planned change.

• Moving an existing account to another WHM package
• Finding the owner, package and resource usage of a WHM account
• Understanding allocated resources and overselling limits in WHM
• Preparing starter files for newly created cPanel accounts

• cPanel: Modify Upgrade Multiple Accounts
• cPanel: Upgrade Downgrade An Account