# Keep your domain and email when leaving WordPress

Moving your site changes one DNS record, not your domain or your inbox. Here is the difference that keeps email safe.

> Source: https://wpbuildai.com/blog/how-to-keep-my-domain-and-email-when-moving-off-wordpress/
> By lawrence-arya · 2026-06-27

---
You keep your domain and your email when you move off WordPress, because a website migration only touches the DNS records that point visitors at your site, not your domain ownership or your mail records. Your domain stays registered in your name, and your email keeps flowing as long as the MX records are left alone. WPBuildAI changes only the website-serving records at cutover and never touches your MX or domain registration, which is why email keeps working through the move. The fear here is common and almost always misplaced.

The one rule that prevents trouble: change the records that serve the website, leave the mail records alone.

## Your domain and your website are not the same thing

A domain is a name you rent from a registrar. Where that name sends different kinds of traffic is controlled by DNS records, explained well in Cloudflare's [overview of DNS](https://www.cloudflare.com/learning/dns/what-is-dns/). A migration updates the records that resolve your website (the [A or CNAME record](https://www.cloudflare.com/learning/dns/dns-records/dns-cname-record/)) so the name points at the new site. It does not transfer the domain, and it does not have to touch anything else.

That separation is why you can change your entire website and keep the same address, the same registrar, and the same inbox.

## Which DNS records change, and which stay

Only the website-serving records move. Email and verification records stay exactly as they are.

| Record | What it does | Changes in a migration? | Verdict |
| --- | --- | --- | --- |
| A / CNAME (website) | Points the domain at your site | Yes, to the new host | The only essential change |
| MX (email) | Routes your email | No, leave untouched | Keep as is |
| TXT (SPF, DKIM, verification) | Email auth and site verification | No, unless you also move email | Keep as is |
| NS (nameservers) | Where DNS is managed | Only if you change DNS host | Optional, plan carefully |

The pattern: the A or CNAME record is the one thing that must change, and the [MX record](https://www.cloudflare.com/learning/dns/dns-records/dns-mx-record/) is the one thing that must not. WPBuildAI edits the first and never the second.

## How email keeps working through the move

Email is routed by MX records, which are completely separate from the record that points to your website. As long as those MX entries are untouched, your mail provider keeps delivering exactly as before, during and after the switch. The website cutover and the mail flow simply do not intersect.

For example, a business on a workspace email provider can repoint its website to a new host in minutes and never see a single email delayed, because the change is scoped to the website record alone. The safe full sequence is covered in [how to migrate a WordPress site to Lovable](/blog/how-to-migrate-a-wordpress-site-to-lovable/).

## Where people actually get into trouble

Two mistakes cause the rare horror stories. The first is changing nameservers without copying every existing record first; moving DNS hosting replaces the whole record set, so any MX or TXT entry not carried over disappears, and email breaks. The second is editing the wrong record in a panic. Both are avoided by a simple rule: snapshot the full DNS zone before any change, edit only the website record, and confirm MX and TXT are identical afterward.

Use a low time-to-live on the website record before cutover so the switch propagates fast, then raise it again. If you are still deciding whether to move at all, [Lovable vs WordPress for small business sites](/blog/lovable-vs-wordpress-for-small-business-websites/) covers that call.

## Key takeaways: keeping your domain and email

A migration changes only the DNS record that points your domain at the website, usually an A or CNAME, and leaves your domain registration and MX records alone, so ownership and email are unaffected. Trouble only happens when nameservers are switched without copying every record across. WPBuildAI repoints the website record at cutover and never touches your mail, so your address and inbox carry on exactly as before.

## Quick answers

### Will I keep my domain and email if I move off WordPress?

Yes. A migration only updates the DNS record that points your domain at the website; it does not transfer your domain or change your email. Your registration stays in your name and your MX records keep routing mail as before. WPBuildAI changes only the website-serving record at cutover and never touches your MX or domain ownership, so your address and inbox keep working throughout the move.

### Does changing my website affect my email?

No, as long as the MX records are left alone. Email is routed by MX records, which are separate from the A or CNAME record that resolves your website. Repointing the website record has no effect on mail delivery. Email only breaks if someone switches DNS nameservers without copying the existing MX and TXT records to the new DNS host first.

### Do I need to transfer my domain to migrate?

No. You keep your domain at its current registrar. A migration just updates where the domain points by editing one DNS record. Transferring the domain to a new registrar is a separate, optional action and is not required to change your website. Keeping the domain where it is also keeps the move simpler and lower risk.

### What is the riskiest DNS mistake during a migration?

Changing nameservers without first copying every existing record. Moving DNS hosting replaces the entire record set, so any MX, SPF, DKIM, or verification entry you forget to carry over vanishes, which is what breaks email. The fix is to snapshot the full DNS zone before any change, edit only the website record, and confirm the mail records are identical afterward.