AWS MIGRATION ACCELERATION PROGRAM · THREE FUNDED STAGES
Move to AWS in funded stages. Prove the case before you commit a euro.
Migration goes wrong when the whole decision is made at the start, on a business case nobody has tested. AWS MAP splits it into three stages, funds a share of each one, and lets you stop after any of them with something worth having.
- Duration
- Assess 10 days · Mobilize ~6 weeks · Migrate per portfolio
- Format
- Three stages, each one scoped before it starts
- Price basis
- Assessment free; later stages quoted per stage
The three stages
-
Stage 1 - Assess. Free.
A portfolio assessment and a defensible TCO case: what you are running, what it would cost on AWS, what moves easily and what does not. Ten days of work, funded by AWS, free to you.
You leave with a business case you can take to a board. If the answer is do not migrate, that is a real answer and it cost you nothing.
-
Stage 2 - Mobilize.
The foundation: a governed AWS landing zone, security and networking baseline, migration tooling, the operating model, and a pilot workload moved to prove the pattern.
This is the stage that decides whether the migration is boring or painful. It is also the stage most projects skip.
-
Stage 3 - Migrate and Modernize.
The workloads move, on the pattern proven in Mobilize, with your team trained to run what lands.
Mobilize and Migrate are each scoped on the portfolio and quoted before the stage starts, and the price follows the size of the estate. The assessment gives you the number for the next stage before you commit to it.
Scope
In scope
Portfolio assessment, TCO modelling, landing zone, security baseline, migration execution, and enablement of your team.
Rehost and replatform migrations, including from VMware, Microsoft platforms and licensed databases.
Out of scope
Application rewrites. Refactoring is scoped separately, under Modernization.
Ongoing operations after the migration lands. That is Managed Services and it is usually the right next step.
What AWS funds
AWS funds a share of migration work through MAP, and the share varies by stage and by the size of the workload committed. The Assess stage is fully funded, which is why it is free. Mobilize and Migrate carry partial funding, confirmed per opportunity with AWS before anything is signed. Nobody should quote a MAP percentage from a web page, including this one.
Proof
Delivered by AWS Heroes. Recent migration work includes Azure-to-AWS moves for production estates, and TrueStay, whose AI workloads moved to Bedrock with spend down by up to 90 percent while the product scaled past 16,000 users.
FAQ
Can we stop after the assessment?
Yes, and some do. The TCO case is yours either way. An honest 'stay where you are' is a better outcome than a migration that should not have happened.
How long does a migration take?
Mobilize is typically six weeks. The migration itself depends entirely on the portfolio, and the assessment gives you a real number for yours.
What happens to our team?
They get trained on what lands, inside the engagement. A migration that leaves your team unable to run the result has not finished.
We are on VMware and the licensing just changed. Does that change the case?
It usually improves it sharply, and it is the single most common trigger right now. The assessment models your actual licensing position.
Ready to take the next step?
Migration Sprint
Tell us about your estate
Share what you need. We will get back to you to discuss the scope.