Qutzl Insights

Advertisement

2 min read

When to stop self-hosting email (and when to keep it)

A straight take on leaving on-prem or cPanel mail for Microsoft 365 / Google Workspace, and the few cases where self-hosting still makes sense.

By Michael NarehoodHosting

Self-hosted email feels independent until the first deliverability spiral, the first midnight spam crisis, or the first restore that takes longer than your customers’ patience. For most small businesses, the question is not “can we run mail?” It is “should we keep paying attention to it?”

Signs it is time to leave

Move to Microsoft 365 or Google Workspace when several of these are true:

  • Nobody on staff enjoys DNS, SPF/DKIM/DMARC, and blacklist cleanup
  • Mobile devices and calendar sharing are daily friction
  • Backups of mail are unclear or untested
  • You are one hardware failure away from silence
  • Compliance or customers expect modern retention / eDiscovery features

If mail is a side quest that steals weekends from real work, outsource the side quest.

What you gain by moving

  • Better default spam and phishing filtering (not perfect; still use MFA)
  • Shared calendars and mobile sync that people already understand
  • Less “why is our invoice in spam?” archaeology
  • A clearer offboarding story when staff leave

You are trading control of the MTA for time and predictability. For most SMBs, that trade is correct.

When keeping self-hosted still makes sense

Self-hosting can stay rational if:

  • You have in-house skill and enjoy running it
  • Volume/cost math truly beats Microsoft/Google for your size
  • You have tested restores, monitoring, and outbound reputation under control
  • Legal or architectural constraints require mail to stay on systems you operate

“We have always done it this way” is not one of those reasons.

How to migrate without drama

  1. Inventory domains, aliases, and distribution lists
  2. Fix DNS intentionally (MX cutover plan, SPF/DKIM/DMARC)
  3. Sync or stage mailboxes before you flip MX
  4. Keep the old system read-only for a short overlap
  5. Update scanners, apps, and devices that still point at the old host

Do not cut MX on a Friday before a holiday. Your future self will not thank you.

Bottom line

If email is not your product, it probably should not be your hobby infrastructure. Move when deliverability and device chaos cost more than a Microsoft 365 or Google Workspace bill, and keep self-hosting only when you truly staff it like a production service.