Switching website builders does not have to touch your email, but it will by accident if you do not know which DNS records belong to the website and which belong to email. A domain points to several services at once through different DNS record types. Change the wrong one, or let a migration wizard "clean up" your DNS, and mail stops flowing while the website looks fine. This guide covers how the pieces fit together, which records to protect, and a cutover order that keeps mail running.
Which parts of my domain does a website move touch?
A domain involves four separate roles:
- Domain registrar
- where you registered the domain name and who you pay to keep it (GoDaddy, Namecheap, Squarespace Domains, and others).
- DNS host
- whoever's nameservers answer for your domain and hold its records. This is often the registrar by default, but a domain can be registered at one company and have its DNS managed somewhere else.
- Website host
- the server or platform that serves your pages, pointed to by an A record (an IP address) or a CNAME record.
- Email host
- the mail service (Google Workspace, Microsoft 365, your builder's own mailboxes, or another provider), pointed to by MX records and authenticated by a few TXT records.
Many all-in-one builders bundle all four into one dashboard, so "changing my website" feels like one action. It is really one DNS zone with several independent record sets. Moving the website requires changing only the records that point to the website. Everything else, left alone, keeps working.
Which DNS records keep email working?
Four record types matter:
- MX (Mail Exchange) tells the internet which mail server accepts email for your domain. GoDaddy's explainer says "an MX record... tells email services where to deliver emails for a specific domain" (GoDaddy). For Google Workspace, Google's current MX value is
smtp.google.comwith priority 1. Older accounts may still useaspmxrecords, which Google says keep working (Google Workspace Admin Help). - SPF (Sender Policy Framework) is a TXT record listing which servers may send mail as your domain. Your email provider publishes the exact
include:value, so copy it from their setup page rather than a generic guide. - DKIM (DomainKeys Identified Mail) is a TXT record holding a cryptographic key your mail provider uses to sign outgoing messages so receiving servers can verify they were not altered.
- DMARC (Domain-based Message Authentication) is a policy record that tells receiving servers what to do with messages that fail SPF or DKIM. Google's setup guidance says to allow 48 hours after setting up SPF and DKIM before setting up DMARC (Google Workspace Admin Help).
None of these is an A, CNAME, or website-related record. A clean website migration edits only the records that point to your pages and leaves MX, SPF, DKIM, and DMARC exactly as they were.
What order should I change things in?
- Export or screenshot your domain's full current DNS zone, every record and not just the ones you think matter. This is your rollback copy.
- Identify every MX, SPF (TXT starting
v=spf1), DKIM (TXT, usually with a._domainkeyhost), and DMARC (TXT at_dmarc) record and mark them "do not touch." - Set up the new website host and get its required A/CNAME records. If your control panel allows a staged change, do not submit them yet. Test the new site on a temporary or staging subdomain first if the platform supports it.
- Change only the website-pointing records (A/CNAME for the root and
www) to the new host, at the DNS host that actually controls your zone, which may or may not be your registrar. - Wait for DNS propagation (commonly up to 48 hours, per most registrars' guidance) before assuming a record change has failed.
- Re-check your mail records immediately after the change with any DNS lookup tool, and send a real test email in both directions.
- Cancel the old website host only after the new site is confirmed live and mail is confirmed unaffected.
What traps come with a domain or email bought through the builder?
Changing nameservers moves your whole DNS zone. Some builders ask you to point your domain's nameservers at them instead of adding a few records. When nameservers change, the old DNS host's records stop being used, mail records included. Before you switch, recreate every MX, SPF, DKIM, and DMARC record in the new DNS zone, check them with a lookup tool, and only then make the switch. If the builder offers record-level connection (pointing only A/CNAME records at it), that is the lower-risk option for email.
Squarespace plus Google Workspace. If you signed up for Google Workspace through Squarespace, Squarespace automatically tries to add Google's MX records to the domain's DNS. It warns that any other MX records already present will block your mail from sending or receiving, so they must be removed, not layered on top (Squarespace). If you later move your website off Squarespace but keep the domain and Google Workspace, make sure your migration tooling touches only the site's A/CNAME records and leaves those Google MX records alone.
Wix Mailboxes. Wix ties your email setup to how the domain connects to Wix. If the domain uses name servers, you add your provider's MX records inside the Wix DNS panel. If it is connected by "pointing," Wix says you must configure those records with your actual domain host, because Wix is not the DNS authority for a pointed domain (Wix). Know which connection method your domain uses before you start, or you may edit records in a panel that is not authoritative for your DNS.
GoDaddy email. If your site was built in GoDaddy Websites + Marketing and your email is also bought through GoDaddy, both depend on the same domain's DNS records. When you point the domain at a new website host, edit only the A/CNAME entries and leave the MX entries (the Name, Priority, Value and TTL fields GoDaddy documents) as they are (GoDaddy).
What should I check before the switch?
- Full DNS zone exported or screenshotted, dated, and saved outside the DNS panel itself.
- Every MX, SPF, DKIM, and DMARC record identified and labeled "do not touch."
- Confirmed which company hosts your DNS (not assumed from who you pay for the domain), and whether the new builder wants a nameserver change.
- New website host's required records gathered in advance.
- A test email sent and received successfully right before the cutover, as a known-good baseline.
- A named person responsible for re-checking mail records within the hour after the DNS change goes live.
What if my email breaks anyway?
Restore the exact MX, SPF, DKIM, and DMARC records from your saved pre-cutover export at whichever DNS host is authoritative for your domain. This is reversible as long as you kept that copy and know where DNS is managed. Do not guess new values from memory or a generic guide. Use the exact strings your provider issued, since a single missing character in an SPF or DKIM record fails authentication silently rather than throwing an obvious error. If you are not sure which DNS host is authoritative, run dig MX yourdomain.com or use any public DNS lookup tool from a few locations to see which servers are answering. That shows where the fix needs to happen.
If you are moving off a builder as part of this, the export capability matrix shows what each platform lets you take with you.