Domains & Email / Answer

Can I move my website without moving my email?

Usually yes. Website and email are separate services that share a domain, so a new site can go live by changing only the web records while the email records stay exactly as they are.

Author
Chris Carswell
Published
Updated
Short answer

Yes, in most cases. Your website and your email are separate services that happen to share a domain name. The domain's DNS holds one set of records saying where the website lives and another saying where email is delivered. A new website goes live by changing the web records only. Leave the email records alone and email carries on exactly as before: same inboxes, same passwords, nothing to change on anyone's phone.

Why the website and email can be moved separately

When someone visits your site, their browser looks up the web records for your domain. When someone emails you, their mail server looks up the MX record to find the receiving mail server. Cloudflare's MX documentation explains that routing. Check the hostname the MX record points to as well: it may depend on an address record shared with the old hosting.

So a website move is a matter of knowing which records belong to which service:

RecordWhat it doesChange it when the website moves?
A record, and AAAA if present, for the bare domain (example.com)Points the domain at the web serverUpdate as required by the new host; check email dependencies first
CNAME, A or AAAA record for wwwPoints www at the web hostUpdate as required by the new host
MXSays which servers receive your emailNo
TXT record starting v=spf1 (SPF)Lists the servers allowed to send email as youNo, unless something new needs to send email
DKIM records (TXT or CNAME)Let receiving servers check your email was really sent by youNo
TXT record at _dmarcTells receivers what to do with email that fails those checksNo
Records such as autodiscover or mailHelp email apps find their settingsNo

The web host will tell you which values to use for the first two rows. Preserve the email records and check the dependencies before changing a shared address record.

Will my email go down while the website moves?

It should not when the email service and all its DNS dependencies remain intact. Preserve the MX records, the addresses of the mail servers they name and the email authentication records. Also check that the old hosting package is not providing the mailboxes before cancelling it.

When it is not that simple

Most moves are as described above. These are the situations where they are not, and every one of them is easy to spot in advance.

Your email is part of the old website hosting package. Many traditional hosting plans include mailboxes on the same account. Moving the website is fine, but cancelling that package would delete the mailboxes with it. Email needs a new home before the old hosting is cancelled, or the package stays.

Someone wants to change the nameservers. Some hosts ask you to point the domain's nameservers at them. That changes which provider answers DNS queries; it does not copy the records automatically. Recreate and check all records first. What happens when you change nameservers covers it. When only the website is moving, editing its web records is usually the lower-risk route.

The new site sends email itself. A contact form that sends through an email service may need adding to your SPF record. A domain can only have one SPF record, so the new service is added to the existing one rather than replacing it. Replacing it is a common way for perfectly good email to start landing in spam.

The old site was made with a site builder. Builders often bundle the website, DNS and sometimes email under one login, so it takes a little longer to see which part is which. We wrote up one of these in Replacing an IONOS Website Builder site while keeping IONOS email.

How we move a website and leave email alone

  1. Save a copy of every DNS record for the domain before touching anything: an export if the provider offers one, screenshots if not.
  2. Mark which records belong to email: MX, SPF, DKIM, DMARC and any mail-related names.
  3. Lower the TTL on the web records in advance, allowing the previous TTL to expire before the move.
  4. Update the required bare-domain and www records, including any existing AAAA records, without changing the mail service's dependencies.
  5. Check the site loads securely on both addresses, then send an email to the business from an outside address and reply to it.
  6. Keep the old hosting running for a short overlap, and only cancel it once nothing, email included, depends on it.
Related
Contact

Got a question
we haven't answered?