exchange se, Exchange 2016 vs Exchange 2019 vs Exchange Server Subscription Edition

Microsoft Exchange 2016 vs Exchange 2019 vs Exchange Server Subscription Edition

The fastest way to understand an Exchange SE project is to look at the three generations side by side.

A reminder for all of you who took the wrong path.

For all those of you who found out that compliance, laws, privacy, data protection in some country do not match Exchange Online and you are worst case getting in real trouble

focus on the words “Long-term on-premises platform”. If you want something that runs really 24/365 100% uptime and not 364 or lower then this is still the best way.

Maybe if you have too much pressure with M365 in Hybrid mode for some things if they really need it. Teams can’t see the Exchange calendar as example we did found out would be a reason to risk compliance.

DAG-cluster, F5/Kemp Load Balancer is still the way to go in 2026. Skip 50% of the compliance trouble and as before run it on-premises.

Fast, no limits, no latency, high secure and without any downtime because some datacentre is just overloaded or someone did a change and they need 48h or two weeks to rollback worldwide.

Before you start we like to mention our existing good posts regarding Exchange SE and Exchange in general.

https://www.butsch.ch/post/microsoft-exchange-server-se-subscription-edition-ab-herbst-2025/
https://www.butsch.ch/post/category/microsoft-exchange/

Exchange 2016 reached end of support on October 15, 2025. Exchange 2019 reached end of support on October 15, 2025. Microsoft now directs customers toward Exchange Server SE or Exchange Online.

Exchange 2016: the legacy starting point

If you are still running Exchange 2016, do not plan an in-place upgrade to SE.

Microsoft explicitly states that in-place upgrades to SE are supported from Exchange 2019 CU14 or CU15. Earlier versions require a legacy upgrade.

Your architecture is therefore normally:

Exchange 2016

• Build new Exchange infrastructure.
• Establish coexistence.
• Move mailboxes and resources.
• Move applications and SMTP relay.
• Validate client connectivity.
• Remove Exchange 2016.
• Continue to Exchange SE if required.
• You can also use Exchange 2019 as an intermediate platform before moving to SE.The important point is that Exchange 2016 is not your final destination anymore.Exchange 2019: the special case

  Exchange 2019 is interesting because Microsoft created a direct in-place path to SE.

  If you are on Exchange 2019 CU14 or CU15, Microsoft supports an in-place upgrade to Exchange SE.

  That means:

  Existing Exchange 2019 server

• Same VM
• Same operating system
• Same Exchange organization
• Same databases
• Same DAG
• Same namespaces
• can potentially become:Exchange SEwithout moving the mailboxes.

  This is the lowest-complexity path.

  But it is important to understand what “in-place” means.

  It upgrades Exchange.

  It does not magically upgrade:

• Your storage
• Your hypervisor
• Your Windows Server
• Your network
• Your backup
• Your monitoring
• Your SMTP relay architecture
• Your certificates
• Your load balancer
• Your Active Directory design
• Exchange SE: the new baselineExchange SE is the current on-premises Exchange platform.Microsoft describes Exchange SE RTM as code-equivalent to Exchange 2019 CU15, apart from the product name, licensing agreement and build number. New changes are introduced starting with Exchange SE CU1.

  This is an important detail for Exchange engineers.

  The transition from Exchange 2019 CU15 to SE is not equivalent to the historical jump from Exchange 2013 to Exchange 2016.

  SE is designed around the subscription/Modern Lifecycle model and continued cumulative servicing.

  The architecture also has fewer server roles.

  Exchange SE has:

• Mailbox
• Edge Transport
• Unified Messaging has been removed.Migration paths at a glance
  

  Current environment	Target	Migration method	New servers required?	Mailbox moves?
  Exchange 2019 CU14	Exchange SE	In-place	No	No
  Exchange 2019 CU15	Exchange SE	In-place	No	No
  Exchange 2019	Exchange SE + new hardware	Legacy/swing	Yes	Yes
  Exchange 2016	Exchange SE	Legacy/swing	Yes	Yes
  Exchange 2016	Exchange 2019	Legacy/swing	Yes	Yes
  Exchange 2016	Exchange 2019 then SE	Legacy + in-place	Yes	Yes
  Exchange 2013	Exchange SE	Legacy path	Yes	Yes
  Exchange 2013	Exchange 2019 then SE	Legacy + in-place	Yes	Yes
  Exchange on-premises	Exchange Online	Hybrid/cloud migration	Usually	Yes
  Exchange 2019	Exchange Online	Hybrid/cloud migration	Not necessarily	Yes

  Microsoft currently documents two fundamental upgrade methods:

• Legacy upgrade: deploy newer servers, migrate mailboxes/resources and remove the old servers.
• In-place upgrade: upgrade the existing Exchange 2019 CU14/CU15 installation directly to SE.
• Microsoft specifically identifies legacy upgrade as the method when moving from Exchange 2016 to SE or when moving to new hardware or a newer Windows Server version.Real-world server sizingThis is where Exchange articles often become too theoretical.

  Someone asks:

  “How much RAM does Exchange SE need?”

  The answer is not:

  “192 GB.”

  There is no universal 192 GB Exchange requirement.

  Microsoft’s current Exchange 2019/SE documentation recommends 128 GB RAM for a Mailbox server. It also documents support for large-memory configurations up to 256 GB.

  So I would use the following as engineering starting points, not Microsoft minimums.

  Environment	Mailboxes	Exchange servers	vCPU/server	RAM/server	Typical architecture
  Small	100 to 250	1 or 2	8 to 12	128 GB	Single server or small HA
  Medium	250 to 1,000	2	12 to 16	192 GB	DAG
  Large	1,000 to 2,500	2 to 4	16 to 24	192 to 256 GB	DAG, distributed DBs
  Very large	2,500+	4+	Workload-based	256 GB where justified	Multiple DAG members/sites

  These are practical starting points.

  They are not Microsoft’s official sizing calculator.

  Actual sizing should consider:

• Mailbox count
• Mailbox size
• Message rate
• Concurrent users
• Database count
• Database size
• Database copies
• Search workload
• Transport workload
• Storage latency
• Backup workload
• DAG replication
• Number of Exchange servers
• Example: 500-user Exchange SE environmentA realistic design could be:EX01
• 12 to 16 vCPU
• 192 GB RAM
• Exchange SE Mailbox
• 3 to 5 mailbox databases
• SSD-backed storage
• EX02
• 12 to 16 vCPU
• 192 GB RAM
• Exchange SE Mailbox
• 3 to 5 mailbox databases
• SSD-backed storage
• DAG:
• 2 members
• Database copies distributed between EX01 and EX02
• Dedicated witness configuration
• Correct DAG networking
• This is a very different architecture from:
• 1 Exchange VM
• 32 vCPU
• 512 GB RAM
• Everything on one datastore
• More hardware does not automatically equal better Exchange.Why 192 GB RAM can make senseIf you are designing a new medium-sized Exchange SE platform, 192 GB RAM is a perfectly reasonable engineering configuration.

  For example:

  16 vCPU

  192 GB RAM

  Fast SSD

  2 DAG members

  This gives you considerable headroom without jumping immediately to a 256 GB or larger configuration.

  But I would not write:

  “Exchange SE requires 192 GB.”

  That would be misleading.

  I would write:

  “Microsoft currently recommends 128 GB RAM for a Mailbox server. In real-world medium-sized production deployments, 192 GB is a practical starting configuration where workload, database size and HA requirements justify it.”

  That distinction matters.

  CPU sizing

  CPU is another area where Exchange environments are frequently overbuilt.

  A 32-vCPU Exchange server is not automatically better than a 16-vCPU server.

  For a medium deployment, I would normally investigate something around:

• 12 to 16 vCPU
• 128 to 192 GB RAM
• Fast storage
• Low storage latency
• Proper DAG design
• For larger environments:
• 16 to 24 vCPU
• 192 to 256 GB RAM
• Then validate against actual workload.The Exchange server should be sized around the workload, not around how much RAM happens to be available in VMware or Hyper-V.Database sizing example

  Imagine:

  500 mailboxes

  Average mailbox:

  8 GB

  Total mailbox data:

  Approximately 4 TB before considering additional database/log/storage requirements.

  With two database copies, the physical storage requirement is obviously much larger than 4 TB.

  You also need to account for:

• Transaction logs
• Database growth
• Content indexing
• Free space
• Backup requirements
• Recovery requirements
• Replication
• Temporary migration capacity
• This is why:”500 users x 8 GB = 4 TB”is not a storage design.

  It is only the starting data point.

  Exchange licensing architecture

  The same principle applies to licensing.

  Example:

  2 Exchange SE servers

  Each server requires the appropriate server license.

  Then you have:

• Standard CALs
• Enterprise CALs where required
• Software Assurance/subscription rights
• Existing Microsoft agreement
• DR requirements
• The Standard and Enterprise server editions also have different mounted mailbox database limits.
  

  Licensing component	Standard	Enterprise
  Server edition	Standard	Enterprise
  Mounted mailbox DBs/server	Up to 5	Up to 100
  Standard CAL	Required for applicable users	Required
  Enterprise CAL	Additional where required	Additional where required
  Typical use	Smaller DB architecture	Larger DB architecture

  Microsoft’s licensing documentation should be used for the actual licensing decision because the commercial result depends on the licensing agreement and applicable subscription/Software Assurance rights.

  The money question

  If management asks:

  “How much will Exchange SE cost?”

  do not answer with only an Exchange license price.

  Build the project from these components:

  Cost area	In-place	Swing migration	Cloud migration
  Exchange licensing	Yes	Yes	Depends
  New Exchange servers	Usually no	Usually yes	No
  Windows Server	Usually no	Usually yes	No
  Storage	Existing	Usually new	Microsoft service
  Backup	Existing	Review/rebuild	Microsoft 365 architecture
  Load balancer	Existing	Review/new	Cloud architecture
  Mailbox migration	No	Yes	Yes
  SMTP relay migration	Usually low	Yes	Yes
  Certificate work	Some	Usually yes	Different
  Namespace work	Usually low	Usually moderate	Significant
  Testing	Moderate	High	High
  Engineering time	Low	High	High
  Temporary infrastructure	No	Often yes	Usually no
  Long-term on-premises cost	Continues	Continues	Reduced

  That table is much closer to how the project should actually be budgeted.

  The biggest Exchange SE decision

  If you have:

  Exchange 2019 CU14/CU15

  and:

• Good hardware
• Supported Windows Server
• Good storage
• Healthy DAG
• Clean configuration
• Good backup
• Good monitoring
• then the in-place route can be very attractive.If you have:Exchange 2019

  but:

• Old hardware
• Old Windows Server
• Old storage
• Poor VM design
• Bad certificates
• Undocumented SMTP relay
• Weak monitoring
• then the new-server swing migration can be more appropriate.If you have:Exchange 2016

  you are already in legacy migration territory.

  If you have:

  Exchange 2013 or older

  you are looking at a modernization project rather than a simple version upgrade.

  And if Microsoft 365 is the actual destination, the entire cost calculation should be compared with a move to Exchange Online.

  The technical migration path determines the project.

  The project determines the infrastructure.

  The infrastructure determines much of the real cost.

  One final warning about the table

  Do not present the CPU/RAM numbers above as Microsoft’s official Exchange sizing requirements.

  Use them as:

  “Real-world engineering starting points.”

  Microsoft’s official requirements and sizing documentation should always win over a blog’s generic recommendation.

  For Exchange SE, the current Microsoft documentation is particularly important because the platform is moving through its ongoing CU-based servicing model. Microsoft states that Exchange SE RTM is code-equivalent to Exchange 2019 CU15 and that new changes are introduced with subsequent SE CUs.

  Microsoft documentation:

  Exchange SE upgrade paths:
  https://learn.microsoft.com/en-us/exchange/plan-and-deploy/deploy-new-installations/upgrade-to-exchange-server-se

  Exchange SE system requirements:
  https://learn.microsoft.com/en-us/exchange/plan-and-deploy/system-requirements

  Exchange SE what’s new:
  https://learn.microsoft.com/en-us/exchange/new-features/new-features

  Exchange SE discontinued features:
  https://learn.microsoft.com/en-us/exchange/new-features/discontinued-features

  Exchange 2016 lifecycle:
  https://learn.microsoft.com/en-us/lifecycle/products/exchange-server-2016

  Exchange 2019 lifecycle:
  https://learn.microsoft.com/en-us/lifecycle/products/exchange-server-2019

  Exchange licensing:
  https://www.microsoft.com/en-us/microsoft-365/exchange/microsoft-exchange-server-licensing-licensing-overview