With end of support for Exchange Server 2019 on October 14, 2025 and the parallel release of Exchange Server Subscription Edition (SE) in July 2025, many SMBs face a question that’s been deferred for a decade: do we stay on Exchange — and if yes, in what form? Or is this the right moment to switch to Exchange Online, an open-source solution like Mailcow, or an established third-party like Kerio Connect or MDaemon? This article surveys the options and shows which ROI factors really matter — without invented dollar figures, but with honest qualitative trade-offs for three typical company sizes.
The five realistic options
Anyone replacing Exchange 2019 essentially has five paths. Each has its own logic:
| Option | License model | Maintenance effort | Target size |
|---|---|---|---|
| Exchange Online (M365) | Subscription per mailbox | Very low | 5–unlimited |
| Exchange SE 2025 on-prem | Subscription + CALs | High (AD/IIS stack on you) | 50–unlimited |
| Mailcow:dockerized | Open source, optional support | Medium (Docker, DNS, TLS) | 10–500 |
| Kerio Connect | Per-user license, commercial | Medium-low | 10–500 |
| MDaemon Email Server | Per-user license, commercial | Medium-low | 10–500 |
All three commercial third parties (Kerio, MDaemon) and Mailcow speak ActiveSync, connect Outlook in IMAP or MAPI/HTTP mode, and sync calendars/contacts via CalDAV/CardDAV or proprietary Outlook connectors. Functionally there’s no longer a sharp dividing line — the difference lies in license philosophy, compliance requirements and admin convenience.
What Exchange SE 2025 changes
Exchange Server SE has been available since July 2025 — a Subscription Edition with rolling updates rather than classic version jumps. Key points:
- License model: subscription only (analogous to M365), no perpetual license anymore
- Required: Active Directory, Windows Server 2022/2025, valid subscription
- Cumulative Updates continue; technologically SE 2025 is close to Exchange 2019 CU14
- Migration path: in-place upgrade from Exchange 2019 supported, from 2016 not directly
The subscription shift hits many SMBs harder than expected: previously Exchange was a CAPEX line item, written off after 5–7 years. SE turns it into an OPEX line item — and the question “Why even stay on-prem?” suddenly has a different answer for many SMBs.
ROI factors without invented numbers
Real ROI comparisons across the five options fail in practice because the dollar amounts vary heavily by volume discount, reseller and industry pricing. More useful is a qualitative review of the real cost drivers:
| Factor | Exchange Online | Exchange SE | Mailcow | Kerio | MDaemon |
|---|---|---|---|---|---|
| License | Per mailbox/month | Server + CAL/user | Open source / optional support | Per user/year | Per user/year |
| Hardware | – | VM or HA hardware | One VM is enough | One VM is enough | One VM is enough |
| Backup | Native or Veeam M365 | Classic server backup | Snapshot + DB dump | Snapshot + DB dump | Snapshot + DB dump |
| Spam/AV | Defender integrated | Add-on required | Rspamd + ClamAV integrated | integrated | integrated |
| Admin time | Low | High (patches, updates, AD) | Medium | Medium | Medium |
| GDPR/EU hosting | Microsoft EU Data Boundary | Full sovereignty | Full sovereignty | Full sovereignty | Full sovereignty |
| Outlook integration | Native | Native | Native via ActiveSync and IMAP | Native via Outlook connector | Native via Outlook connector |
| Mobile/ActiveSync | Native | Native | Z-Push | Native | Native |
To derive concrete numbers:
- Pull current list prices from the vendors (see sources below)
- Request volume discounts via your reseller — Microsoft CSP in particular often gives meaningful concessions
- Account for hidden costs: backup, spam, archiving, high availability, training
That last point is regularly where the “cheaper” on-prem server ends up more expensive than Exchange Online in reality — or vice versa, where the “pricier” M365 plan comes out cheaper because backup, Defender and archiving are already included.
Three scenarios
Scenario 1: 10 employees, classic trades business
Profile: small company, an external IT provider visits quarterly, no internal IT staff. Outlook on Windows desktops, a few smartphones on Exchange ActiveSync.
| Option | Rating |
|---|---|
| Exchange Online | ★★★★★ — no server upkeep, single vendor, Microsoft 365 Business Standard covers Office + mail |
| Exchange SE | ★ — effort and license cost out of proportion for 10 mailboxes |
| Mailcow | ★★★ — works, but assumes a technically engaged IT provider |
| Kerio/MDaemon | ★★ — functionally fine, rarely the economic sweet spot for 10 users |
Recommendation: Exchange Online on a Microsoft 365 Business plan. Migration as an IMAP cutover.
Scenario 2: 50 employees, consulting/law/engineering firm
Profile: half-time internal IT lead, on-prem domain controller, high compliance requirements (attorney-client privilege, professional confidentiality), reservations about US cloud.
| Option | Rating |
|---|---|
| Exchange Online | ★★★ — works, often fails on internal compliance rules |
| Exchange SE | ★★★ — functionally ideal, but OPEX rise versus the old 2019 license |
| Mailcow | ★★★★ — open source, full sovereignty, strong compliance story; SOGo as webmail+CalDAV+CardDAV |
| Kerio | ★★★★ — mature compliance features (email archive, audit) |
| MDaemon | ★★★★ — similar to Kerio, often cheaper per user |
Recommendation: seriously evaluate Mailcow or Kerio/MDaemon. If client confidentiality and M365 interest collide, consider a hybrid setup — production mailboxes on-prem, M365 workloads for Teams/SharePoint.
Scenario 3: 200 employees, mid-market industry/pharma
Profile: full IT department, Active Directory, DMS, Exchange as part of the Office 365 stack or a deliberate on-prem island.
| Option | Rating |
|---|---|
| Exchange Online | ★★★★ — the typical path, often as an E5 or frontline mix |
| Exchange SE | ★★★★ — sensible when compliance/sovereignty is mandatory and internal know-how exists |
| Mailcow | ★★ — technically feasible, rarely resource-efficient at 200 mailboxes |
| Kerio | ★★★ — possible, often a special case (government, education) |
| MDaemon | ★★★ — like Kerio |
Recommendation: clear decision between “M365 with full breadth” or “Exchange SE on-prem.” Mailcow/Kerio rarely make economic sense at this scale.
Migration: the three realistic paths
Path A: PST export → fresh build
- When: switch to Mailcow, Kerio or MDaemon with modest data volumes
- How:
New-MailboxExportRequestto PST, import via IMAP upload or vendor tool on the target - Strength: clean data, no legacy baggage
- Weakness: Outlook rules, categories and distribution lists are lost
Path B: IMAP migration
- When: switch to Mailcow or Exchange Online
- How: imapsync or Microsoft’s own IMAP migration into M365
- Strength: incremental sync possible, short cutover
- Weakness: calendars, contacts and tasks need separate handling
Path C: Coexistence
- When: move to Exchange Online with hybrid configuration or Exchange SE
- How: Hybrid Configuration Wizard, both systems run in parallel, mailboxes migrate gradually
- Strength: Free/Busy stays intact, no big bang
- Weakness: most complex path, worth the effort from roughly 50 mailboxes upward
Common pitfalls
- DNS changes: update MX, SPF, DKIM and DMARC on cutover day — otherwise mail keeps flowing to the old IP. Details in Email security: SPF, DKIM and DMARC.
- Outlook profiles: moving off Exchange sometimes requires fresh Outlook profiles — true for Mailcow and Kerio in particular.
- Smartphone profiles: ActiveSync accounts on iOS/Android don’t migrate automatically — users have to recreate the profile.
- Distribution lists and public folders: modern mail servers often map these differently (shared mailboxes, Teams channels). Plan the mapping in advance.
- Backup strategy: especially on Exchange Online, teams forget that Microsoft retention is not backup — plan for Veeam Backup for M365 or equivalent.
DATAZONE recommendation
We advise on Exchange replacements vendor-neutrally and produce qualitative assessments per customer. As rough rules of thumb:
- Under 25 mailboxes: Exchange Online is almost always the most sensible choice
- 25–150 mailboxes with data sovereignty needs: seriously evaluate Mailcow or Kerio/MDaemon
- Over 150 mailboxes: either full M365 or Exchange SE — mixed setups rarely pay off
- High compliance: Mailcow or MDaemon hosted in-house, optionally at a German provider with BSI-C5 attestation
Related articles:
- End of support for Microsoft Exchange 2019
- Email security: SPF, DKIM and DMARC
- Backup strategy for SMBs with Proxmox and TrueNAS
Sources
More articles
Mailcow: Your Own Mail Server for SMBs
Mailcow:dockerized as a self-hosted mail server for SMBs. Postfix, Dovecot, SOGo, Rspamd, ClamAV and ActiveSync in a single stack — setup on Proxmox, limits and alternatives, when Mailcow makes sense.
Proxmox vs. VMware: Migration from a Real Project
Migrating 30 VMs of an SMB customer from VMware vSphere 7 to Proxmox VE 9. Phases, tools, pitfalls and lessons from an actual project — honestly documented without glossy numbers.
Self-Hosting vs. Microsoft 365: When Running Your Own Servers Pays Off
Microsoft 365 or a self-hosted mail, file and collaboration stack? An honest comparison matrix for SMBs — when self-hosting really pays off, when M365 is the rational choice, and how hybrid setups work in practice.