How to migrate to ChemiCloud
Moving an existing site to ChemiCloud — what they handle for you, what you'll do yourself, and the safe order to do it in.
Choosing a Plan: Match Your Current Footprint
Starter ($2.49/mo) fits static sites under 20GB, while Turbo ($4.49/mo) handles 50GB databases and 6GB RAM workloads. Renewals jump to $11.95–$21.95, so benchmark against the 1121ms server response time — if your current host averages faster, the price/performance tradeoff may not hold. The 45-day refund window lets you test this risk-free.
Pre-Migration: Lower DNS TTL and Backup
Set your DNS TTL to 300 seconds (5 minutes) at least 48 hours before migrating. This minimizes downtime during cutover. Export a full backup: databases as SQL dumps, files via SFTP/rsync. ChemiCloud’s free SSL (verified on all plans) means no certificate reissuing is needed if your current site uses HTTPS.
Transfer and Test on Temporary URLs
Upload files to the new server via FTP or file manager. Import databases using phpMyAdmin or CLI tools. ChemiCloud provides a temporary URL (e.g., server.ip/~username) to verify functionality before DNS changes. Check:
- Page load consistency (3193ms fully loaded in tests)
- Database queries (1053ms server processing time)
- Mixed content warnings (free SSL auto-installs)
DNS Cutover and Post-Migration Checks
Update nameservers or A records. Monitor:
- DNS propagation (2ms lookup time in benchmarks)
- TLS handshake speed (35ms verified)
- Global response (996ms North America latency; use tools like Pingdom to compare regions)
Support via live chat or ticket if anomalies persist. Keep old host active for 72 hours as a fallback.