Clean DNS migration, verified and zero-downtime
DNS Management and Record Migration
Migrate your DNS to Cloudflare, Route 53, or any standard provider with full record audit and a zero-downtime cutover.
Service Overview
Clients migrating DNS to Cloudflare, Route 53, or registrar DNS get a clean, verified transition with zero-downtime cutover. Every A, MX, CNAME, and TXT record is audited, staged, and verified on both sides before the NS change is published.
Moving DNS between providers carries real operational risk. A misconfigured MX record drops email, a missed subdomain breaks a staging environment, and a poorly timed cutover puts sites offline during propagation. This add-on removes that risk. We audit your current zone, stage every record on the new provider, and coordinate the switch so the cutover is clean and verified end to end.
What you get
The work is scoped per domain and covers the full DNS footprint, so A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, SRV, and NS records. We pull every record from the source provider, review it for accuracy and intent, stage it on the target provider (typically Cloudflare, AWS Route 53, Google Cloud DNS, or registrar-level DNS), and then coordinate the cutover with you on a scheduled window. Propagation is monitored across major global resolvers, and a post-cutover verification pass confirms that email delivery, web resolution, and third-party integrations are all intact.
How the zero-downtime cutover works
TTL values on the source zone are lowered 24 to 48 hours before the switch, so propagation happens fast once the NS change is published. The target zone is fully seeded and tested against the new nameservers before the NS update, which means resolvers see a complete, working zone the moment they pick up the change. There is no window where records are missing or partial.
Who this is for
Buy this if you are moving DNS from your hosting provider to Cloudflare or AWS Route 53, consolidating DNS from multiple registrars onto a single provider, or cleaning up a historically messy zone as part of a migration. It is also useful when switching email platforms, because the MX, SPF, DKIM, and DMARC chain has to move together without breaking delivery.
Zero-downtime cutover
Records staged and TTL lowered in advance so the NS switch publishes a complete, working zone instantly.
Multi-provider DNS
Cloudflare, AWS Route 53, Google Cloud DNS, and registrar DNS — pick the target that fits your stack.
Verified end to end
Every A, MX, CNAME, and TXT record is audited and re-verified for 7 days after cutover.
What is Included
Checklist
How It Works
Audit
We pull the complete zone from the source provider and review every record for accuracy and intent.
Stage
All records are created on the target provider and tested against the new nameservers before any public change.
Lower TTL
Source zone TTL is reduced 24 to 48 hours before cutover, so propagation moves quickly when the NS change is pushed.
Cutover
Nameservers are switched at the agreed window and propagation is monitored across major global resolvers end to end.
Verify
A post-cutover pass confirms web resolution, email delivery, and third-party integrations work against the new zone.
None for typical setups. We lower the source-zone TTL 24 to 48 hours in advance and pre-seed the target zone, so the moment the NS change is published, resolvers pick up a complete, working zone. Web traffic, email, and integrations stay reachable throughout.
Cloudflare, AWS Route 53, Google Cloud DNS, and registrar-level DNS at most standard providers including GoDaddy, Namecheap, and ResellerClub. If your target is unusual, send us the provider name before ordering and we will confirm compatibility.
Yes. Email records move together with the rest of the zone so inbound and outbound delivery stays intact. We do not, however, handle mailbox migration or email-platform setup — that is a separate engagement.
Administrative access to both the source DNS provider and the target DNS provider. Without both sides we cannot stage records or publish the NS change. Credentials are treated as confidential and are not retained after handover.
Audit and staging complete within 2 business days of receiving access. The cutover itself is scheduled at a window you agree to, and the NS switch typically propagates within 15 minutes globally.
Post-cutover verification runs for 7 days. Any discrepancy that comes from the migration work is fixed at no extra cost within that window. Issues caused by upstream outages or undisclosed source-side misconfiguration sit outside that warranty.
One domain per unit. Buy additional units for additional domains. We can sequence multiple-domain migrations in a single engagement on request.
No. Procurement of the target DNS service — Cloudflare plan, AWS account, registrar upgrade, and so on — is your responsibility. This service covers the record migration work only.
- Service is billed per domain on a one-time basis. Payment is due at the time of order.
- You are responsible for providing administrative access to both the source DNS provider and the target DNS provider. Without access to both sides, the migration cannot be completed.
- Scheduling of the cutover window requires mutual agreement. We recommend scheduling outside business hours to minimise exposure to business operations.
- The service covers DNS records only. Procurement of the target DNS service (Cloudflare subscription, AWS account, registrar upgrade, and so on) is your responsibility and is not included in this fee.
- Refunds are available within 24 hours of order if the audit has not yet started. Once record mapping begins, the service is considered in progress and is not refundable.
- We verify post-cutover that all migrated records resolve correctly against the new nameservers. Any discrepancy identified within 7 days of cutover is remediated at no additional cost, provided the discrepancy results from the migration work.
- Issues caused by upstream provider outages, registrar policy changes, or misconfiguration at the source that was not disclosed during the audit are out of scope.
- All credentials shared for migration purposes are treated as confidential and are not retained after the work is completed. You are advised to rotate credentials once the handover is complete.
- This service does not include ongoing DNS management. For continuous monitoring, buy a maintenance plan or a separate monitoring add-on.
Related Services
You might also be interested in these services.
End-to-end SSL certificate installation with mixed content fix, HTTPS redirects, and an independent SSL Labs grade re...
A unified maintenance program that combines security, backups, monitoring, performance, SEO, and human support - mana...
New
Businesses building a newsletter or nurture funnel get their website forms connected to Mailchimp, Klaviyo, or a simi...
Sites with a history of URL changes or migrations get a full audit across 8 HTTP error code categories, proper 301 re...
WooCommerce stores get live shipping rates at checkout and automated label generation through direct integration with...
WooCommerce stores launching or migrating a catalog get products live with full metadata, no self-serve typing. Each ...