Cover: The Zero-Downtime Migration Runbook, Written by AI
October 14, 2026·10 min read·2,245 words·

The Zero-Downtime Migration Runbook, Written by AI

An AI web hosting migration plan is a written runbook, generated by an AI assistant, that sequences every step of moving a website from one host to another. It covers backups, DNS TTL (time to live, the setting that tells browsers how long to cache your domain's records) reduction, a content freeze, file and database transfer, cutover, and rollback. The goal is zero downtime and no lost email during the switch. Below are the exact prompts to generate each part of that runbook, and how to check the AI hasn't missed something that will break your site at 2am.

I've moved thousands of sites between hosts, and the failures are almost never technical. They're sequencing failures. Someone forgets to lower the TTL 48 hours ahead, or nobody freezes content updates during the sync window, so the old database keeps changing after the new one's already live. An AI assistant is genuinely good at catching these gaps if you ask it the right way. It's bad at knowing your specific host's quirks, so you still need to verify.

What should an AI migration plan actually include?

A complete migration plan needs eight parts, in order: an inventory of what's moving, a timeline, a TTL lowering schedule, a content freeze window, a file and database sync plan, the cutover steps, a rollback plan, and a post-cutover checklist. Miss any one of these and you'll find out the hard way.

  • Inventory first: domains, subdomains, email records (MX), SSL certificates, cron jobs and any third-party integrations
  • Timeline second: working backwards from your cutover date, accounting for DNS propagation delay
  • Rollback plan before you start, not after something breaks

Here's a single prompt that forces an AI to produce the whole runbook at once, with reasoning shown so you can spot gaps before you commit to a date.

You are helping me plan a website migration from {old_host} to {new_host}, running {cms}. My DNS is managed through {dns_provider}. Before giving me a final plan, list every risk you can think of specific to moving from {old_host} to {new_host} (email routing, SSL renewal, database size, cron jobs). Then produce a numbered runbook covering: inventory, timeline, TTL schedule, content freeze, sync plan, cutover steps, rollback plan, post-cutover checklist. Flag any step where downtime is likely.

What it gets wrong: I've seen this prompt return a plan that assumes email is hosted with the website, when in most setups MX records point somewhere else entirely (Google Workspace or a separate mail provider). The AI often skips checking this unless you tell it explicitly, and that's how businesses lose incoming email for a day mid-migration.

Verify it: cross-check the AI's DNS record assumptions against your actual records using the DNS checker before you touch anything. If your setup involves WordPress specifically, our WordPress migration guide covers plugin-based transfers this general runbook doesn't.

How do I build a migration timeline with AI?

A good timeline works backwards from cutover day and accounts for your traffic patterns, not just technical steps. Ask the AI to schedule the riskiest work outside your busiest hours.

Build me a day-by-day migration timeline for moving {cms} from {old_host} to {new_host}. My traffic peaks during {traffic_peak_hours}. Schedule all file transfers, database syncs and DNS changes outside peak hours. Show your reasoning for each date choice, including why you chose that day and time over alternatives. Then give me the final timeline as a table with dates, tasks and who's responsible.

What it gets wrong: AI tools frequently default to a same-day cutover model, ignoring that DNS propagation can take up to 48 hours to fully clear across all resolvers worldwide. It will confidently tell you the migration is "done" the moment you update the nameservers, which isn't true for every visitor.

Verify it: run your domain through the DNS propagation checker at each stage of the timeline to see how far the change has actually spread, not how far the AI assumes it has.

How do I lower DNS TTL before I move host?

Lowering your DNS TTL (the cache duration for your domain's records) days before cutover is the single most important step people skip. It's what lets the switch happen fast instead of dragging on for days.

I'm migrating {cms} from {old_host} to {new_host} using {dns_provider} for DNS. My current TTL is unknown. Walk me through checking my current TTL value, then create a schedule for lowering it in stages ahead of cutover (explain why staged lowering matters versus a single change). Tell me what TTL value to set and how many hours before cutover I need to make this change for it to take effect reliably.

What it gets wrong: some AI answers give a generic "lower it to 300 seconds" instruction without checking whether your DNS provider even supports low TTLs on all record types, or without mentioning that some resolvers ignore TTL settings and cache longer regardless.

Verify it: use the DNS propagation checker to confirm your new TTL value is actually being honoured by major public resolvers before you schedule cutover around it.

How do I write a content freeze window and database sync plan?

A content freeze stops anyone editing the live site during the final sync, so the old and new databases don't drift apart. Skipping this is the number one cause of "lost" orders or comments after migration.

Write a content freeze policy for migrating {cms} from {old_host} to {new_host}. Explain what "freeze" means in practice (no new posts, orders, comments, or plugin updates) and who needs to enforce it. Include a fallback plan for what happens if someone edits content during the freeze anyway. State exactly when the freeze starts and ends relative to the DNS cutover time.
Create a database sync plan for {cms} moving from {old_host} to {new_host}. Assume the database is actively being written to until freeze time. Show your reasoning for choosing a full export versus incremental sync, then give me the exact commands or tools to use, plus how to verify the new database matches the old one row for row before I switch DNS.

What it gets wrong: AI models routinely suggest a single database export as "sufficient" without accounting for orders, form submissions or comments that arrive between the export and the actual DNS cutover, which can be hours apart.

Verify it: keep a manual backup of the old database using the practices in our backup glossary entry, and reconcile row counts between old and new before you announce the migration complete.

What should my rollback plan look like?

A rollback plan is your insurance policy: the exact steps to revert to {old_host} if something breaks after cutover. Write it before the migration, not while you're panicking.

Write a rollback plan for a failed migration from {old_host} to {new_host} running {cms}. Assume DNS has already been switched and something is broken (site down, database errors, or missing content). List the decision criteria for when to roll back versus fix forward. Then give exact steps to revert DNS, restore the old database, and communicate the rollback to users, ranked by urgency.

What it gets wrong: AI-generated rollback plans often assume the old host account is still active and untouched, when in reality many people cancel {old_host} the moment the new site goes live, closing off the rollback path entirely.

Verify it: don't cancel your {old_host} account until the DNS propagation checker shows full global propagation and the site has run cleanly for at least a few days on {new_host}.

How do I write the post-cutover checklist?

The post-cutover checklist is what you run through in the hours after DNS switches, to catch problems before customers do. It should cover SSL, email, forms, and search visibility.

Create a post-cutover checklist for a website that just migrated from {old_host} to {new_host}, running {cms}. Cover SSL certificate validity, email deliverability, contact form submissions, site speed, search engine indexing, and any {cms}-specific settings that commonly break (permalinks, base URLs, cached pages). For each item, explain how to test it and what a failure looks like.

What it gets wrong: AI checklists frequently forget SSL certificate reissuing entirely, assuming certificates transfer automatically between hosts. They usually don't, and a lapsed certificate throws a browser warning that scares visitors away instantly.

Verify it: confirm your SSL status and DNS records together using the DNS checker, and read Let's Encrypt's documentation if you're issuing a fresh certificate on the new host.

How do I tell my team and clients about the migration?

A stakeholder email needs to say what's happening, when, and what (if anything) the reader needs to do. Most migration emails fail because they bury the actual downtime window in technical jargon.

Write a stakeholder email announcing a website migration from {old_host} to {new_host}. The audience is non-technical. State clearly: what's changing, the expected downtime window (if any), what action they need to take (none, ideally), and who to contact if something looks wrong afterward. Keep it under 150 words and avoid technical terms like DNS or TTL unless you explain them in plain language.

What it gets wrong: AI drafts often lead with technical detail ("we're updating our nameservers") instead of the one thing readers actually want to know, which is whether the site will be down and for how long.

Verify it: read the draft aloud before sending, and check it against your actual timeline from the propagation checker so you're not promising a downtime window you can't guarantee.

If you're choosing a new host to migrate to in the first place, don't skip that step. Compare candidates on the HostList directory, ranked by an independent score rather than affiliate payouts, and read our general guide on changing web hosts without downtime alongside this runbook approach.

TemplateWhat you paste inWhat you get backVerify with
Full runbookOld host, new host, CMS, DNS providerComplete numbered migration plan with risks flaggedDNS checker
Timeline builderPeak traffic hours, CMS, hostsDay-by-day schedule as a tableDNS propagation checker
TTL scheduleDNS provider, current TTLStaged TTL lowering plan with timingDNS propagation checker
Content freeze policyCMS, hosts, cutover timeFreeze rules and fallback planBackup glossary
Database sync planCMS, hostsExport/sync method with verification stepsManual row count check
Rollback planCMS, hosts, failure scenarioDecision criteria and revert stepsDNS propagation checker
Post-cutover checklistCMS, hostsTest list for SSL, email, forms, indexingDNS checker plus Let's Encrypt docs
Stakeholder emailHosts, audience typePlain-language announcement draftManual read-through against timeline

Search engines need to see the migration go smoothly too, so keep your sitemap and robots.txt untouched during the freeze window, and check Google's Search Central documentation on site moves if you're also changing your domain name, not just your host. Changing host alone, with the same domain, is far lower risk for rankings than a domain change.

One thing AI tools consistently underestimate is how long a CDN (content delivery network, a system that caches your site closer to visitors) can hold on to old content after cutover. If you use Cloudflare or a similar service in front of your site, purge its cache manually after DNS switches. Read Cloudflare's learning centre for how their caching interacts with DNS changes specifically.

None of these prompts replace judgement. They replace the blank page and the nagging feeling you've forgotten something. Treat every AI-generated runbook as a first draft that needs checking against your actual DNS records, not a document you paste into a project management tool unread.

Frequently Asked Questions

Can AI actually execute the migration, or just plan it?

AI can write the plan, the commands, and the checklists, but it can't log into your hosting panel or run the transfer itself. You or your host's migration team still execute each step. Treat the AI output as a script to follow, not an automated agent.

How long before cutover should I lower my DNS TTL?

Most guidance suggests 24 to 48 hours before cutover, though some resolvers cache longer regardless of your setting. Check your current TTL first using the DNS checker, then lower it and wait before scheduling anything final.

What's the biggest cause of downtime during a host switch?

Cutting over before DNS has propagated globally, combined with cancelling the old host too early to allow a rollback. Both are sequencing mistakes, not technical failures, and both are preventable with a written runbook checked against a propagation tool.

Does migrating hosts hurt my search rankings?

Moving to a new host with the same domain name generally has minimal ranking impact if there's no extended downtime. Changing your domain at the same time is a different, higher-risk process; see Google's Search Central documentation on site moves for that scenario.

Should I trust an AI-generated rollback plan without testing it?

No. Test the rollback path on a staging copy of your site before you need it for real, if you have time. At minimum, confirm your old host account and backup are both untouched until the new site has run cleanly for several days.

The bottom line

An AI-generated runbook won't move your site for you, but it will catch sequencing mistakes that cause most migration downtime, provided you check its DNS and email assumptions against real data. Run every plan through the propagation checker before committing to a cutover date, and keep your old host active until you're certain the new one's solid.

HostList on LinkedIn
More independent hosting data

Follow HostList for new rankings, original research, and changes across the hosting industry.

Gautam Khorana
Gautam Khorana
Founder, HostList.io

Over 10,000 websites launched. Years managing thousands of client sites. Built HostList because the world deserves honest hosting advice.

LinkedIn →

MENTIONED HOSTS

RELATED ARTICLES

RadixSponsorPremium names that work like prime real estate400,000+ short, memorable premium domains across .tech, .store, .online, .site and more. 20,000+ already sold.See Radix premiums
.tech domains from RadixSponsor.tech: the address for what you buildPremium .tech names like cloud.tech and micro.tech, from Radix. Short, dictionary-word domains for tech brands.See premium .tech
.host domains from RadixSponsor.host: a domain that says what you doPremium .host names for hosting companies and infrastructure brands, from the Radix registry.See premium .host
GreenGeeksSponsorEco-Friendly WordPress Hosting DealFast WordPress performance backed by expert 24/7 support, free migration, daily backups and built-in security.See GreenGeeks
HostPapaSponsorFast, Reliable, & Affordable Web HostingLaunch, grow and manage your website with reliable hosting, easy tools and 24/7 PapaSquad support.See HostPapa

Promoted placement. Does not affect HRI, ranking order or eligibility.