Published 2026-09-03 · Updated 2026-09-11 · 6 min read

How to migrate web hosts without downtime

A checklist for moving a small-business site to new hosting — DNS TTL, staging, SSL, email pitfalls, and a rollback plan that keeps you online.

By CloudBridge Digital Services LLC

Migrations fail when email and web are treated as one move

Hosting migrations scare owners because “the site went down” stories are loud. With a checklist, most brochure and WordPress-class moves for Overland Park businesses happen with minutes of DNS propagation — not hours of outage — if email and web DNS are handled carefully.

The usual foot-gun is changing everything at once. Web A records and mail MX records are different levers. Pull the wrong one and customers bounce while the site looks fine — or the opposite.

Inventory before you touch DNS

List the domain registrar, current host, CMS or static files, databases, SSL certificates, and every mailbox on the domain. Note whether email lives at the same host as the website (common on cheap shared hosting) — that changes the cutover plan.

Screenshot current DNS, export contacts if needed, and confirm who can change nameservers at the registrar. Access delays kill more migrations than technology does.

Stage, lower TTL, then cut over

Lower DNS TTL a day or two ahead (for example to 300 seconds) so the eventual switch propagates faster. Build and test on a staging hostname or temporary URL at the new host. Click every form, login, and key page before touching public DNS.

Sync final content (database dump, uploads, redirects). Point the A/AAAA (or CNAME) records to the new host while keeping MX records untouched if email stays put. Issue or renew SSL on the new host immediately after DNS answers correctly.

Email, SSL, and rollback

If you only change web A records and leave MX alone, mail keeps flowing. If the old host bundled mail and you are leaving that host entirely, migrate mailboxes first or in a planned window — never assume “site move” includes mail.

Keep the old host running for a few days with a documented reverse DNS change. Monitor uptime and form delivery after cutover. On Growth and Pro plans we often include straightforward migrations; complex or legacy platforms get a written quote so there are no surprises.

When to ask for help

If your site is WordPress with many plugins, uses custom PHP, or ties into booking or payment systems, a dry-run migration is cheap insurance. We run this checklist end to end for Kansas small businesses that want a no-drama move — see our hosting page for uptime, backup, and restore specifics.

Related services

Ready for numbers on your project? Book a free consultation or see public pricing.