Website Launch Planning — DNS Migration & Hosting Transition

Overview

When launching a new website that replaces an existing hosted solution, coordinating the DNS migration and hosting overlap period is critical to preventing downtime. This article captures the process and decision points involved, drawn from the SBS/WI website launch.

Core Principle: Overlap Before Cutover

Never cancel the old hosting service before the new site is confirmed live. Maintain both services simultaneously through the transition window. The cost of an extra month on the old platform is negligible compared to the risk of a gap in web presence.

"I don't mind paying an extra month to Hibu. The idea is, though, that at some point, this is what ends up on the internet." — Brandon Aman (SBS/WI)

DNS Migration Checklist

Confirm hosting credentials are in hand — The developer (or technical lead) should have login access to the registrar/hosting panel (e.g., SiteGround) before launch week.
Identify 2FA requirements — If the account uses two-factor authentication, coordinate with the client in advance so they can provide the code on demand. Don't let this be a last-minute blocker.
Do not require old host shutdown to begin development — The new site can be built and staged independently. The old site stays live until DNS is pointed at the new one.
Set a target cutover date — Align with the client on a specific date. Build in buffer. Communicate that hitting earlier is a win, not a problem.

Hosting Overlap Strategy

Phase	Old Host	New Host	Action
Development	Live	Staging/dev	Build and review new site
Pre-launch	Live	Ready to deploy	Final client review
Launch day	Still live	DNS pointed over	Flip DNS, monitor
Post-launch buffer	Paid through month-end	Live	Cancel old host after confirmed stable

Client Communication Points

Tell the client early that they should budget for one overlap month on the old platform.
Clarify who initiates the old-host cancellation — typically the client, since they hold the billing relationship. Asymmetric should advise on timing but not unilaterally cancel a client's service.
Confirm the client has a contact at the old host in case issues arise during transition.

Timing Considerations

If the old hosting renews on a fixed date (e.g., the 19th of the month), plan the launch to land before that date or accept the renewal cost as the overlap fee.
A mid-month launch target gives room to absorb delays without crossing a billing cycle.
Avoid end-of-month launches if the team is also managing content reviews and approvals — the schedule compresses too quickly.

^[1]
^[2]
^[3]