What MAP Actually Funds
The AWS Migration Acceleration Program is AWS's structured framework for funding enterprise migrations: a three-phase methodology — Assess, Mobilize, Migrate & Modernize — paired with cash and credits that offset migration cost. The headline matters: MAP commonly offsets up to around 25% of eligible first-year AWS spend on the migrated workloads. But the framing matters more. MAP funding is earned against milestones and consumption, not granted on signature, and it is tied to your projected first-year run-rate (ARR) on the workloads you move. It is a powerful incentive, and it is also one of the credit categories AWS rarely volunteers in a commercial conversation — which is precisely why it belongs in your negotiation, as we set out in the AWS enterprise agreement negotiation guide.
The Three Funding Phases
MAP funding is released through three gates, each conditional on documented progress rather than a signed contract alone.
| Phase | Indicative funding | Released when |
|---|---|---|
| Assess | ~5% of projected ARR (cash/credits) | After AWS approves the migration readiness assessment |
| Mobilize | ~20% of projected ARR (cash/credits) | Once the landing zone is built and pre-migration tasks complete |
| Migrate & Modernize | ~15–25% of projected ARR (credits) | Once workloads are live and verified in production |
Assess-phase funding typically lands within one to two weeks of approval; the later phases pay out as the work is verified. The shape of this — early small grant, larger mid-stage funding, credits on delivery — mirrors the back-loaded ramp logic in our multi-year cloud discount structures guide, and the discipline is the same: model the funding against a realistic timeline, not the optimistic one.
How Credits Are Calculated
MAP credits follow a simple formula with sharp edges: a credit percentage set in your approved Migration Plan, multiplied by your incremental tagged spend growth — not your total bill. Credits are assessed quarterly, issued to the payer account, and arrive with roughly a one-quarter lag between consumption and credit. There is usually a minimum eligible-spend threshold, generally starting around $50,000, below which a workload may not qualify. Because the calculation rewards incremental growth on tagged resources, the value is highly sensitive to how cleanly you tag and how accurately you forecast the run-rate.
MAP funds spend growth, not your existing bill. A migration that simply lifts-and-shifts a flat workload generates far less credit than one that grows consumption on properly tagged resources — model the credit against your real spend curve before you let it shape the business case.
The Tagging Rule That Decides Everything
Tagging is the mechanism that earns the credit, and it is non-negotiable. Every migrated resource must carry the designated AWS MAP tags. Spend counts only from the day a tag is applied, and there are no retroactive credits for resources moved before tagging. The post-migration eligibility window typically runs 12 to 24 months after workloads reach production; once it closes, credits stop accruing regardless of how much tagged spend remains. A weak tagging programme is the single most common reason enterprises leave MAP money on the table — untagged or late-tagged workloads simply never accrue. Treat tagging governance as a funded workstream from day one, not an afterthought handed to the migration team.
MAP Inside the EDP Negotiation
MAP credits sit in the credit stack — the set of incentives that runs alongside the base Enterprise Discount Program discount percentage. Most enterprises negotiate only the discount percentage and overlook the credit categories, including MAP, that AWS almost never offers proactively. Treat the base discount and the credit stack as two distinct workstreams: the discount sets your effective rate on every dollar, while MAP and other credits offset specific spend. Critically, if a partner receives MAP credits on your behalf, AWS terms require them to pass the entire value through to you and disclose that they are doing so — confirm this in writing in your partner agreement. For how the discount itself is structured, compare the routes in our EDP vs Private Pricing Agreement analysis, and remember that AWS Marketplace private offers add a further 25% of commitment headroom on top.
Where Enterprises Lose MAP Money
Three failures recur. The first is poor tagging discipline — the credits depend entirely on it, yet it is routinely under-resourced. The second is letting a partner pocket value: the pass-through obligation exists, but buyers who never ask rarely see the full amount applied. The third is treating MAP as separate from the EDP — funding the migration through MAP while accepting a weak base discount, when the two should be negotiated together as part of one commercial position. A migration is the moment of maximum leverage with AWS; spend it deliberately. For an independent read on how to structure MAP funding alongside your commitment, request a confidential briefing, review the cloud contract complete guide and the AWS vendor intelligence hub, or download the AWS EDP Negotiation Playbook.