contact@yourcompany.com hosted on the same shared plan as the WordPress site. Web migration goes wrong, someone wipes the DNS zone — no email for three days. Coupling site and mail means accepting a web incident becomes a communication crisis.
Separating from day one does not mean multiplying vendors for fun. It means treating email as a service with its own commitments, not a hosting plan bonus.
Website vs mail: two services
| Dimension | Website | Business email |
|---|---|---|
| Protocols | HTTP/S | SMTP, IMAP, POP |
| DNS | A/AAAA, CNAME | MX, SPF, DKIM, DMARC |
| Frequent outage | Site unreachable | Mail not received or sent |
| Migration | Files + database | Mailbox sync, MX cutover |
| Volume | Visitor traffic | Mailboxes, attachments |
Your site can be in maintenance for an hour. Your email should not vanish for that reason.
Recommended day-one architecture
Option A — Mail specialist (Google, Microsoft, Infomaniak Mail, etc.). Site at web host; MX points to mail provider. SME standard.
Option B — Host email separate from site. Same group but distinct products and independent MX DNS.
Option C — All-in-one shared. Acceptable for micro-structure if limits known and MX migration plan documented.
DNS to configure correctly
Set MX with priority to chosen mail server. Write SPF: v=spf1 include:... -all authorises legitimate senders. Add DKIM public key TXT. Deploy DMARC at p=none then tighten after monitoring. Frequent mistake: SPF still referencing old host after site migration.
Migration without cutting email
Inventory accounts and aliases. Lower MX TTL to 300 seconds one week ahead. Create destination accounts and start IMAP sync. Switch MX in off-peak hours. Test internal and external send/receive (Gmail, Outlook). Keep old server read-only 48–72 hours.
The climax: email is harder to fix than a site
Configure DNS with DNS without jargon and deliverability with Transactional email.
Decide and move forward without blind spots
Choose an independent mail provider or dedicated mail product from day one, before the site even goes live. Document MX, SPF, DKIM and DMARC in a file the whole team can access, with the date of last verification. Do not combine site change and MX change the same weekend: two cutovers multiply blind spots. Test sending to Gmail and Outlook before declaring migration done. Plan archiving if your sector is regulated.
Frequently asked questions
Can email and site stay with the same host?
Yes if the mail offer is reliable — mailbox limits, anti-spam, documented support. The risk remains coupling: site migration or server outage can hit both services. Separating MX to a mail specialist reduces that single point of failure.
Google Workspace or Microsoft 365 vs host email?
Workspace and Microsoft 365 offer calendar, collaboration, and stronger service commitments — at a higher monthly cost. Included host email suits very small structures if deliverability is tested and documented. Compare shared calendar and archiving needs before deciding.
Which DNS records for business email?
Point MX to your mail server, add an SPF TXT record, configure DKIM with the public key provided, then deploy DMARC progressively. Without SPF and DKIM, messages often land in spam — the full checklist is in Transactional email.
How to migrate without losing messages?
Lower MX TTL one week ahead, create destination accounts, run IMAP sync or export, switch MX in off-peak hours, then keep the old server parallel for at least 48 hours to absorb propagation delays.
A website is your shop window. Email is your contract with the world — do not lock both in the same room without a spare key.