To transfer your domain to a new cloud hosting provider without downtime, the secret is simple: don't touch your DNS until your site is already running on the new server. Set everything up at the destination first, verify it works, and only then point your DNS records. Follow this sequence and downtime is zero.
Most people do the opposite — they change DNS first, then migrate files, leaving the site down for hours. This guide shows you the right order.
Before You Start: What You Need to Know
Before moving a single file, answer these questions:
- Who manages your domain? Your domain could be at the same provider as your hosting (GoDaddy, HostGator, Namecheap) or at a separate registrar. Identify where your current DNS lives.
- What is your current DNS TTL? A high TTL (86400 seconds = 24 hours) means changes propagate slowly. A low TTL (300 seconds = 5 minutes) speeds up the transition.
- Do you have email on the current host? MX records need to be migrated or kept separately.
With these answers clear, the process becomes predictable.
Step 1: Lower Your DNS TTL in Advance
Do this step before any migration — ideally 24 to 48 hours ahead of time.
Log in to your domain registrar or DNS provider and lower the TTL on all A, CNAME, and MX records to 300 seconds (5 minutes). This ensures that when you change the IP in the final step, propagation completes in minutes, not hours.
Once the migration is done, raise the TTL back to 3600 or 86400 to reduce load on DNS servers.
Step 2: Set Up the Site on the New Cloud Host
Upload all your files and restore the database on the new server — without touching DNS yet.
- Create the hosting account and add your domain in non-propagated mode (most control panels support this).
- Upload your site files via FTP/SFTP or the panel's file manager.
- Export the database from the old host using
mysqldumpor phpMyAdmin, then import it on the new server. - Update the connection strings in your config files (
wp-config.php,.env, etc.) with the new database credentials. - Configure SSL on the new server. If you use Let's Encrypt, issue the certificate before the DNS change.
Step 3: Verify the New Site Using Your Hosts File
Before changing your official DNS, test that the site works on the new server by editing your local hosts file to force resolution to the new IP.
On Mac/Linux, edit /etc/hosts. On Windows, edit C:\Windows\System32\drivers\etc\hosts. Add this line:
NEW_SERVER_IP yourdomain.com www.yourdomain.comOpen your browser and visit https://yourdomain.com. If the site loads correctly — including images, forms, and the admin panel — you're ready for the DNS change.
When verification is complete, remove that line from the hosts file to return to normal behavior.
Step 4: Update Your DNS Records
With the site verified on the new server, now update the DNS. The key change is the A record:
| Record | Type | Old Value | New Value |
|---|---|---|---|
| @ (root) | A | Old hosting IP | New cloud hosting IP |
| www | CNAME or A | Old IP or CNAME | New IP or CNAME |
| MX | Old mail server | New mail server (if applicable) |
With TTL at 300 seconds, the change propagates in 5–15 minutes for most users. In rare cases, ISPs with aggressive caching can take 1–2 hours.
Step 5: Monitor and Keep the Old Host Active for 48 More Hours
Don't cancel the old hosting immediately. Keep it active for at least 48 hours after the DNS change. This protects users whose ISPs are still resolving the old IP.
Use a tool like dnschecker.org to confirm propagation is complete across major regions. When 95%+ of servers reflect the new IP, you can safely cancel the old hosting.
If you need migration support or a cloud hosting plan optimized for your region, elenlace.com includes full migration assistance with every plan.
Browse more cloud infrastructure tutorials in our cloud hosting section.
Key Takeaways
- Never change DNS before the site is live and verified on the new server.
- Lower TTL to 300 seconds 24–48 hours in advance to speed up propagation.
- Verify the new site with your local
hostsfile before touching official DNS. - Always migrate files and database together — files alone are not enough.
- Keep the old host active for 48 hours after the DNS change as a safety net.
- Use dnschecker.org to confirm propagation is complete before cancelling the old hosting.
Want to migrate to cloud hosting without the hassle? The team at elenlace.com handles the full migration for you — files, database, DNS, and SSL — with zero downtime guaranteed.
FAQ
How long does DNS propagation take when switching hosts?
With a TTL of 300 seconds, most users will see the change within 5–15 minutes. Without lowering the TTL first, it can take up to 24–48 hours depending on the ISP. That's why reducing TTL in advance is critical.
Do I need to transfer the domain or just change the DNS?
These are two different things. Changing DNS (pointing to the new IP) is all you need to get your site running on the new host — this takes minutes. Transferring the domain (moving the registration to another registrar) is optional and can take up to 7 days. To eliminate downtime, you only need a DNS change.
What happens to my email during the migration?
If you host email on the current server, migrate the accounts to the new server before updating your MX records. Set up email on the new host, verify it works, and then update MX records at the same time as your A records. This way email delivery is uninterrupted too.
Can I do the migration without SSH access?
Yes. You can migrate files using the control panel's file manager (cPanel, Plesk) or via FTP, and the database using phpMyAdmin (export from the old host, import to the new one). A full migration without SSH is completely viable for most websites.
Compare providers
Other providers and guides worth comparing:
