Migration planning
A migration design your team can actually follow — architecture choices, sequenced steps and a rollback path, written down before anything moves.
What you receive
Pure consultancy: the engagement ends with documents your team can actually use — implementation is always quoted separately.
Target architecture
What your environment should look like after the move, platform by platform, with the reasoning written out.
Migration sequence
Which systems move first, which move together, and what has to be true before each step starts.
Rollback plan
For every stage: where we pause, what we keep, and how your team returns to a working setup if a step fails.
Scope, stated plainly
These boundaries are fixed for every client. If a piece of work falls outside them, you get a separate quote — not a surprise invoice.
Included
- Architecture workshop with your team
- Written target architecture
- Sequenced migration plan
- Rollback plan for every stage
- Cut-over runbook for the go-live window
Not included
- The migration work itself (quoted per consultant-day)
- Software licences (billed by vendors at cost)
- A guarantee of zero downtime — we design for it, then we test it
A fixed price for the design stage
The design stage is a fixed-price engagement, agreed in writing before we start. Implementation, if you proceed, is quoted per consultant-day with a cap you approve in advance.
Request a quoteMoving something soon?
Tell us what runs where today, and we will scope the design stage — including what it should NOT include.