A website move does not have to be an email move
Your domain name can connect to several different services. The website might be hosted by one company while business email is handled by another. Moving website files therefore should not automatically mean changing where mail is delivered.
The risk appears when someone replaces nameservers or a whole DNS zone and copies only the website records. The homepage comes online, but the email records that previously worked are missing. Treat the website and email as two separate migration checklists.
Capture the current DNS configuration
Before making changes, export the existing zone or record each entry accurately. Keep the hostname, type, value, priority and TTL. Include mail routing, authentication, verification and any service subdomains; do not copy passwords into this record.
Cloudflare’s email-record documentation explains the role of MX records in mail delivery and TXT records for email authentication. Use the exact values supplied by your own email provider. An example record in a tutorial is not a replacement for your account’s settings.
- Website: identify the current A, AAAA or CNAME records.
- Inbound email: record MX destinations and priorities.
- Outbound email: preserve the provider’s SPF, DKIM and DMARC configuration.
- Other services: include verification records and relevant subdomains.
Make the smallest change that achieves the move
If the DNS provider is staying the same, a website move may only require changing the web records. If nameservers are changing, populate and review the new zone first. Do not remove the old hosting or DNS configuration before there is a tested rollback path.
For a store or frequently edited website, also plan how to handle content created during the move. Decide whether you need a short editing pause, a final database copy or another controlled synchronisation process. Copying files alone does not reconcile new orders.
Test the website and email independently
Check HTTPS, key pages, forms and downloads on the new website. Then send a message from an external mailbox to the business address and reply from the business address. Verify actual receipt in both directions, including spam folders; a successful website form screen is not proof of email delivery.
Keep a simple test log: time, sender, recipient, result and any error. Check aliases and important automated senders as well as the main mailbox. DNS caches can retain earlier answers, so do not assume one successful check means every visitor has switched.
Before agreeing a hosting migration, specify who owns DNS changes, mailbox migration if any, testing and rollback. This avoids discovering during launch that email was outside the agreed scope.