Exchange 2019 to Exchange Server SE In-Place Upgrade

Yes — if the server is on Exchange 2019 CU14 or CU15. Microsoft supports the in-place upgrade from those two builds only and describes it as identical to installing a cumulative update, because Exchange SE RTM is code-equivalent to Exchange 2019 CU15 with the May 2025 hotfix. Setup runs in upgrade mode; the server keeps its name, databases, connectors, certificates and DAG membership, and what changes is the licence agreement, the version and the product key. A server on CU13 or older takes CU15 first, which we include with one extra window. Exchange 2016 has no in-place path at all.

Per server: the readiness pass with HealthChecker, the prerequisite CU15 and hotfix where needed, Exchange-aware backups and configuration exports with a written rollback position, the upgrade window itself (maintenance mode and database moves for DAG members, SE setup, product key and edition check, customisations re-applied, return to service), and a validation record covering mail flow, Outlook, Outlook on the web, EWS, ActiveSync, Autodiscover, certificates, Extended Protection, replication health and hybrid where present. Per organization: the licensing and key confirmation, the sequence and change plan, Active Directory preparation where required, organization-wide validation, the issue log, and the as-built with a next-CU run book.

$1,250 per server plus a $1,950 flat fee per Exchange organization — the tenant fee on our quote — fixed and quoted in writing before work begins; you pay after you approve delivery. A two-member DAG with one Edge Transport server is three servers: $3,750 plus $1,950, or $5,700. A four-member DAG is $6,950. Standalone and Edge Transport servers count as servers. Multi-DAG estates and several Exchange organizations are quoted per estate. Exchange SE licences, client access licences and Software Assurance are Microsoft's charges through your licensing channel, not part of this fee.

About 2 weeks for a typical single-DAG deployment: readiness and licensing in the first days, prerequisites and backups next, then the upgrade windows one server at a time, then organization-wide validation and handover. On a healthy DAG users do not notice: active databases are moved off each member before it is upgraded and back afterwards. A standalone server is unavailable to its users for the length of setup and reboot — typically an hour or two — in a window you agree. Larger member counts or more sites extend the calendar at the same per-server price, and the quote states the real dates.

You can, and for a single well-maintained server many administrators do. Where it goes wrong is the same places a cumulative update goes wrong, plus the SE specifics: setup fails late on a prerequisite nobody checked; a DAG member is upgraded with active copies still on it; the SE key is not in hand, or is a Standard key on a server with more databases than Standard allows; web.config and OWA customisations vanish because setup rewrote them; Extended Protection and a load balancer doing SSL offloading stop talking; hybrid free/busy breaks and nobody tests it until Monday. Our value is the sequence, the backups and rollback position, the validation record per server, and the documentation — the parts that turn a setup into a controlled change your auditors and your successors can read.

Microsoft has said that Exchange SE Cumulative Update 2 will only coexist with other SE servers: it will not install while Exchange 2016 or 2019 servers remain in the organization, so the side-by-side migration window closes when it ships. Microsoft's original plan put CU2 in the second half of 2026; CU1, which still allows coexistence, was delayed several times and as of Microsoft's August 2026 update had no release date, so CU2 has none either. The practical reading: the window is open now and closes on Microsoft's schedule with the lead time of a release note. We re-check this page at each review cycle, and we would rather you upgrade while the door is open than plan around a date nobody has. If the upgrade genuinely cannot start yet, Out-of-Support Exchange Server Risk Containment reduces the exposure of the 2019 servers in the meantime.

Exchange SE is licensed the way SharePoint Server SE is: a Server licence and client access licences, each under either a subscription licence or a licence with active Software Assurance. Users covered by cloud subscriptions such as Microsoft 365 E3 or E5 usually hold the CAL-equivalent rights under Microsoft's Product Terms; the Server licence is still needed. Microsoft issues Exchange SE product keys separately from Exchange 2019 keys, you retrieve them from your volume-licensing portal, and the key sets the edition — Standard or Enterprise, with different mounted-database limits — so it must match the server. We confirm all of this in the first days and do not start a window without the keys. If you need the licences quoted, Microsoft Volume Licensing is where we do that.

It adds a step, not a project. Microsoft supports the in-place upgrade only from CU14 or CU15, so a server on an older cumulative update takes CU15 first — a full cumulative-update install with its own maintenance window, which we include for that server — and then the SE upgrade. Because Exchange 2019 is out of support, the CU15 media and hotfix are the last 2019 builds Microsoft published; we confirm they are still downloadable and that their prerequisites are met before we schedule anything.

No — nobody can. Microsoft offers no in-place upgrade from Exchange 2016 to SE; the supported route is to install new Exchange SE servers into the organization, move mailboxes, public folders and connectors, and then decommission the 2016 servers, and CU2 will eventually require that the 2016 servers are gone. That is Exchange 2016 to Exchange Server SE Migration. If your destination is really Exchange Online rather than another on-premises generation, Hybrid Microsoft 365 Migration from your own Exchange Server is usually the better use of the same effort.

Not in this engagement, and not in place. Microsoft does not support upgrading the operating system underneath an installed Exchange server, so a newer Windows Server means a new server build with mailbox moves — the same shape of work as a 2016-to-SE migration. Exchange SE runs on the Windows Server versions Microsoft lists for it, which include 2019, and Windows Server 2019 is in extended support until January 2029 per Microsoft's product lifecycle, so the in-place SE upgrade on your existing hosts is a supported, in-support outcome. If you want SE on Windows Server 2025 as well, we quote that as a separate new-server project.

Exchange SE is supported for hybrid, and the in-place upgrade keeps the hybrid configuration on the server. We record the hybrid state at readiness, validate cross-premises free/busy and mail flow and run a test mailbox move in each direction after the upgrade, and re-run the current Hybrid Configuration Wizard if validation shows it is needed — that is in scope. If the server exists only to manage recipients for synchronized users, we tell you at readiness whether Microsoft's Exchange Management Tools model would let you retire it instead of licensing SE for it; that decision, and the decommissioning, are separate engagements.

One member at a time, the way Microsoft's own cumulative-update guidance describes: the member is drained on the load balancer, put into maintenance mode with Microsoft's StartDagServerMaintenance script or the equivalent manual steps, active databases are moved to other members, setup runs, the server reboots, the member is taken out of maintenance mode, every database copy is checked to Healthy with Test-ReplicationHealth, and active databases are redistributed to their preferred servers before the next member is touched. A copy that fails to catch up is re-seeded. The remaining members stay on the old build until the upgraded one is validated, which is the DAG's built-in rollback position.

The realistic failures are a setup that stops on a prerequisite or a stuck service (setup can usually be re-run once the cause is fixed, and Microsoft's SetupAssist script diagnoses most of them), a product key that is missing or the wrong edition, certificate bindings or customisations that setup reset, Extended Protection conflicts with a load balancer, and a database copy that does not catch up. Each has a known fix and is on our validation list. The rollback position is written before each window: for a DAG member, the other members are still on the old build and hold the active databases; for a standalone server, it is the verified Exchange-aware backup, because a cumulative-update-style upgrade has no uninstall. We do not open a window without both the backup and that written position.

Exchange SE stays supported only if you keep installing its cumulative updates and security updates, so you leave with a one-page run book for the next one, the as-built, and the validation results to compare against. Ongoing patching, monitoring and scheduled HealthChecker runs are Managed Exchange Server SE Administration and Patching, priced per server. Customers who buy their Microsoft licensing through IT Partner get break-fix support during business hours at no extra charge through Microsoft 365 Break/Fix Support; hourly administration by the same team is Exchange Online Administrator on Demand; and when the last server finally goes, Exchange Server Decommissioning removes it cleanly.

Not as a rule. This engagement includes its own readiness pass in the first two days — HealthChecker on every server, the licensing and key check, the DAG and hybrid state — and it is scoped for organizations that already know SE on the existing servers is the destination. The Exchange Server SE Upgrade Readiness Assessment is the right first step when that decision is still open: 2016 and 2019 servers mixed, a hybrid server whose future is undecided, hosts you would rather rebuild, or a board that wants the options and costs in writing before committing. If you have done it, its report replaces our discovery and feeds the sequence directly; the per-server price is unchanged.

Mike Mackey, IT Partner's founder, is the named owner of this service and your escalation point during the change windows. Every window is run by an engineer working from the written sequence and rollback position, with go/no-go agreed with your named approver — and where a Microsoft case is needed, escalation under our Premier Support agreement is available as a paid add-on.