Describe how the website works
List the CMS, important functions and external services. A company page, blog and shop have different requirements. Decide who publishes content and handles updates. If the website is already running, review traffic and resource usage. This lets you choose based on information rather than assumptions, and explains what the new environment must support.
Review environment parameters
Disk capacity does not replace details about CPU, memory and process limits. PHP and database compatibility matter. Ask about scheduled tasks, log access and changing environment versions. For a shop, include integrations, database load and campaign traffic. The useful comparison is whether the service supports your actual workload and application requirements.
Agree backup and support arrangements
Check what is copied, how often and how long backups remain available. Ask about recovery procedures and the support scope. Hosting does not always include code repairs or CMS updates. Responsibilities should be clear. Important data may also need an independent archive in addition to the operator’s standard backups.
Plan growth and migration
Find out how service parameters can change and when a VPS might be needed. For migration, check access requirements, email transfer scope and tests before DNS changes. Keep the previous environment until verification finishes. Request a service summary so that you compare actual conditions rather than package names alone.