How to Transfer a Domain to a New Website Builder Without Downtime

Moving to a new website builder should take an afternoon. Too often it turns into three days of downtime because of one step nobody warned you about: the domain. The site is built, the pages look great, and then the domain gets double-parked, DNS records point at the wrong server, and visitors land on an error page.

Here is how to transfer a domain to a new website builder cleanly, keep your email working, and avoid the traps that take small business sites offline.

Understand what "transferring" actually means

Most of the time, you are not transferring the domain at all. You are pointing it somewhere new. There are two separate jobs, and mixing them up causes most of the pain:

• Changing nameservers — you tell the domain to use a different DNS provider (often your new builder's). Fast, reversible, no fee.
• Transferring registrars — you move ownership records from one registrar to another. Takes 5–7 days, requires an unlock code, and is rarely necessary just to launch a site.

If your only goal is to get the site live on the new builder, change nameservers. Save the registrar transfer for later, or skip it entirely.

Step 1: Build and preview before you touch DNS

Never point a live domain at a half-finished site. Publish to the builder's temporary URL first, check every page on mobile and desktop, and confirm forms and checkout work. With webceke, you describe your business in a sentence and get a complete multi-page site on a staging address, so you can review everything before the domain moves.

Only when the new site is ready should you open your domain registrar's DNS settings.

Step 2: Point DNS records the right way

Your new builder will give you either nameservers or specific records. Use whichever they recommend — do not mix the two.

If they give you nameservers, replace the existing ones at your registrar. If they give you records, edit them individually:

• A record — points the root domain (yourdomain.com) to the builder's IP address.
• CNAME record — points www to the builder's hostname.
• TXT records — used for verification and email authentication. Do not delete these.

Lower your TTL (time to live) to 300 seconds a day before you switch. That tells DNS servers to refresh quickly instead of caching the old address for 24 hours.

Step 3: Avoid the double-parking trap

Double-parking happens when two systems both think they own the domain. Common causes:

• The old builder still has the domain connected to its own DNS.
• You changed nameservers but left old A records at the registrar.
• The domain is registered through the old builder and they auto-renewed it into their own account.

Before switching, log into the old builder and disconnect the domain or delete its DNS zone. Then change nameservers at the registrar. One owner, one set of records.

Step 4: Verify HTTPS and email still work

After DNS propagates — usually 15 minutes to a few hours with a low TTL — check three things:

1. HTTPS. Visit https://yourdomain.com and confirm the padlock appears with no mixed-content warnings. If the certificate is missing, your builder may need the domain verified first. This can take up to an hour.
2. Both versions. Test yourdomain.com and www.yourdomain.com. Set a redirect so one points to the other.
3. Email. Send a test message to and from your business address. If mail breaks, you deleted the MX records. Restore them at your DNS provider — they are separate from your website records and should never be touched during a site move.

What to do if the old builder locks your domain

Some builders register the domain in their name and refuse to release it. You have options:

• Request the EPP/authorization code in writing and escalate to support.
• Check ICANN rules — registrars must allow transfers after 60 days from registration.
• If they will not cooperate, point the domain's nameservers elsewhere anyway. You keep control of DNS even if they hold the registration.

Transferring registrars is worth it only if you want full ownership and easier management long-term. Otherwise, changing nameservers solves the problem today.

The short version

Build first, lower your TTL, disconnect the old host, change nameservers once, and leave your MX records alone. Do that and your site moves without a minute of downtime.

Ready to skip the setup headaches? Describe your business in one sentence and let webceke build the site — then follow this guide to point your domain with confidence.