Exchange Server exit before the October 2026 cutoff

Retire the old mail server before its updates stop, with every mailbox and printer moved first.

Mail is on a supported system before the updates stop. Every mailbox, printer and application that sends mail has a new route, tested, and the old server is retired only after the checks pass.

What you get: The agreed move to Exchange Online or Exchange Server Subscription Edition, with migration checks and a documented retirement sequence.
How it starts: A free scope call. The price is fixed in writing before anyone is given access.
When it is done: In-scope mailboxes and groups are reconciled; mail flow and application relay are tested; gaps are closed or owned. Server retirement follows the agreed dependency checks.

Price the Exchange exit Review scope & terms

Exchange Online and Exchange Server Subscription Edition are separate destination paths. We confirm the source version, supported upgrade sequence and remaining server dependencies before agreeing the work. Microsoft’s destination guidance

Illustrative sample · constructed example

Moving the mailboxes does not retire the last dependency.

Exchange Online path · application relay before server retirement

Selected check

Does the warehouse printer still depend on the server?

Exchange exit / retirement dependenciesIllustrative

Exchange Online path · application relay before server retirement

MailboxesAgreed mailbox move checked in Exchange Online.

Identity and relayDirectory authority, printers, applications and archives still need owners.

Server retirementRetirement waits for approved dependency and recovery checks.

Exchange exit / retirement dependencies: constructed inspection record
Dependency	What has to be established	Sample review
Mailboxes	Check the agreed move to Exchange Online.	Move checked
Printer relay	Verify the replacement sending route with the printer owner.	Old server still referenced
Directory authority	Confirm how identities will be managed after the change.	Separate review required
Archives and retirement	Resolve archive dependencies and approve retirement steps.	Retirement not approved

One successful relay test cannot authorize the server retirement.

Evidence: Printer configuration names the Exchange server as its mail relay.
Decision: Do not retire the server
Next action: Agree a supported replacement route with the application owner.

Illustrative Exchange Online destination. The alternative Exchange Server Subscription Edition path is scoped separately. A relay test does not prove that directory or archive dependencies are resolved.

Open the complete illustrative document to inspect its fields and print a copy.

Open the sample document

Why now

The work starts here.

Exchange Server 2016 and 2019 left support on October 14, 2025. Paid security updates run only to the end of October 2026, and your mail is still on one of them.

Scope at a glance

All-in: planning, move, testing, handover
Complex environments start with a paid plan
Client owns end-user support

If nobody acts

What waiting costs

Paid security updates for these versions run to the end of October 2026. Microsoft has published that no further coverage period follows. The date the patches stop is already set, and buying more coverage does not move it.
There is no in-place upgrade from Exchange 2016 to the Subscription Edition. Both destinations are migration projects. The time that work needs does not shrink because the deadline has already passed.
Printers, scanners and business applications relaying mail through the server stop sending the moment it goes. The ones missing from your list get found by whoever notices their invoices stopped arriving.
The size of the move is set by total mail volume, archives included. That keeps growing for as long as the server keeps taking delivery. A move put off is a bigger move when it finally starts.
Either destination needs licensing you arrange yourself. So the schedule carries a purchase decision and a procurement wait on top of the technical work.

Check your own environment

Sounds like you?

Mail still arrives through a server sitting in your building or a data centre you rent
Nobody can say when that server was last patched, or who would do it
Some applications, printers or scanners send mail through it and nobody has listed them
Old mail lives in archives or on legal hold, and nobody knows what happens to those in a move

Save yourself the call

Not for you if

Mail already runs in Exchange Online and no server is left doing mail
A provider already has a dated plan for the move and someone owns it
The only Exchange server left handles nothing but printer or scanner mail, which is a smaller job

The work

What is different when we hand over

Every mailbox, archive, shared mailbox, distribution group and public folder is counted, and each one gets a destination.
The 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.
Mailboxes move in dated waves, with coexistence held where the schedule needs it.
The cutover runs inside an agreed window against written rollback criteria, not a hope.
Everything on the list is reconciled. A legacy server is retired only where agreed, after identity authority, relay, archive, retention and recovery dependencies are approved.

Acceptance

Checks before handover

Every mailbox, shared mailbox and group in the inventory has arrived at its destination
Mail sends and receives on the new path, tested both ways, including application relay
The check sheet shows the old and new systems match, with every gap closed or given an owner
The decommission sequence is documented and, where in scope, executed

A fair question

The server still works. Why move now?

Because working and supported stopped being the same thing. Security updates for Exchange 2016 and 2019 ended, and the paid extension has its own end date. The reason to move early is not the server failing. It is that archives, legal holds and the applications quietly relaying mail through it are what make this slow, and they are much worse to untangle against a deadline than ahead of one.

Price and calendar

Scope, price and project calendar

Engagement price

Price fixed after a short scope call.

The price is agreed in writing before any work starts and before anyone is given access. The call itself costs nothing. What moves the number:

What determines the scope

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

Delivery calendar

The calendar is set once the data, the dependencies and the cutover requirements have been checked, then fixed in writing before the move begins.

How engagements work

Scope & responsibilities

What is and is not included

The exclusions, what we need from you, how change is staged and reversed, and what is handed over at the end.

Exclusions

Exchange Online or Exchange Server SE licensing
Fixing faults in the old system 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

What we need from you

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

Change and rollback method

Mailboxes move in dated groups, and a group is not started until the one before it checks out.
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.

What you keep at handover

A System guide: the configuration as delivered, the checks that were run and the unresolved list
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 check sheet proving the old and new systems match

Related work

Exchange and mailbox migrations on the delivered record

Privately reviewed contract records support prior email migration experience. They do not establish that the same Exchange retirement scope or acceptance checks were delivered.

Read it on the Results page

Access, acceptance and support arrangements

How you know the work is good

Judge it by what you can inspect.

The method is written down, the sample records open and the demo can be broken on purpose. Read it the way your technical owner would.

How a project runs: A first conversation, free. An agreed scope with a named technical lead in the proposal. The price fixed in writing before we are given access. Checks before handover.
How we work
What is checked: Release checks, access test matrices and ownership maps. Constructed inspection records on the service pages show the standard before you buy.
See sample deliverables
What you keep: A System guide: what was agreed, what changed, what was tested and what remains open. With it, the scripts and check results behind the work.

Next step

Start with a free scope call.

Tell us what needs to change, what must keep working and the deadline. The call is free, and the price is fixed in writing before anyone is given access.

Price the Exchange exit

Or write to [email protected]