Measure current storage, database size, busy-period resource use and the number of websites. Include mailboxes, logs, staging copies and backups kept inside the account. For an application, identify its required PHP, Python, Ruby or Node.js versions and supporting services.

1. Review the current Cloud Hosting product and the exact plan quotation. Compare CPU, memory, storage, bandwidth and website allowances.
2. Confirm the control panel and runtime options available to that service. An advertised selector does not mean every framework version or system library is installed.
3. Check the backup tool, retention and restore process. Maintain your own tested copy of essential information.
4. Identify any requirement for root access, containers, custom daemons or an unusual database. Ask about suitability before purchasing; a cloud hosting account is not automatically a VPS.
5. Review billing period, support scope and any migration arrangement in the order and applicable terms.

Look for repeated resource limits during legitimate traffic, sustained storage growth or an application requirement that the current service cannot meet. First investigate inefficient queries, oversized media, background jobs and unwanted traffic. Extra resources may relieve pressure without removing the cause.

Inventory files, databases, email, scheduled tasks and DNS dependencies. Test the application on the new service and arrange a final data sync before switching traffic. For a busy store, control new orders during the final database cutover so the two copies do not diverge.

After migration, compare real customer journeys and resource use with the old baseline. Keep the previous service until the agreed checks pass and all required data is preserved.

• Moving a website onto Nabtech Cloud Hosting
• Understanding CPU, memory and resource limits on Cloud Hosting
• Understanding managed hosting responsibilities before you need support
• Comparing a VPS and a dedicated server for a business workload

• Cloud hosting
• Nabtech Terms