FOR COMPANIES ON THE WRONG CLOUD OR A DATED STACK
Migration Readiness Assessment
Before you move platforms, know what you are moving, where it should land and what could go wrong. The assessment gives you a migration plan you can act on, and a fixed fee proposal for the migration itself.
Plan the move before you make it
A migration that starts without a clear picture of what is being moved tends to find its problems halfway through: a dependency nobody mapped, data that does not reconcile, a cutover with no way back. The assessment looks for those problems first, while they are still easy to plan around.
What the assessment examines
The assessment is built from your own environment. It examines five things.
- Current state: the applications, data, integrations and infrastructure you run today, and how they depend on each other.
- Target architecture: where each workload should land, and why.
- Migration path: the order of the move, in phases, with what has to be true before each phase starts.
- Risks: what could break, what could be lost and what could stall the move, with a response for each.
- Delivery plan: who does what, in what sequence, and how the business keeps running during the move.
The assessment is yours to keep and act on, whether or not ZA delivers the migration.
Who it is for
Companies on the wrong cloud
A platform chosen years ago that no longer fits how the business runs, what it needs or what it should spend.
Companies on a dated stack
Applications and infrastructure that are hard to change, hard to support or close to the end of vendor support.
Companies with a move that keeps slipping
A migration that has been on the list for a long time because nobody can yet say what it involves, what it risks or what it should cost.
What you receive
Current state findings
The applications, data, integrations and infrastructure you run today, and how they depend on each other.
Target architecture
Where each workload should land, and why.
Migration path, in phases
The order of the move, with what has to be true before each phase starts.
Risk register
What could break, what could be lost and what could stall the move, with a response for each.
Delivery plan
Who does what, in what sequence, and how the business keeps running during the move.
A fixed fee proposal for the migration itself
A written proposal for the migration, so the next decision is made with the plan in front of you.
Every item is written for the people who will make the decision and the people who will do the work.
How the engagement runs
Scoping call
We learn what you run, where you want it to run and what is driving the move. You receive a written proposal for the assessment with a fixed fee before any work begins.
Assessment
We examine your environment with your team and document the current state, the target architecture, the migration path, the risks and the delivery plan.
Decision
You receive the findings and a fixed fee proposal for the migration. What happens next is your decision, made with the plan in front of you.
Questions, answered plainly
Is the assessment tied to a particular cloud provider?
No. The target architecture is chosen for your workloads and your business, and the assessment explains the reasons for each choice.
What does the assessment cost?
It is scoped from the first call and priced as a fixed fee in a written proposal before any work begins.
Do we have to use ZA for the migration?
No. The assessment is yours to act on with your own team or another partner. If you want ZA to deliver the migration, the assessment ends with a fixed fee proposal for it.
What do you need from us to start?
A scoping call with someone who knows the current environment. Access to documentation and systems is agreed after that, as part of the proposal.
