Defined implementation
Run email on Microsoft 365 instead of a server that stopped getting updates.
Mail moves to Exchange Online, or onto the supported Subscription Edition route. Mail flow, DNS and the way back are all handled, and every mailbox is checked against the list you started from.
PricePrice fixed after a short scope call.
DeliveryThe calendar is set once the data, the dependencies and the cutover requirements have been checked, then fixed in writing before the move begins.
What you receive · illustrative sample
A move is complete when the checks agree.
Illustrative excerpt from a migration acceptance record. The actual checks follow the workloads in your scope.
| Check | Evidence | Recorded result |
|---|---|---|
| Mailbox reconciliation | Source/destination totals and exceptions | Sample: checked |
| Mail flow and sign-in | Agreed user and shared-mailbox tests | Sample: passed |
| Remaining exception | Archive item assigned to client owner | Sample: accepted exception |
Related delivery record
SharePoint migration troubleshooting and reconciliation
Read what changed and how it was checked ↗Engagement context
When this engagement applies.
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.
Related source documentation
Microsoft: Exchange Server 2016 end of support Microsoft: upgrade to Exchange Server Subscription EditionScope considerations
- All-in: planning, move, testing, handover
- Complex environments start with a paid plan
- Client owns end-user support
The defined work
Engagement scope.
- 01
Every mailbox, archive, shared mailbox, distribution group and public folder is counted, and each one gets a destination.
- 02
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.
- 03
Mailboxes move in dated waves, with coexistence held where the schedule needs it.
- 04
The cutover runs inside an agreed window against written rollback criteria, not a hope.
- 05
Everything on the list is checked item by item against the old system, and the old server is only switched off once that check passes.
Acceptance
Completion has an agreed standard.
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
Commercial basis
Price, scope and timing are considered together.
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 workScope & responsibilities
The full engagement boundary.
Review the exclusions, required client participation, change controls and operational handover for this engagement.
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
Client responsibilities
- 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.
Operational record and handover
- 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 delivered work
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.
Read selected workBefore you commit
A clear first step.
You stay in control.
Start with the problem and the result you need. The initial fit conversation is free and does not require access to your systems.
Check client feedback on Upwork ↗Prefer to contract through Upwork? Contact Alwatheq there. Existing Upwork engagements continue through Upwork.
Who will actually do the work?
Alwatheq Zboun leads the scope, technical work and handover. If a specialist collaborator is needed, their role is agreed with you before work starts. Your proposal names the responsibilities and delivery windows.
What happens before you get access?
We agree the scope, fee and completion checks in writing. Access uses named accounts and only the permissions the work requires. Approved access is reviewed and removed at handover.
How do we know the change worked?
Your scope defines the pilot, test cases and acceptance checks. Results and exceptions are recorded. Recovery options and their limits are agreed before production changes; a failed check is addressed before the next approved stage.
Will we need an ongoing retainer?
A defined project can end at handover. Your team receives the agreed configuration records, runbook and walkthrough. Any limited support period is written into the proposal; ongoing support or additional work is a separate agreement.
Discuss this engagement
Put the scope in context.
Describe the problem, systems and deadline. Alwatheq will review the fit and the scope questions before preparing a written proposal.
Get the Exit Priced in Writing