Migrating your DNS management to Cloudflare from your current registrar means carefully recreating every existing DNS record before switching nameservers, since a missed record (an email MX entry, a subdomain) can cause a real, disruptive outage the moment the switch takes effect.
Cloudflare DNS migration from registrar
DNS migrated to Cloudflare with every existing record verified before nameservers switch.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your current registrar’s DNS management to review existing records
- A Cloudflare account, or agreement to set one up as part of this
- Your preferred timing for the actual nameserver cutover, ideally during lower-traffic hours
This or something else?
| You want your DNS migrated to Cloudflare, with every existing record correctly preserved | This fix covers it |
| You already have Cloudflare configured for your DNS and want other settings reviewed instead | Cloudflare full configuration audit & setup |
| You want registrar-level DNS changes without migrating to Cloudflare specifically | Registrar-level DNS & nameserver changes |
| You’re changing hosting providers entirely, not just DNS management | Host-to-host migration – single site, in the Backups, Staging & Migration Ops category |
What we do
- Document every existing DNS record at your current registrar
- Recreate each record accurately within Cloudflare
- Verify the recreated records match exactly before any cutover
- Update nameservers at your registrar to point to Cloudflare at the agreed time
- Monitor propagation and verify every service (website, email, subdomains) continues working correctly
- Confirm the migration is complete and stable before considering it finished
What is included
- A complete, verified migration of every DNS record to Cloudflare
- Nameserver cutover managed at your agreed time
- Post-cutover verification of every affected service
- Monitoring through the propagation period
Not included
- Setting up new DNS records that didn’t already exist, unless specifically requested as part of the migration
- Broader Cloudflare configuration beyond DNS migration itself — a separate, related fix if also needed
- Changing your actual hosting provider, a separate, larger migration
- Ongoing DNS management after the migration is complete
Questions about this fix
What happens if a DNS record gets missed during migration?
A missed record — commonly an email-related MX entry or a subdomain — can cause that specific service to break the moment nameservers switch, which is exactly why we document and verify every existing record carefully before any cutover happens.
Will this cause any downtime for my website or email?
If every record is correctly migrated and verified before cutover, disruption should be minimal — DNS propagation can introduce a brief window of inconsistency, which is normal and expected rather than a sign of an error.
Do I need to do anything with my registrar myself?
You'd typically need to authorize the nameserver change at your registrar, since that's an account-level action tied to your ownership — we'd guide you through exactly what's needed at that step.
Can I switch back to my old DNS setup if something goes wrong?
Yes, nameserver changes are reversible, and we'd keep the original configuration documented specifically so a rollback is straightforward if genuinely needed, though careful pre-migration verification aims to make that unnecessary.
Will my email stop working during this migration?
Email-related DNS records (MX entries) are specifically among the most critical to get right, and we prioritise verifying these carefully, since email disruption is one of the most disruptive possible outcomes of a DNS migration done carelessly.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.