Complex migration and cutover planning
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.
- What you get
- A migration plan covering inventory, destinations, dependencies, waves, stop conditions and an implementation quote.
- How it starts
- A free scope call. The price is fixed in writing before anyone is given access.
- When it is done
- Owners agree the destination and sequence, rollback conditions are written down, and implementation is separately priced. This engagement does not execute the move.
Illustrative sample · constructed example
Price the plan against the dependency that can stop the move.
Planning excerpt · first cutover wave
Selected check
Is the source inventory complete enough to plan the first wave?
Planning excerpt · first cutover wave
| Dependency | What has to be established | Sample review |
|---|---|---|
| Source inventory | Confirm workloads, access, volumes and their owners. | Archive volume missing |
| Connected systems | Name relay, identity and domain dependencies. | Application owner missing |
| Change window | Agree sequence, stop conditions and a fallback. | Approval needed |
| Execution estimate | Price the delivery against the accepted plan and assumptions. | Estimate conditional |
This engagement produces the plan. Migration execution is separately scoped.
- Evidence
- Archive volume and application owner are not yet confirmed.
- Decision
- Keep the estimate conditional
- Next action
- Record assumptions and request the missing inputs before fixing the wave plan.
Illustrative sample. This offer delivers the plan. Executing the migration is separately scoped.
Open the complete illustrative document to inspect its fields and print a copy.
Open the sample documentWhy now
The work starts here.
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 at a glance
- Read-only planning engagement
- Several workloads, tenants or unresolved dependencies
- Named decision owner
If nobody acts
What waiting costs
Anything not counted before a fixed price is agreed sits outside what that price was built on. Each item found later goes back to the budget holder as a change to a number already signed off.
A cutover date becomes a commitment the moment staff and customers are told. A date set against estimated counts has to be re-announced by the same people if the estimate moves.
Once mail has been re-pointed and the old subscription released, reversing the move is a migration in its own right. A stop-or-continue decision taken without agreed criteria is taken at the point where the options have already narrowed.
A third-party archive is governed by its own export terms. A legal hold can be lifted only by someone with authority to lift it. Either one surfacing mid-move parks the work behind a question the project team cannot answer.
How long the old platform runs alongside the new one is set by what still depends on it. An overlap nobody has scoped is time both platforms stay licensed, supported and in the mail path.
Check your own environment
Sounds like you?
- Every estimate you have been given for the move is a wide range
- There is more than one Microsoft 365 tenant involved
- Mail runs partly in the building and partly in Microsoft 365 at the same time
- Some mailboxes are on legal hold, or there is an archive from another vendor
- Nobody can say who owns the domain, the tenant, or the licenses
Save yourself the call
Not for you if
- The source, destination, size and dependencies can all be confirmed on a short call
- You already have a plan and what you need is someone to carry it out
- The move is one mailbox or one folder
The work
What is different when we hand over
The source, destination, workloads, data volumes and ownership are verified.
Dependencies, coexistence requirements and constraints are mapped.
The route, wave plan, cutover sequence, stop criteria and validation method are agreed.
The implementation is priced and scheduled from the completed plan.
Acceptance
Checks before handover
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
A fair question
Why pay for a plan instead of just getting on with the move?
Because for this kind of move a fixed price would be a guess, and a guess protects nobody. Where the source, destination and size can be confirmed on a call, you are pointed at the move itself and not sold this. This exists for the ones where they cannot: several tenants, hybrid mail, compliance holds, or ownership nobody has settled. The implementation is quoted from the finished plan and billed separately.
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
- 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
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
- 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
What we need from you
- 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.
What you keep at handover
- A System guide: the configuration as delivered, the checks that were run and the unresolved list
- Verified source and destination inventory
- Dependency and ownership map
- Wave, cutover and rollback plan
- Validation method and fixed implementation proposal
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.
- 01How 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- 02What 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- 03What 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.
Plan the complex migrationOr write to [email protected]