How to migrate to Cloudways
Moving an existing site to Cloudways — what they handle for you, what you'll do yourself, and the safe order to do it in.
Pre-Migration Checklist
Back up everything — databases, files, configurations. Cloudways doesn’t list free migration in the DATA PACK, so assume manual or third-party tools. Lower DNS TTL to 300 seconds (5 mins) at least 48 hours before cutover to minimize downtime.
File and Database Transfer
No cPanel/Plesa mentioned — this is a managed cloud setup (DigitalOcean 1GB). Use SFTP/SSH for files (standard Linux server access) and export/import databases via CLI or tools like MySQL Workbench. Screenshots confirm $11/mo for DO 1GB (25GB storage, 1 vCPU), but no free SSL — budget for a certificate if needed.
Testing Before DNS Cutover
Cloudways provides no temporary URL in the DATA PACK. Test by modifying your local hosts file to point to the new server’s IP (found in their dashboard post-setup). Verify TTFB (139ms in benchmarks) and fully loaded time (352ms) match expectations for your region.
Final DNS Switch and Support
Update DNS records (A/AAAA/CNAME). Monitor uptime (100% over 30/90/365 days per data). If issues arise, use 24/7 live chat or tickets — no phone support listed. Datacenters span NYC, Amsterdam, Frankfurt, London, Singapore, Tokyo, Sydney, Bangalore, Toronto; pick the one closest to your audience.