Skip to content

Knowledgebase

Comparing storage, users and application limits before an upgrade

web-hosting

Compare limits using the actual unit and scope of each service. A mailbox allowance, shared organisation pool, website disk quota and application-user limit are different constraints, even when they appear together on a product page.

01 Build a useful comparison

  1. List the required services and current usage. For each, record the exact metric, its limit, whether it is per user or shared, and where usage can be checked.
  2. Separate storage from other limits such as users, websites, databases, monitored targets, message size or application features.
  3. Identify what happens at the limit. Ask whether new uploads, sending, backups or another function is restricted, rather than assuming every product behaves the same way.
  4. Estimate growth from actual recent use and planned changes. Include migration overlap and temporary working space where relevant.
  5. Compare the proposed plan's current specification with the order terms. Confirm which allowances are included and which require an add-on or edition change.
  6. Choose warning points and an owner for reviewing usage. Leave practical headroom for the business's expected growth instead of waiting for a hard limit.
  7. After an upgrade, verify that the effective quota and required feature changed in the product dashboard.

02 Example: compare the unit and scope before upgrading

Build a small worksheet from the actual service dashboards. The following rows show the type of distinction to record, without assuming a particular plan allowance:

Resource Scope to confirm Evidence to compare
Website storage The hosting account or defined website pool Live files, database use and counted backup copies
Email storage One mailbox or the organisation's shared pool Mailbox and organisation usage displays
Business applications Each licensed user and the purchased edition Assigned licences and enabled features

A full mailbox with unused website disk space does not establish that space can be transferred. Ask support to match the specific resource and ordered entitlement, then verify the changed limit in the appropriate dashboard after an approved upgrade.

Common questions

Can unused website space become mailbox space?

Only if the specific product shares that pool. Separate services should be treated as separate allowances unless the order explicitly states otherwise.

Does deleting a user always free paid capacity immediately?

Data handling and billing commitments can differ. Review the provider's removal process and the subscription terms before deleting an account.

What if the dashboard and invoice seem inconsistent?

Provide the service identifier, ordered plan and a current usage screenshot with private data removed. Ask support to reconcile the entitlement before purchasing another service.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution