How to move a client domain with near-zero downtime: a day-by-day cutover plan
Short answer: To move a client's domain with near-zero downtime, build and test the new site first, lower the DNS TTL (the number of seconds other computers remember an address) ahead of time, get the new host's security certificate ready before you switch, then change only the website records (the A record and the www record) and leave email records alone. Keep the old host running until its traffic drops to zero, so you can roll back. Nobody can promise zero downtime, but this order removes the usual causes: certificate errors, cached old addresses and broken email.
You have a client's domain to move to a new host and you want visitors and email to keep working the whole time.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Downtime during a domain move almost never comes from DNS (the system that tells the internet where a website and its email live) being slow. It comes from order. The new host is not ready, the security certificate (the thing that makes the padlock work) is missing when the address switches, or someone replaces too many records and email stops. This page gives you an order that avoids all three, with a day-by-day plan you can paste into a ticket.
It works for any host. I use Ploy, an AI platform that builds and hosts websites, as the worked example because its docs publish exact cutover steps. Ploy is one option, and the plan stands on its own if you use another host.
This page may contain affiliate links from which Blur Studio earns commissions.
The five words you need
- DNS: the settings that tell the internet which computer serves a name. You edit them at your domain registrar (where the domain was bought) or at a DNS host such as Cloudflare, a company that runs DNS and website security services.
- A record: points the bare domain (example.com) at a numeric address.
- CNAME record: points one name (such as www) at another name.
- TTL (time to live): how many seconds other computers keep an answer before asking again. A low TTL means a change reaches people sooner. It also means a change back reaches them sooner.
- MX, SPF, DKIM and DMARC records: the records that deliver and protect email. A website move should never change them.
For a beginner's setup walk-through of a single domain, see custom domain, DNS and SSL setup. This page is the cutover plan around it.
The plan, day by day
Day numbers count back from the switch (T0). Spread them out if the client's site matters more than your schedule.
| When | What you do | Why |
|---|---|---|
| T-7 | Record every DNS record. Lower the TTL on the A and www records. Confirm who has registrar and DNS logins. | Google's site-move guide says to lower TTL at least a week in advance. The old, higher TTL must run out before the low one takes effect. |
| T-5 | Publish the new site on its host's test address. Test every page, form and phone number. | You find problems while no visitor is affected. |
| T-3 | Build the redirect sheet for any address that changes. Load redirects on the new host. | Redirects are part of the cutover, not an afterthought. |
| T-2 | Add the host's certificate verification records. Wait until the host confirms the certificate is issued. | The new host can serve secure pages the moment the address moves. |
| T-1 | Remove temporary noindex tags and robots blocks from the new site. Re-check forms and tracking. | Google says to remove them before you update DNS, or search engines may skip the new site. |
| T0 | Change only the A record and the www record. Check on your phone using mobile data. | Smallest possible change. |
| T+1 | Check Search Console, forms, and logs on both hosts. Send a test email to and from the domain. | Catches silent failures. |
| T+7 and later | Retire the old host only when its logs show traffic near zero. Keep redirects for at least a year. | Google says redirects should stay generally at least one year. |
Step 1: the TTL question, with both sides
Advice differs on TTL, so here is who says what. Google's guide for moving a site without changing its addresses says to lower the TTL to a conservative low value, for example a few hours, at least a week in advance. Ploy's migration checklist says to lower the TTL on the A record and the www record to 300 seconds before migration day, and gives no lead time. Ploy's DNS setup page says 60 to 300 seconds. Cloudflare's own TTL page does not tell you to lower anything, and it says records Cloudflare proxies (passes traffic through its network) are fixed at Auto, which is 300 seconds, and cannot be edited.
My rule: follow Google and lower it at least a week ahead where you can. If you are short of time, lower it as early as you can, and never closer to the switch than the old TTL. If the old TTL is 86,400 seconds (one day), lowering it an hour before does little, because computers that cached the old answer keep it for up to a day. The same rule governs rollback. If you lower it too late, going back is as slow as going forward.
Check what you have before you start. On a Mac or Linux terminal, dig A example.com shows the current TTL in the answer. Your DNS host's control panel also shows it.
Step 2: keep email safe
The cardinal rule: change only the A record and the www CNAME (plus add the certificate records your host gives you). Do not delete MX, SPF, DKIM or DMARC records, and never choose "reset to default" or replace the whole zone. A change of nameservers (the setting that says who controls all your DNS) can make email records disappear. Ploy's docs say it does not need to take over your nameservers, and many other hosts work the same way, but check yours.
- Before you start, export or screenshot every record.
- Put the screenshot in the client file with the date.
- After the switch, send an email to the domain from an outside address and one from the domain to an outside address.
- If the client uses Google Workspace or Microsoft 365 (business email services), do not edit their records without reading their setup pages first.
The long version is in pointing a domain at a new website without breaking email.
Step 3: get the certificate ready before you switch
A visitor who reaches a host with no certificate sees a security warning, which looks like downtime. The fix is to prove ownership of the domain while the old site is still serving. Let's Encrypt, a free certificate authority, describes this as DNS-01 validation: you publish a record named _acme-challenge and the authority checks it. It also says you can use a CNAME to delegate that answer to another zone. The idea is that the certificate can be ready before the traffic arrives.
Ploy's docs follow this pattern. In Ploy's DNS setup guide you add two _acme-challenge CNAME records first. Ploy states these do not affect live traffic. You leave the A record and www pointing at the old host, confirm with Ploy that the SSL certificate has been issued, and only then switch the A record and www. Ploy then detects the change and marks the domain Live. Ploy's pages say waiting for DNS can take up to 24 hours and that issuance after DNS verifies usually takes a few minutes. This is Ploy's own description, so run it on a low-risk domain first.
Ploy's published values, as of its DNS setup page updated 10 November 2026: A record @ pointing to 207.207.209.209 and CNAME www pointing to proxy.runploy.com. Do not copy these from this page. Copy them from the Domains screen in your own Ploy dashboard, because the value of the _acme-challenge records contains a code that is specific to your setup, and the address can change. Some registrars want the name blank instead of @, and some need a dot at the end of a CNAME value, so match what the dashboard shows.
- Cloudflare users: set each of the records to DNS only (the grey cloud). Ploy's docs say the Flexible SSL mode causes redirect loops, so use Full (strict) or DNS only. Make sure any CAA record (a record that lists which companies may issue certificates) allows Google Trust Services.
- Other hosts: the same logic applies. Ask for the certificate-validation records and the date by which a certificate will exist before the switch.
- Do not redirect the challenge path. Vercel's docs say
/.well-known/acme-challengecannot be redirected or rewritten. On any host, do not add a redirect rule that catches it.
Step 4: choose a whole-domain cutover or a staged one
You can switch every page at once or section by section. Google's guide says small and medium sites generally move all at once, and that large sites can move in sections. A staged move is a risk choice, not a Google recommendation.
To stage a move on Ploy, point the domain at Ploy first, then use route rules. Ploy acts as a reverse proxy (a middle server that receives every request and forwards it). Paths are checked top to bottom, the first match wins, and the last row, "Everything else", can send unmoved pages to your old host while keeping your domain in the address bar. Ploy says changes usually take effect within 60 seconds, and gives you an Undo and a History of saved versions. If the screen says an edge sync failed, use Retry and do not assume the new routing is live. Ploy's docs do not say whether the proxy passes through the old host's canonical tags, so view the source of a proxied page and check that its canonical points to your domain.
This also gives you a fast rollback: delete the rule and wait about a minute. For the staged method in more depth, see how Ploy migration works.
Step 5: redirects, trailing slashes and sitemaps
- Use permanent redirects (301 or 308) and avoid chains, ideally three hops or fewer, per Google.
- Do not send many old pages to one unrelated page. Google may treat them as soft errors.
- Ploy's pages drop the trailing slash by default (
/about/goes to/about). SettingtrailingSlash: "always"inastro.config.mjskeeps it. Decide before launch. - Ploy groups redirects into shared rules and asks you to contact support before migration day if you need more than 20 rules.
- The old sitemap does not carry over. Submit the new one in Search Console, and keep both listed in robots.txt if part of the site stays on the old host.
If rankings do slip after the move, work through the ranking recovery checklist.
Step 6: how to confirm the move worked
- Open the site on a phone using mobile data, which skips your office's cached answers.
- Run
dig A example.com +shortanddig CNAME www.example.com +shortand compare with the new host's values. - Check the padlock on the bare domain and on www, and open one page that redirects.
- Submit every form and confirm the email arrives.
- Send and receive test email on the domain.
- In Search Console, run URL Inspection on the home page and one deep page.
- Watch logs on both hosts. Old-host traffic should fall toward zero.
Ploy's docs say that if the dashboard shows the domain as Live, the DNS update is working, and rolling DNS back at that point undoes a successful setup. If you still see old content, wait, test from a different network, and only then decide.
Step 7: the rollback plan
Write the rollback before the switch, as three lines: the trigger (for example "forms fail or the padlock fails for 30 minutes"), the action (put the old A and www values back), and who does it. While the old host is still serving and your TTL is low, going back means re-pointing the records. Remember that the old TTL, not the new one, governs how fast computers that cached the old answer let go. Keep the old host running until its logs show traffic near zero, as Google advises.
Failure modes
- Security warning after the switch. Usually the certificate had not been issued yet, or Cloudflare was set to Flexible. Fix the setting and check again.
- Too many redirects. A redirect rule at the registrar or CDN (content delivery network) conflicts with the new host. Disable the older rule.
- Another platform still holds the domain. Ploy lists a Cloudflare 1034 error for this. Remove the domain from the old platform first. For a Webflow site, remove the domain at least 5 minutes before you verify on Ploy.
- Email stops. Someone edited MX or SPF. Restore from your screenshot.
- Google skips the new site. A noindex tag or a Disallow rule was left over from testing.
Options for who does it
- Stay on the current host. If the problem is a slow or unreliable host, ask them to fix it before you move anything. Free to ask.
- A freelancer. Quote or hourly. Ask for the written cutover plan above.
- An agency. By quote. Best for several domains or heavy traffic.
- A custom-coded site by a developer. By quote, with its own hosting set-up.
- Ploy. It hosts sites at the edge with automatic SSL. As of November 2026, its pricing page lists one custom domain family on Starter at $50 a month (billed monthly) and five on Pro at $300 a month (billed monthly), with the Free plan at $0 and no custom domain. Annual billing is lower. A domain family covers the bare domain, www and subdomains. Ploy's docs say unused credits do not carry over. Check Ploy's current plans before you rely on these numbers.
When not to use this setup
- You cannot reach the DNS logins. Fix that first.
- The client cannot tolerate any chance of a certificate error. Get the host's written cutover support on a call.
- The site has a store or booking system you cannot test on the new host. Keep that part where it is, and move the pages only.
- You need a signed statement about uptime. Ploy's own page on hosting speed and uptime is covered in Ploy hosting speed and uptime; read it and ask for the current terms.
Copy-ready checklist
- Registrar and DNS logins confirmed.
- All DNS records exported and dated.
- TTL on A and www lowered a day to a week ahead.
- New site tested on its test address, forms included.
- Redirect sheet loaded.
- Certificate records added, certificate confirmed as issued.
- noindex and robots blocks removed.
- Rollback trigger and owner written down.
- T0: only A and www changed.
- Mobile data check, forms, email, Search Console.
- Old host kept until traffic reaches zero. Redirects kept at least a year.
How I'd approach this
I would never do a cutover without a written plan, a screenshot of the DNS, and an agreed rollback. For a small client site I would book the switch for a quiet weekday morning, so a problem is found by people who can fix it. The week before is where the work is. If the host's certificate is ready and the redirect sheet is loaded, T0 is a two-record change that takes minutes.
First-week plan: Monday, export the records and lower the TTL. Tuesday, finish testing on the test address. Wednesday, redirects and certificate records. Thursday, remove the testing blocks and rehearse the rollback. Friday morning, switch. If you want help with the hosting set-up, ongoing care or monitoring, Blur Studio does that work; see what it includes.
For the next step, see How to Move Your Site and Keep the Forms You Already Use.
For the next step, see Can My Site Be Moved? How to Check Before You Commit.
A closely related page covers the same ground from another angle: How to Move Your CMS Content Into One Place.
Questions people ask
Is zero-downtime domain migration possible?
Near-zero is realistic if the new site is tested, the certificate is ready before the switch, and you change only the website records. Nobody can guarantee zero, because caches outside your control keep old answers for as long as the old TTL says.
How long before the move should I lower the TTL?
Google's guide says at least a week in advance, to a value such as a few hours. Ploy's checklist says 300 seconds before migration day. Lower it early enough that the old, higher TTL has expired before the switch.
Will my email stop working when I change DNS?
Not if you change only the A record and the www record. Email stops when MX or SPF records are deleted or the whole zone is replaced. Export the records first and see this email-safe guide.
How can I get an SSL certificate before the domain points to the new host?
Use a DNS-based check. Let's Encrypt describes publishing a record named _acme-challenge, and Ploy's docs have you add two _acme-challenge CNAME records first, confirm the certificate is issued, then switch the A and www records. Check your own host's docs, because not every host supports this.
What are Ploy's DNS values?
As of Ploy's DNS setup page updated 10 November 2026, the A record is 207.207.209.209 and the www CNAME is proxy.runploy.com. Copy the current values, including the _acme-challenge records, from your Ploy dashboard, not from a blog.
Can I roll back if something breaks?
Yes, if the old host is still serving. Put the old A and www values back. How fast it works depends on the old TTL, so lower it early. Ploy's routing rules also have Undo and History if you moved pages by route rule.
Does Cloudflare let me lower the TTL?
On records set to DNS only, yes: between 60 seconds and one day on non-Enterprise plans. On proxied records the TTL is Auto, 300 seconds, and cannot be edited. Cloudflare's TTL page does not tell you to lower TTL before a change.
How long should I keep the old host and redirects?
Keep the old host until its traffic reaches zero, and keep redirects generally at least a year, per Google. See keeping rankings when you move a client site.
More in this topic: Websites: moving a site without losing traffic (5 guides) →