Our Cloud Hosting provides a hosting account with the tools and resource allocation shown in your plan. Start by checking those values and your application's requirements. The word cloud does not establish that an account has root access, automatic scaling or hourly billing.
IN THIS ARTICLE
01 Prepare the move
List the websites, databases, mailboxes, scheduled tasks and external services involved. Record your current DNS zone, especially MX and authentication records when business email stays with another provider. Make an independent backup and confirm that you can open it before changing the live site.
- Open the Cloud Hosting service in your client area and review its access details, assigned server address and available management tools. Use the provided cPanel access when required.
- Create the required domains and database users. Confirm the supported PHP or application runtime before copying production files. An available selector is not proof that every version or extension is installed.
- Transfer the website files and import a database copy. Update database credentials, filesystem paths and application settings for the destination. Keep private configuration outside publicly downloadable locations where the application permits.
- Recreate scheduled tasks, outgoing email configuration and any external allowlists. Prevent both old and new scheduled jobs from charging customers or sending duplicate messages during the move.
- Preview the destination and test important customer journeys. Check login, forms, uploads and, for a store, a sandbox order. Confirm the backup method and create a recovery point.
- Schedule the final data copy and DNS change. For a site accepting orders or edits, agree a brief write pause or another application-specific synchronisation method before the final switch.
02 Verify after DNS changes
Check the authoritative records, HTTPS certificate and application logs. Test from more than one network while caches refresh. Leave the previous hosting service available until website and email checks are complete and you have confirmed no important data was written there after the switch.
What should I check if the cloud plan appears too small?
Observe the actual bottleneck before upgrading. CPU, memory, disk space and I/O are different limits. Ask support to review the current plan and a representative time range. Cloud infrastructure does not remove the need to optimise slow database queries, oversized images or expensive background jobs.