AWS Migration Acceleration Programme: How MAP Actually Works for Enterprise Buyers

The AWS Migration Acceleration Programme — usually called MAP — is the single most-discussed migration incentive in cloud procurement. It is also the single most-misunderstood. AWS account teams present MAP as funded migration assistance. Buyers hear "free money for migration." Neither characterization is accurate, and the gap between the marketing positioning and the contractual reality is where enterprises consistently overspend.

MAP is a structured funding programme. AWS pays a defined percentage of partner-delivered migration work in exchange for a committed run-rate of AWS consumption over a defined period, with prescribed partner involvement and specific workload eligibility criteria. The economics of MAP can be excellent. They can also be deeply unfavourable if the commitment terms are taken at face value. This guide explains how MAP actually works, what the negotiation levers are, and where buyers leave the most value on the table.

The Three Layers of MAP

MAP is not one programme. It is a tiered family of programmes with different funding percentages, commitment levels, partner requirements, and eligibility rules. Understanding which tier applies to your workload is the first negotiation decision and it shapes every downstream economic outcome.

MAP for Small Migrations

The entry-tier programme covers small migrations — historically workloads under $250,000 in annual AWS consumption. Funding is limited and the partner involvement requirements are lighter. This tier is appropriate for departmental migrations, single-application moves, and pilot workloads. The contractual obligations are modest and the upside is correspondingly small. Most enterprise buyers can ignore this tier except as a structuring device for early pilots.

MAP for Mid-Sized Migrations

The middle tier covers workloads in the roughly $250,000 to several-million-dollar annual consumption range. Funding is more substantial, partner involvement is required, and the commitment terms are more meaningful. Most mid-market and growth-stage enterprise migrations fall in this tier. The economics work well for buyers with a defensible spend forecast and an existing partner relationship.

MAP 2.0 / Enterprise MAP

The top-tier programme is reserved for large enterprise migrations — typically multi-million-dollar annual consumption commitments. Funding is significant, partner involvement is mandatory and substantial, and the EDP integration is explicit. This tier is where most of the contractual complexity lives, and it is where buyers who negotiate well capture meaningful upside relative to buyers who accept the first offer.

How MAP Credits Are Funded

MAP credits are not cash. They are AWS service credits applied to your account, typically over a 24-36 month consumption window. The mechanics:

1. Workload assessment. An AWS-approved partner delivers a portfolio assessment and migration plan. This is often funded by a smaller pre-MAP credit pool sometimes called the Migration Readiness Assessment (MRA).
2. Migration execution. The partner delivers the migration work under a Statement of Work co-signed by AWS, the partner, and the buyer. The funding is paid to the partner directly, not to the buyer.
3. Service credits. The buyer receives AWS service credits sized to a percentage of the qualifying migrated workload's first-year consumption. Credits are applied against AWS invoices during the consumption window.
4. Commitment validation. AWS validates that the committed run-rate consumption materialised and that the migrated workloads are actually consuming the expected services.

The structure matters because it determines where the negotiation leverage lives. The partner SOW value, the service credit pool, and the commitment ramp are three separate negotiable instruments. Most buyers treat them as one and lose value on all three. See our MAP credits negotiation playbook for the structured approach.

Partner Involvement: Required, Not Optional

MAP requires partner involvement. This is not a buyer preference — it is a programme requirement. AWS does not deliver MAP-funded migrations directly. The partner choice is consequential and the partner-SOW economics are a meaningful share of the negotiation.

Partner Tiering

AWS partners are tiered: Select, Advanced, Premier. Premier Tier partners have access to deeper MAP funding pools and additional partner-funded incentives that stack with MAP. For enterprise-scale migrations, Premier Tier involvement is typically expected and the partner choice should be driven by competence, not just tier.

Partner SOW Margin

The partner is paid for the migration work. Funding from AWS offsets a percentage of that cost — not all of it. The buyer pays the partner for the work above the AWS contribution. Partner SOW margin varies widely and is negotiable. Buyers who shop the SOW between two qualified partners routinely save 15-25% on the partner cost without sacrificing programme funding.

Exclusivity Provisions

MAP funding agreements sometimes contain explicit or implicit partner exclusivity provisions for the migration scope. These can lock you into a single partner for years of work without competitive pressure. Negotiate them out where possible or carve scope to limit the exclusivity to specific workload classes.

The Commitment Math

MAP credits are paid for. The currency is committed AWS run-rate consumption. The math is straightforward: AWS funds a percentage of the migration cost up front in exchange for the buyer committing to consume a multiple of that funding amount in run-rate spend over a defined period. The multiple varies but is typically large — commonly 5-10x the funded amount across the commitment period.

This is where MAP becomes a contractual instrument rather than a marketing offer. A buyer who accepts MAP credits without modelling the run-rate commitment over the contract life can end up paying meaningfully more than the credit value through the EDP terms that lock in the commitment. The right comparison is not "MAP credits versus no credits." It is "MAP-bundled EDP versus non-MAP-bundled EDP." See our complete EDP negotiation guide for the integration mechanics.

POC and Pilot Funding: The Pre-MAP Layer

Before MAP, AWS will typically fund a proof-of-concept or pilot phase to demonstrate viability and de-risk the decision to migrate. POC credits are almost always available for workloads of meaningful size and are negotiable on amount, duration, and scope. The strategic value: POC credits buy time to build the defensible spend forecast that supports a better MAP tier negotiation later.

Buyers who skip POC funding because they "already know they're migrating" sometimes miss the opportunity to build the parallel hyperscaler quote that would materially improve the MAP and EDP terms. The POC phase is when you have the most leverage, because the destination decision is technically still open.

Workload Eligibility

Not every workload is MAP-eligible. The programme is structured to fund net-new migrations — workloads moving from on-prem, from another hyperscaler, or from a non-AWS hosting environment. Workloads that are already on AWS are typically not MAP-eligible, even if they are being restructured or modernised.

This rule has consequences. Some buyers structure migrations to maximise the share of workloads that qualify for MAP funding — for example, by sequencing waves so that on-prem-to-AWS moves happen first and AWS-internal modernisation happens later. This is legitimate optimisation and AWS account teams understand it. Buyers who do not sequence for eligibility often leave 20-40% of available MAP funding uncaptured.

The Negotiation Levers That Actually Matter

MAP is more negotiable than most buyers realise. The levers, in approximate order of impact:

1. Tier placement. Pushing for the higher tier — with the spend forecast to support it — produces the single largest economic improvement.
2. Funding percentage. The percentage of qualifying spend funded varies by tier and is negotiable within bands. Competitive hyperscaler pressure moves this materially.
3. Commitment multiple. The run-rate spend commitment that supports the funding is negotiable. Lower multiples mean less downside if forecasts slip.
4. Partner SOW economics. Shop the partner SOW. Use Premier Tier as a baseline, not a constraint.
5. Service credit window. Longer credit consumption windows reduce the risk of unused credits and provide cash-flow flexibility.
6. EDP integration. MAP credits and EDP discount tiers are economically interrelated. Negotiate them together.
7. Exit terms. What happens if the migrated workload moves off AWS during the commitment period? Default terms favour AWS strongly. Negotiate explicit reversion provisions.

Common MAP Mistakes

Patterns from 500+ engagements:

• Accepting the first tier offered. AWS account teams quote tiers conservatively. Buyers with defensible spend forecasts qualify for higher tiers than they are initially offered.
• Letting the partner negotiate MAP for you. The partner is an AWS-incentivised intermediary. Their incentives are not perfectly aligned with yours. Negotiate MAP directly with AWS.
• Treating MAP funding as free. Every dollar of MAP funding is paid for in EDP commitment terms. Buyers who do not model the all-in cost systematically overspend.
• Missing the multi-cloud lever. A documented Azure or GCP migration assessment moves MAP funding by 25-50% in many cases. Buyers who skip the parallel bid leave material money on the table.
• Signing MAP before EDP terms are locked. Sequencing matters. MAP is most valuable as part of an integrated negotiation, not as a standalone document signed before the EDP economics are settled.
• Accepting default exit terms. If you ever leave AWS, default MAP terms can claw back unconsumed credits and trigger penalties. Negotiate this explicitly.

How MAP Interacts with Other AWS Programmes

MAP does not exist in isolation. It interacts with EDP, with partner-funded programmes, with POC credits, and with hyperscaler competitive dynamics. The interactions are not always additive — sometimes accepting MAP credits forecloses a better EDP outcome, and sometimes the reverse. The right sequencing depends on the workload size, the spend trajectory, and the multi-cloud posture.

For the EDP integration, see the EDP negotiation guide. For the broader migration funding context, see the AWS migration cost planning guide pillar.

Frequently Asked Questions

The Bottom Line

MAP is a real funding programme and the economics can be excellent. They can also be quite bad if accepted at face value. The buyers who capture the most value treat MAP as one instrument among three — alongside the EDP and the partner SOW — and negotiate the integration explicitly.

The buyers who pay too much are the ones who let the AWS account team quote a tier, accept the proposed partner, sign the SOW first, and then negotiate the EDP. Sequencing the negotiation in that order systematically leaves 20-35% on the table.

If you are entering a MAP engagement of meaningful size, contact us for a structuring review before any of the three documents are signed.