A builder project, its public domain and its connected email can have different settings and owners. Plan a domain change as a coordinated release so the new website address works without disrupting unrelated services.
01 Prepare and perform the change
- Confirm the builder product, account owner and current project. Ask us whether the ordered integration supports an in-place domain change or needs a different migration process.
- Record the existing site address, important page URLs, domain registration, authoritative DNS provider and connected email service.
- Verify control of the new domain and obtain the exact connection instructions for that project. Do not copy record values from a different builder or customer.
- Review forms, payment settings, analytics, verification records and third-party callbacks for references to the old address. Prepare necessary changes before the cutover.
- Back up the site and create an old-to-new URL map. Plan redirects for important pages where the old hosting or builder supports them.
- Connect the new domain using the provider's approved sequence, then verify its certificate, published pages, forms and checkout if applicable.
- Retain the old domain and required services through the migration period. Monitor both addresses and correct missed internal links.
Common questions
Must I change nameservers?
Follow the project's actual connection method. A nameserver change replaces who manages the whole DNS zone and requires preserving email and other records, so it should not be assumed necessary.
Will the builder move my email automatically?
Do not assume it. Identify the mailbox provider and preserve its configuration separately from the website connection.
Can I release the old domain immediately?
Existing bookmarks, search results and customer correspondence may still use it. Agree a retention and redirect plan before allowing it to expire.