Hosting plan and quota change checklist

Use this worksheet before requesting a hosting plan or resource-limit change. Fill in the plan and change details from your own account and the provider's current terms, then mark each check when it is complete. A larger plan may change billing, limits, network details, or service behavior; the exact effects depend on the provider and the specific change.

Record the proposed change

Check price, billing, and limits

• Compare the new plan's exact limits with current measured use and the workload you need to support. Record each unit, scope, and measurement window; do not treat a plan label as a guaranteed amount of a resource.
• Confirm the price, currency, billing term, renewal price, taxes, fees, and any unused-term credit or proration in the checkout/account terms before submitting.
• Confirm whether the change renews the subscription, changes its expiration date, changes included sites/email/backups, or affects separately billed services.
• Read the provider's current change policy for eligibility, timing, interruption, reversibility, and whether the requested resource can be changed in place or requires a migration.

Prepare a recoverable backup

• Create a recent, consistent backup of both website files and the database, and store a copy somewhere that will remain accessible if the hosting account is unavailable.
• Confirm the backup set is complete and identify the restore procedure, credentials, responsible person, and expected recovery steps. A backup that has not been checked may not be usable.
• Note how new orders, form submissions, comments, uploads, or other writes will be protected if a restore or rollback becomes necessary.

Plan the change and recovery path

• Ask whether the change can restart services, alter an IP address, change nameserver/DNS requirements, or affect email, SSL, scheduled jobs, integrations, or access credentials. Record only effects confirmed for this change.
• Choose a change window and notify anyone who needs to avoid publishing or editing during it. Save relevant settings and the provider's support contact.
• Write down a rollback or escalation route: which plan/settings can be restored, who can request it, what it costs or requires, and how data created after the change will be handled.
• Define a stop condition and a person authorized to stop or escalate the change if the site, mail, or an essential workflow fails.

Verify after the change

• Confirm the account shows the intended plan and resource limits, billing term, and next renewal details.
• Check the site over HTTPS, sign in, review representative pages and media, submit a test form, and verify essential integrations and scheduled work that apply.
• Check domain resolution and email sending/receiving if the provider says the change affects IP, DNS, or mail settings.
• Review usage and error information in the provider dashboard after the change. Compare the same metrics and time windows as the pre-change record.

0 checklist items checked.