Defined implementation
Plan your Microsoft 365 tenant merger around the deal timeline.
The agreed users, mail and files land in the receiving tenant. Sign-in and mail work on the new path, and every user is checked across both sides.
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.
A sale, a purchase or a company split means one Microsoft 365 tenant has to move into another. The date is usually agreed before IT is asked.
Scope considerations
- Clashes found before the first user moves
- Checked user by user before sign-off
- You own staff support on both sides
The defined work
Engagement scope.
- 01
Everything in scope is counted on both sides before anything moves, and every user gets a named destination.
- 02
The clashes are found first: shared domains, duplicate accounts, and security rules that differ between the two tenants.
- 03
How much the two sides can see of each other during the move is decided and set up in advance, rather than discovered on the first morning.
- 04
The move runs in dated groups, and each group is checked before the next one starts.
- 05
The receiving tenant is checked against the source user by user, and every gap is closed or given an owner.
Acceptance
Completion has an agreed standard.
Every user on the agreed list can sign in on the receiving tenant
Mail and files for those users have arrived and are tested
Every user is counted across both tenants, and anything deliberately left behind is written down with an owner and a date
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 users are moving
- Which parts of Microsoft 365 are in scope: mail, files, Teams, devices
- Whether the two tenants have to work side by side during the move, and for how long
- Whether devices have to be re-enrolled on the receiving side
- How many domains move, and whether any are shared between the two businesses
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, on either side
- Application rebuilds or integrations on the receiving side
- HR, payroll or finance system moves
- Help desk and staff support
Client responsibilities
- Confirm the list of users, domains and data that moves
- Approve the switch window and the period the two sides run side by side
- Give administrator access to both tenants
- Tell staff on both sides what is happening and support them through it
Change and rollback method
- Users 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 user moves, and they name conditions rather than intentions.
- The domain move is scheduled as its own step, with its timers shortened in advance, because it takes sign-in and mail for everyone on it at the same moment.
Operational record and handover
- The counted list of users, mail and files that moved
- The list of clashes found and how each was settled
- The dated schedule, as it actually ran
- The agreed conditions for stopping
- The check sheet proving source and destination 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 Tenant Move