We provide a route to grow your hosting service as its requirements change. Start by opening the relevant service in your client area and reviewing the upgrade options available for it. Our Web Hosting page advertises upgrades with prorated billing, but you should review the actual quotation, effective date and any requirements before confirming a change.
IN THIS ARTICLE
01 Identify the capacity constraint and expected growth
An upgrade is most useful when you understand the constraint it needs to solve. Check whether the problem is storage, website count, memory, processing load or an application requirement. A larger package can provide more capacity, but it will not automatically repair inefficient database queries, a broken plugin or an incorrect application setting. The manager's usage information and the relevant AI Engineer can help investigate the cause before you choose a plan.
Describe your expected growth to us. Examples include adding a second website, expanding a product catalogue, increasing mailbox storage or handling a campaign that may create a traffic peak. Ask about the resources and features that matter to that workload rather than assuming a higher-priced plan changes every limit.
02 Determine whether the change needs a migration
Some changes fit within the existing service family. Moving from general Web Hosting to NabWP, or to an environment requiring server-level control, can involve a different product and a migration. Confirm whether files, databases, DNS, email and application settings need attention, and arrange testing if the hosting environment will change.
03 Review billing and verify the completed upgrade
- Before approving an upgrade, check the amount due now, the future renewal amount and the billing cycle.
- Keep a suitable backup before any move that affects the hosting environment.
- After completion, confirm the new allocation in your account and test the site's essential functions.
A billing confirmation and a fully verified application are separate parts of completing the change.
What information should I provide for a plan-change request?
- Provide the current service and describe which limit or requirement the change must solve.
- Review the available destination package and whether the change is a same-service adjustment or a move requiring migration.
- Before approving, check the immediate charge, the next renewal amount and the future billing cycle. Afterward, verify both the account allocation and the website functions.
For a downgrade, reduce legitimate usage only through an agreed plan that preserves needed data. A smaller allowance must still accommodate files, databases, mail and websites. Moving between Web Hosting and NabWP can involve a product transition even when the same domain is retained.