How to Apply for AWS MAP Funding

Step 3: Build the Business Case

The business case is a required deliverable for MAP qualification. It quantifies the total cost of ownership comparison between your current environment and the projected AWS environment. AWS provides a Migration Portfolio Assessment (MPA) tool that standardizes this analysis.

A strong business case includes projected AWS spend, expected credit value, migration timeline, and risk factors. AWS reviews this document to confirm that the migration represents a genuine commitment and that the projected spend meets the minimum eligibility threshold, generally $50,000 or more in annual AWS consumption.

Step 4: Submit the MAP Application

Your AWS account team or consulting partner submits the formal MAP application through internal AWS channels. This submission includes the business case, portfolio assessment results, proposed migration plan, and the partner's statement of work. You do not submit the application through a public portal.

AWS reviews the application against program criteria. They verify that the migration scope, spend projections, and partner engagement meet MAP standards. This review typically takes two to four weeks, though complex engagements with multiple business units may take longer.

Step 5: Sign the MAP Agreement

Once approved, AWS issues a MAP agreement that outlines credit terms, eligible services, tagging requirements, and the eligibility window. Review this document carefully with your finance and procurement teams. The agreement specifies the credit percentage, duration, and any conditions that must be met to maintain eligibility.

After signing, you receive the cost-allocation tag that must be applied to all migration-related resources. Credits begin accruing from the agreement start date, not from when you first started migrating. This is why timing the application to align with your migration kickoff matters.

Pay close attention to the eligible service list attached to the agreement. Some organizations assume all AWS services qualify, only to discover later that specific categories are excluded. Confirming eligibility before making architectural decisions prevents budget surprises down the line.

Step 6: Begin the Migration

With the agreement in place, execute your migration plan according to the wave schedule defined during mobilization. Tag every resource from the start and conduct regular audits to ensure compliance. Your consulting partner and AWS account team will conduct periodic reviews to track progress against milestones.

Opsio supports organizations through every step of this process, from initial discovery through post-migration optimization. Our team handles the application paperwork and ensures tagging compliance so you receive the full credit value. Explore our AWS migration services for details.

Common Application Pitfalls

The most frequent issue is underestimating the time required for discovery and business case preparation. Starting the application process at least eight weeks before your planned migration date gives enough buffer for review cycles. Another common mistake is applying without a partner, which limits your access to MAP-specific tools and methodologies.

Finally, ensure your projected spend figures are realistic. AWS validates spend projections against historical patterns and industry benchmarks. Inflated numbers can delay approval or result in a renegotiated agreement. Conversely, underestimating spend means you may qualify for a smaller credit allocation than your project actually warrants, leaving money on the table.

For a broader overview of the program, read our guide on what the AWS Migration Acceleration Program covers.