AWS Migration Acceleration Program (MAP)
MAP is AWS's main program for funding migrations. It offsets part of the cost of assessing, planning and executing a move to AWS with credits and partner funding. It's only available through an AWS Partner: as yours, Averium prepares the plan, files it and handles the tagging that keeps credits flowing.
How MAP works
Assess
A migration readiness assessment, TCO and business case for the workloads you plan to move.
Mobilize
Landing zone, pilot migrations and a detailed migration plan. Partner funding can cover part of this phase.
Migrate & modernize
AWS credits on eligible new AWS spend from the migrated workloads, applied against your bill over the agreement.
Tagging done right
Migrated resources carry the map-migrated tag with your agreement's ID. Untagged resources earn nothing, so we tag in code from the first wave.
Credits modeled honestly
Eligible spend is measured on amortized cost and excludes data transfer, so Savings Plans shrink the base. We model credits and commitments together.
Paperwork handled
Migration plan, projected spend and agreement prepared and submitted by Averium as your AWS Partner.
AWS and Averium share the cost
MAP covers part of the migration through AWS. Averium's share comes from the savings.
AWS programs
MAP credits
Credits on eligible spend of migrated workloads, sized by AWS from the projected annual spend in the agreement.
Partner funding
Funding toward the assess and mobilize phases, paid through the Partner for qualifying migrations.
Averium
Where the work lowers your AWS bill, part of Averium's fee is recovered from those savings instead of being invoiced upfront. The split is fixed in the statement of work before anything starts.
Only an AWS Partner can request AWS funding. We prepare and submit the application; AWS makes the final award. How AWS funding works
AWS sets the benefit level for each agreement and makes the final award. We won't quote a percentage before AWS has reviewed your plan.
From first call to done
- 1
Qualify
Workloads, source environment and projected AWS spend checked.
- 2
Plan & agree
Migration plan and MAP agreement prepared and submitted.
- 3
Migrate & tag
Workloads moved in waves, every resource tagged in code.
- 4
Credits applied
Eligible spend tracked and credits reconciled on your bill.
AWS Partner. Certified engineers. Paid from results.
The team that builds it also runs the FinOps platform that keeps it cost-efficient afterwards.
- We prepare and submit the MAP plan as your AWS Partner
- Tagging enforced in infrastructure as code, so no eligible spend is missed
- Credits and Savings Plans modeled together, so you know the real net
- The same team runs FinOps after the move
Common questions
Who qualifies for MAP?+
Organizations moving workloads to AWS from on-premises or another cloud with meaningful projected AWS spend. AWS sets the thresholds and benefit levels per agreement; smaller migrations can qualify for a lighter version of the program.
What spend earns credits?+
Only resources launched after the MAP agreement is accepted and tagged correctly with map-migrated. Tagging an existing resource doesn't make it eligible, and moving resources between AWS accounts doesn't count as a migration.
Can MAP be combined with PoC funding?+
Not for the same workload. A proof of concept can come before MAP, but its funding is normally deducted from the later migration funding. A PoC on a separate workload is a different case.
How are MAP credits applied?+
As AWS promotional credits against eligible spend, under the terms of your agreement. If you're billed through Averium, the credits are passed through on your invoice.
Do Savings Plans reduce MAP credits?+
They can. Eligible spend is measured on amortized cost, so a commitment lowers the base the credits are calculated on. We model both so you can choose the better net result.