Moving your website’s DNS to Cloudflare is one of the smartest things you can do for your small website. It makes your site faster, safer, and more reliable. But if you skip steps during a Cloudflare DNS migration, things can go wrong. Your email might stop working. Your website could go offline. That is why you need a clear checklist.
This guide walks you through every step of a Cloudflare DNS migration. We use simple words and short steps. Even if you are new to DNS, you can follow this guide. By the end, your website will be running on Cloudflare with zero downtime.
What You’ll Need Before Starting Your Cloudflare DNS Migration
Before you start your Cloudflare DNS migration, gather everything you need. Think of it like packing for a trip. You do not want to stop halfway because you forgot something important.
Required Credentials and Access
You need login details for three things:
- Your domain registrar account. This is where you bought your domain name (like Namecheap, GoDaddy, or Google Domains). You need this to change nameservers.
- Your current DNS provider account. If your DNS is separate from your registrar, you need this to export records.
- A free Cloudflare account. Sign up at cloudflare.com if you have not already.
Write down all passwords. Make sure you have admin access to each account.
Understanding Your Current DNS Setup
Before a Cloudflare DNS migration, know what you have now. DNS records are like a phone book for your website. They tell the internet where to find your site, email, and other services. Common record types include:
- A records — point your domain to an IP address
- CNAME records — point one name to another name
- MX records — handle your email delivery
- TXT records — verify ownership and set email security
If you do not know what these mean, that is okay. We will explain each one as we go.
Estimated Timeline for Each Migration Phase
| Phase | Task | Time Needed |
|---|---|---|
| Phase 1 | Pre-Migration Planning | 1–2 hours |
| Phase 2 | Preparation in Cloudflare | 1–2 hours |
| Phase 3 | Nameserver Switch | 5 minutes (then wait 1–24 hours) |
| Phase 4 | Post-Migration Testing | 1–2 hours |
A full Cloudflare DNS migration usually takes one weekend. The actual switch is fast. The waiting part is the longest.
Phase 1: Pre-Migration Planning Checklist for Cloudflare DNS
Good planning prevents problems. This phase is about understanding everything your current DNS does before you move it.
Audit All Existing DNS Records (A, AAAA, CNAME, MX, TXT, SRV)
Log in to your current DNS provider. Find the DNS management page. Write down every record you see. Here is what to look for:
- A records — These point your domain (example.com) to your server IP.
- AAAA records — Same as A records but for IPv6 addresses.
- CNAME records — These alias one name to another (like www pointing to your main domain).
- MX records — These direct email to your mail server. Do not skip these.
- TXT records — These include verification codes and email security settings.
- SRV records — These are used for specific services like voice chat or gaming.
Take screenshots. Copy everything into a spreadsheet. You will need this list later.
Document Email Dependencies (SPF, DKIM, DMARC Records)
Email records are the most common thing people break during a Cloudflare DNS migration. Look for these TXT records:
- SPF — Starts with “v=spf1”. It tells the world which servers can send email for your domain.
- DKIM — Contains a public key. It proves your emails are real.
- DMARC — Starts with “v=DMARC1”. It tells receivers what to do with bad emails.
Copy the exact values. Even one wrong character can break your email.
Identify Third-Party Service Verifications and Subdomain Delegations
Many services verify that you own your domain. They add TXT records for this. Common ones include:
- Google Workspace or Microsoft 365 verification
- SSL certificate validation (like Let’s Encrypt)
- Social media verification (Facebook, Twitter)
- Analytics tools (Google Search Console)
Also check for NS records. These delegate a subdomain to another provider. For example, if a shop subdomain points to Shopify, you need to keep that NS record.
Choose the Right Cloudflare Plan (Free vs. Pro for Small Websites)
For most small websites, the free Cloudflare plan is enough. It includes:
- Global DNS with fast response times
- Free SSL certificates
- Basic DDoS protection
- Unlimited DNS queries
The Pro plan ($20/month) adds image optimization, advanced analytics, and more. You can always upgrade later. Start with free for your Cloudflare DNS migration.
Phase 2: Preparation Checklist for Zero-Downtime Cloudflare DNS Migration
This phase is where you set everything up in Cloudflare before switching. The goal is zero downtime. Your website should keep working the entire time.
Lower TTL Values 24–48 Hours Before Migration
TTL stands for “Time to Live.” It tells other DNS servers how long to cache your records. If your TTL is 24 hours, changes take up to 24 hours to spread.
- Go to your current DNS provider.
- Find the TTL setting for each record.
- Change all TTLs to 300 seconds (5 minutes).
- Do this 24 to 48 hours before your Cloudflare DNS migration.
This way, when you switch nameservers, the change spreads fast. After the migration, you can raise TTLs back to normal.
Export Your Current Zone File from Existing Provider
Most DNS providers let you export your records as a zone file. This is a text file with all your DNS records.
- Log in to your current DNS provider.
- Look for an “Export” or “Download Zone File” option.
- Save the file to your computer.
If your provider does not offer export, use the list you made in Phase 1. You will enter records manually.
Add Your Domain to Cloudflare and Import DNS Records
- Log in to your Cloudflare dashboard.
- Click “Add a Site.”
- Type your domain name and click Continue.
- Select the Free plan.
- Cloudflare will scan for existing DNS records.
- Review the imported records. Compare them with your list from Phase 1.
- Add any missing records by hand.
This is the core of your Cloudflare DNS migration. Every record must be correct.
Handle DNSSEC: Disable at Current Provider Before Cutover
DNSSEC adds a security layer to DNS. If it is on at your old provider, you must turn it off before switching. Otherwise, visitors may see errors.
- Check your current provider for DNSSEC settings.
- If enabled, disable it.
- Wait 24 hours for the change to spread.
- After your Cloudflare DNS migration is complete, you can enable DNSSEC in Cloudflare.
Verify All Records Match in Cloudflare Dashboard
Go through every record in Cloudflare. Compare each one with your original list. Check:
- Record type (A, CNAME, MX, etc.)
- Name (the subdomain or @ for root)
- Value (the IP address or target)
- Priority (for MX records)
Even small mistakes can cause big problems. Double-check everything.
Prepare SSL/TLS Settings and Proxy Status for Each Record
In Cloudflare, each DNS record has a proxy status. You see a cloud icon:
- Orange cloud (Proxied) — Traffic goes through Cloudflare. You get CDN, security, and caching.
- Gray cloud (DNS Only) — Traffic goes directly to your server. No Cloudflare features.
For your main website (A and CNAME records for www and @), turn on the orange cloud. For MX records and some TXT records, keep them gray. This is important for a smooth Cloudflare DNS migration.
Phase 3: Execution Checklist — Switching Nameservers to Cloudflare
This is the moment of truth. You are about to point your domain to Cloudflare’s nameservers. Follow each step carefully.
Retrieve Your Cloudflare Nameserver Addresses
- In your Cloudflare dashboard, find your domain.
- Look for the “Nameservers” section.
- You will see two addresses like: anna.ns.cloudflare.com and bob.ns.cloudflare.com.
- Copy both addresses.
Log In to Your Domain Registrar and Update Nameservers
- Log in to your domain registrar (where you bought your domain).
- Find the DNS or nameserver settings page.
- Replace the old nameservers with your two Cloudflare nameservers.
- Remove all old nameserver entries.
- Save changes.
Confirm Nameserver Changes Are Saved
After saving, go back to the page. Refresh it. Make sure the new Cloudflare nameservers are showing. Some registrars take a few minutes to update the display.
Monitor DNS Propagation (Tools and Expected Timeframes)
Nameserver changes take time to spread across the internet. This is called DNS propagation.
- Use a tool like whatsmydns.net or dnschecker.org.
- Enter your domain name.
- Select “NS” as the record type.
- Check results from different locations around the world.
Most of the time, propagation finishes within 1–4 hours. But it can take up to 24 hours. During a Cloudflare DNS migration, be patient.
Keep Old DNS Provider Active as Fallback During Transition
Do not cancel your old DNS provider yet. Keep it active for at least 7 days. If something goes wrong with your Cloudflare DNS migration, you can switch back quickly. Your old records will still be there.
Phase 4: Post-Migration Validation Checklist for Cloudflare DNS
The nameservers have changed. Now you need to test everything. This phase makes sure your Cloudflare DNS migration was successful.
Test Website Accessibility and Page Load Performance
- Open your website in a browser.
- Check that it loads correctly on desktop and mobile.
- Test both http:// and https:// versions.
- Use Cloudflare’s speed test or Google PageSpeed Insights to check performance.
- Make sure all pages, images, and links work.
Verify Email Delivery (Send/Receive Test for All Mailboxes)
- Send a test email from your domain to a Gmail account.
- Send a test email from Gmail to your domain.
- Check all mailboxes if you have multiple.
- Verify emails do not go to spam folders.
If email fails, check your MX, SPF, DKIM, and DMARC records in Cloudflare. This is the most common issue after a Cloudflare DNS migration.
Confirm Third-Party Services Still Function (SSL Certs, APIs, Webhooks)
- Check that your SSL certificate is active. In Cloudflare, go to SSL/TLS settings and make sure it shows “Active.”
- Test any APIs that connect to your domain.
- Verify webhooks are still sending data.
- Check analytics tools to make sure they still track your site.
Re-enable DNSSEC in Cloudflare (If Previously Used)
- Go to your Cloudflare dashboard.
- Navigate to DNS → Settings.
- Find DNSSEC and click “Enable.”
- Cloudflare will handle the rest automatically.
Optimize TTL Values and Enable Cloudflare Proxy Features
Now that your Cloudflare DNS migration is stable, you can raise TTL values back to normal (like 1 hour or 4 hours). This reduces the load on DNS servers. Also explore Cloudflare features like:
- Page Rules for caching
- Browser Cache TTL settings
- Always Use HTTPS
- Automatic HTTPS Rewrites
Decommission Old DNS Provider Safely
After 7 days of smooth operation, you can remove your domain from the old DNS provider. But keep your domain registration active. You are only moving DNS, not the domain itself.
Common Mistakes to Avoid During Cloudflare DNS Migration
Many people make the same mistakes during a Cloudflare DNS migration. Here is how to avoid them.
Forgetting to Lower TTLs Before the Cutover
If you skip this step, your old DNS records will stay cached for hours. Visitors may see the old version of your site while others see the new one. Always lower TTLs 24–48 hours before.
Missing Hidden DNS Records (Verification TXT, Delegated Subdomains)
Some records are easy to miss. Verification TXT records for Google or social media often sit quietly in your DNS. NS records that delegate subdomains are also easy to forget. Always do a full audit.
Breaking Email Flow by Overlooking MX or SPF Records
This is the number one problem. If you forget to copy MX records, email stops. If you get SPF values wrong, your emails go to spam. Always test email after your Cloudflare DNS migration.
Enabling Proxy (Orange Cloud) on Records That Should Stay DNS-Only
Not all records should go through Cloudflare’s proxy. MX records should always be DNS-only (gray cloud). Some API endpoints may also need direct access. If you orange-cloud the wrong record, services can break.
Removing Old DNS Provider Too Quickly
Give yourself at least 7 days before removing the old provider. Some visitors and services may still use cached old DNS records. Rushing this step is a common Cloudflare DNS migration mistake.
Cloudflare DNS Migration Rollback Plan: What to Do If Something Goes Wrong
Sometimes things go wrong. Having a rollback plan gives you peace of mind during your Cloudflare DNS migration.
Signs Your Migration Has Issues
- Your website shows an error page or does not load
- Email bounces or goes to spam
- SSL certificate warnings appear in browsers
- Third-party services report connection failures
- DNS lookup tools show incorrect records
How to Revert Nameservers to Your Previous Provider
- Log in to your domain registrar.
- Go to nameserver settings.
- Replace Cloudflare nameservers with your old nameservers.
- Save changes.
- Wait for propagation (usually 1–4 hours).
This is why you kept your old DNS provider active. The rollback is fast and simple.
Post-Rollback Validation Steps
After reverting, test everything again:
- Check website loads correctly.
- Send and receive test emails.
- Verify SSL certificates work.
- Fix the issue in Cloudflare before trying the Cloudflare DNS migration again.
FAQ: Cloudflare DNS Migration Checklist Questions
How Long Does a Cloudflare DNS Migration Take?
The active work takes 2–4 hours. But DNS propagation can take 1–24 hours. Plan for a full day. Most Cloudflare DNS migration projects finish within a few hours in practice.
Will My Website Go Down During the Cloudflare DNS Migration?
If you follow this checklist, no. Your website stays online the entire time. The key is lowering TTLs first and making sure all records are correct in Cloudflare before switching nameservers.
Do I Need to Transfer My Domain Registrar to Cloudflare?
No. A Cloudflare DNS migration only changes your DNS. Your domain stays at your current registrar. You can transfer the domain later if you want, but it is not required.
What Happens to My Email During Cloudflare DNS Migration?
Email keeps working if you copy all MX, SPF, DKIM, and DMARC records correctly to Cloudflare. Test email before and after the switch. If you followed every step, email should not be affected.
Is the Cloudflare Free Plan Enough for Small Website DNS Migration?
Yes. The free plan includes everything you need for DNS: fast global DNS, free SSL, DDoS protection, and unlimited queries. Most small websites do not need the Pro plan. Start free and upgrade only if you need more features later.
Final Thoughts: Completing Your Cloudflare DNS Migration with Confidence
A Cloudflare DNS migration does not have to be scary. With this checklist, you have a clear path from start to finish. Here are the key takeaways:
- Plan first. Audit every DNS record before you touch anything.
- Prepare carefully. Lower TTLs, import records, and verify everything in Cloudflare.
- Execute with confidence. Switch nameservers and monitor propagation.
- Validate everything. Test your website, email, and third-party services.
- Have a rollback plan. Keep your old DNS provider active for at least 7 days.
Cloudflare makes your website faster and safer. The migration is a one-time effort that pays off every day. Follow this Cloudflare DNS migration checklist step by step, and you will complete the move with zero downtime and zero stress. Your small website deserves the best, and Cloudflare delivers exactly that.