Exchange Server 2016 and 2019 left support on October 14, 2025, and mail is still running on one of them.
Get mail off unsupported Exchange, with the cutover planned, staged, and reconciled.
Exchange Server Exit & Cutover
Mailboxes are moved to Exchange Online, or the supported Subscription Edition route is completed, with mail flow, DNS, coexistence and rollback handled and the destination reconciled against the source.
Price
Fixed price confirmed before work begins
Delivery window
2 to 6 weeks, fixed after scoping
The price is agreed in writing before any work begins and before any access is granted. Nothing is billed for the scoping conversation that sets it. What moves the number:
- · Seats and total mail volume, archives included
- · Whether a coexistence period is required
- · Public folders, compliance holds, journaling, or a third-party archive
- · The number of applications and devices relaying mail through the server
- · Whether the cutover has to run outside business hours
No tenant access, credentials, or sensitive files are requested through this website.
What happened
Support for Exchange Server 2016 and 2019 ended on October 14, 2025. Whatever extended-update coverage a business bought, the destination question is the same one and it does not get easier by waiting: move the mailboxes to Exchange Online, or move to Exchange Server Subscription Edition, the only supported on-premises Exchange going forward. Companies on Exchange 2016 should know that both roads are migration projects — there is no in-place upgrade to SE from 2016.
Sources: Microsoft: Exchange Server 2016 end of support, Microsoft: upgrade to Exchange Server Subscription Edition
Mail is still being delivered by an Exchange server whose version left support on October 14, 2025, and the printers, scanners and line-of-business applications relaying through it have no recorded owner. The mailboxes, archives, shared mailboxes, distribution groups and public folders have not been counted, so no destination has been agreed for any of them, and the DNS records the old server owns are wherever they were set years ago.
What happens if it is left as it is
- Support for the version carrying the mail ended on October 14, 2025, and coverage bought past that date extends the clock on the same server without producing the destination the mailboxes still have to reach.
- There is no in-place upgrade from Exchange 2016 to the Subscription Edition, so both destinations are migration projects, and the calendar that work needs does not shrink because the date has already gone by.
- The printers, scanners and applications relaying mail through the server stop sending the moment it goes away, and the ones missing from the dependency map get found by whoever notices their invoices stopped arriving.
- Total mail volume, archives included, is what sets the size of the move, and it keeps growing for as long as the server keeps taking delivery, so a deferred move is a larger move when it finally starts.
- Reaching either destination needs licensing the business arranges itself, so the calendar for the move carries a purchase decision and a procurement lead time on top of the technical work.
What changes in production
Not findings. These are the things that are different afterwards.
- 1Every mailbox, archive, shared mailbox, distribution group and public folder is counted, and each one gets a destination.
- 2The mail-flow path is rebuilt: connectors, the SMTP relay that printers and line-of-business applications quietly depend on, and the DNS records the old server owns.
- 3Mailboxes move in dated waves, with coexistence held where the schedule needs it.
- 4The cutover runs inside an agreed window against written rollback criteria, not a hope.
- 5The destination is reconciled item by item against the source, and the decommission sequence is executed only after that reconciliation passes.
Definition of done
The engagement ends when all of these are true and demonstrable.
- Every mailbox, shared mailbox and group in the inventory has arrived at its destination
- Mail flows on the new path and is validated, inbound and outbound, including application relay
- The reconciliation sheet shows source and destination match, with every exception closed or owned
- The decommission sequence is documented and, where in scope, executed
What you provide
Named up front, because these are the things that stall an engagement when nobody owns them.
- Approve the cutover window
- Own end-user communications and support during the move
- Provide administrative access to source and destination
- Name an owner for every application or device that relays mail through the server
What moves the price
The figure comes from what is actually in the environment. Headcount is one input among several, and rarely the one that matters most.
- Seats and total mail volume, archives included
- Whether a coexistence period is required
- Public folders, compliance holds, journaling, or a third-party archive
- The number of applications and devices relaying mail through the server
- Whether the cutover has to run outside business hours
Standard scope
Meet all of these and the move is priced directly from a scoping call. Miss one and the environment is complex, which means a fixed implementation price would be guesswork — those start with a separate planning engagement, billed separately and not credited against the move.
- Exchange 2016 or newer
- Under 1 TB of mail including archives, with no mailbox over 100 GB
- No public folders, compliance holds, journaling requirement, or third-party archive
- A single scheduled cutover with no coexistence period
- A cutover meeting all of the above is standard scope, and standard scope is what makes a fixed price possible before anyone touches the environment
Not included
Stated so the scope means the same thing to both parties on the last day as it did on the first.
- Exchange Online or Exchange Server SE licensing
- Remediation of the source environment before the move
- Data cleanup or mailbox archiving before the move
- Help desk and end-user support
- Third-party archive rehydration, which is separately scoped
How change is staged and reversed
Production work carries risk. This is the method, not a reassurance.
- Mailboxes move in dated waves; a wave is not started until the previous one reconciles.
- Rollback criteria are agreed in writing before the first mailbox moves, and name the conditions that stop the cutover rather than describing an intention.
- DNS changes are staged with reduced TTLs set in advance so a reversal takes minutes.
Evidence and handover
Yours to keep whatever happens next, including handing it to your own team or another provider. The documents are what prove the work happened; they are not the thing being bought.
- The counted inventory of everything that moved
- The dated wave and cutover schedule, as run
- The dependency map, including the DNS records and relay paths the old server owned
- The agreed rollback criteria
- The reconciliation sheet proving source and destination match
Delivered before
Exchange and mailbox migrations on the delivered record
The delivered-engagement record includes an enterprise Office 365 migration and an email migration with DKIM cutover, both completed and client-rated.
See the delivered record →Is this another report, with the real work quoted afterwards?
It may sound like a consultant will inspect the environment, hand over a document, and then quote a second project. That is not the default here. Where the outcome can be scoped safely from a short working call, the implementation is sold directly, as this page does. Separate paid planning is used only where genuine complexity prevents a responsible fixed price, and where it is used the page says so plainly.
Talk Through the Exchange Exit
Describe what is happening, what has to be working differently, and any deadline behind it. A reply comes within one business day with the most direct next step, or a clear answer that AZ Innovations is not the right fit.
Talk Through the Exchange Exit →