Architecture & decision engagement
Know what a complex move will cost before you commit to a date.
You receive a migration plan showing the route, connected systems, migration groups, stop conditions and completion checks. It names responsibilities and supports an implementation quote, with unresolved questions and cost assumptions recorded.
PricePrice fixed after a short scope call.
Delivery15 business days, the review window this engagement runs to.
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.
Your move has too many unknowns to price from a call. Several tenants, public folders, hybrid Exchange, legal holds, an outside archive, unusual sign-in, big volumes, or ownership nobody has settled.
Scope considerations
- Read-only planning engagement
- Several workloads, tenants or unresolved dependencies
- Named decision owner
The defined work
Engagement scope.
- 01
The source, destination, workloads, data volumes and ownership are verified.
- 02
Dependencies, coexistence requirements and constraints are mapped.
- 03
The route, wave plan, cutover sequence, stop criteria and validation method are agreed.
- 04
The implementation is priced and scheduled from the completed plan.
Acceptance
Completion has an agreed standard.
Done when the decision owner approves a plan that contains enough verified evidence to price and schedule the move.
Every item that has to move is counted and has a destination
The wave and cutover schedule is dated
Rollback criteria are agreed in writing before any move begins
The implementation carries a fixed quote
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
- Number of tenants and source platforms
- Total data volume and mailbox sizes
- Compliance holds, journaling, public folders or a third-party archive
- Whether a coexistence period is required
Scope & responsibilities
The full engagement boundary.
Review the exclusions, required client participation, change controls and operational handover for this engagement.
Exclusions
- No mailbox or file movement, DNS changes, or cutover execution
- The move is quoted from this plan as a separate fixed-fee project
- The plan fee is billed separately and is not credited against the move
Client responsibilities
- Provide read-only access to source and destination
- Confirm ownership where the plan finds it unresolved
Change and rollback method
- No production settings or data are changed during this engagement.
- Assumptions are recorded separately from verified facts and assigned for resolution.
- Implementation begins only under a separately approved scope and change plan.
Operational record and handover
- Verified source and destination inventory
- Dependency and ownership map
- Wave, cutover and rollback plan
- Validation method and fixed implementation proposal
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 Complex Migration