Migrations
How to move a website without losing email
A website migration does not automatically require an email migration. The safest plan decides explicitly whether mail stays where it is or moves with the website and then preserves the correct DNS records.
Find the current email provider before changing DNS
Inspect the MX records and account documentation to determine where mailboxes are hosted. Do not assume the website host is also the email host.
Preserve mail-related DNS when only the website moves
If email stays with the existing provider, copy MX, SPF, DKIM, DMARC and any verification records into the destination DNS zone before changing nameservers.
Plan synchronization when mail moves too
Create the destination mailboxes, transfer historical mail where needed, and account for new messages that may arrive at either platform while DNS caches update.
Test sending and receiving after cutover
Send messages in both directions, test mobile/desktop clients, confirm website forms, and check that authentication records match the active sending systems.
Inventory mail routing before touching nameservers
Write down the current MX, SPF, DKIM, DMARC and any provider-verification records before moving the website. If mail remains with the same provider, preserve those records in the destination DNS zone.
After the web cutover, test inbound and outbound mail separately from the website. A successful homepage does not prove that mail routing survived the DNS change. Keep the old mail path available until those checks pass from more than one external provider.
Common questions
Can I keep my current email provider when I change web hosts?
Yes. Web and email can remain with different providers as long as DNS records route each service correctly.