CLOUD MIGRATION
How your move to AWS runs, phase by phase
Every migration we run follows the AWS Migration Acceleration Program (MAP): assess, mobilize, then migrate and modernize in waves, into a new AWS Organization built on Leverage, our open-source reference architecture. For eligible migrations, AWS funds part or all of our work.
Three phases, one program
The four steps on our cloud migration page fit inside these three phases.
Assess
- Discovery
- TCO model
- Readiness assessment
- Business case
Build the case for change
Mobilize
- Wave plan
- Landing zone
- Security and compliance
- Operating model
- Team skills
- First apps in production
Get ready by doing
Migrate & Modernize
- Migrate in waves
- Operate and optimize
- Modernize where it pays off
Move the rest at scale
01 · Assess
Build the case for change
We measure what you run, what it costs and how ready your team is, so the decision to migrate rests on evidence.
Discovery
- Servers, databases and applications, by real usage and dependencies
Readiness
- A readiness assessment and the plan to close its gaps
Economics
- A total cost of ownership model and the business case
Your team
- Briefings and hands-on workshops
02 · Mobilize
Get ready by doing
We build the foundation the migration runs on, and prove it by moving your first applications to production.
Portfolio
- A strategy for each application, and a wave plan
Platform
- A new AWS Organization with a multi-account landing zone, built on Leverage
- Security, networking, CI/CD, compliance and an operating model
People
- Skills and runbooks for your team
First migrations
- Your first applications in production
03 · Migrate & Modernize
Move the rest at scale
The rest moves in waves, each workload with the strategy that fits it, while the platform gets cheaper to run.
Migrate
- Waves planned around your business
- Rehost, replatform or refactor, each with a rollback path
Operate and optimize
- Rightsizing, cost optimization, backups and security operations
Modernize
- Containers, serverless and managed databases where they pay off
Where the money comes from
AWS credits in your new accounts
Qualifying migrated workloads earn AWS credits, sized by AWS on the new spend.
Services AWS helps fund
For eligible migrations, AWS funds part or all of our work, through MAP or its partner funding for new workloads.
We handle the paperwork
The business case and plan AWS reviews, the opportunity registration, and the tags that make your spend count.
Eligibility, amounts and timing are set by AWS program terms. We confirm them with your AWS account team before work starts.
Questions we hear
We are a small team. Is MAP for us?
The method fits any size. A short assessment tells you the scope and which funding applies.
Do we need new AWS accounts?
For a migration from another provider, yes: a new AWS Organization keeps workloads tagged from the start, and the credits land there.
LLM inference alone can run in the AWS account you already have.
What does it cost us?
It depends on eligibility. You see the numbers in the business case before you commit.
Can we keep running while we migrate?
Yes. Workloads move in waves, each with a rollback path.
Where can we migrate from?
Another cloud, a data center, VMware or a hosting provider. LLM inference has its own page.
Ready to plan your migration?
Tell us what you run today, and we will tell you how the move and its funding would work.