Defined implementation
Migrate email to Microsoft 365, with every mailbox checked.
Email is moved on the agreed date, mail is arriving and sending on the new path, and every mailbox is checked against the original list.
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.
Email has to move off an old host, an old server, or another company’s system, and there is a date it has to be done by.
Scope considerations
- One coordinated owner for the switch
- Checked mailbox by mailbox before sign-off
- You own staff support on the day
The defined work
Engagement scope.
- 01
Every mailbox in scope is counted before anything moves, and each one gets a named destination.
- 02
The things the old system quietly owns are mapped, including the records that tell the internet where to deliver your mail.
- 03
The conditions that stop the move are agreed in writing beforehand, naming what would trigger a stop rather than promising to be careful.
- 04
The move runs on a dated schedule in groups, and each group is checked before the next one starts.
- 05
The new system is checked mailbox by mailbox against the old one, and every gap is closed or given an owner.
Acceptance
Completion has an agreed standard.
Every mailbox on the agreed list has arrived at its destination
Sending and receiving are tested on the new path
Every mailbox is counted back against the list you started from, and anything missing is either recovered or handed over with a named owner
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
- How many mailboxes are moving
- What system the mail is coming from, and whether both systems have to work side by side during the move
- Whether archives, shared mailboxes, public folders or legal holds are included
- Whether the switch 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
- Licenses needed to run the move
- Fixing faults in the old system before the move
- Cleaning up mail before it moves
- Help desk and staff support
Client responsibilities
- Approve the date and time of the switch
- Tell your staff what is happening and support them on the day
- Give administrator access to the old and the new system
Change and rollback method
- Mailboxes move in dated groups, and a group is not started until the one before it checks out.
- The conditions that stop the move are agreed before the first mailbox moves, and they name conditions rather than intentions.
- The records that route your mail are changed with their timers shortened in advance, so undoing it takes minutes instead of a day.
Operational record and handover
- The counted list of every mailbox that moved
- The dated schedule, as it actually ran
- The map of what the old system quietly owned
- The agreed conditions for stopping
- The check sheet proving old and new match
Before 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.
Plan the Email Move