GRNMRK GROUP

AWS Partner Funding Programs

AWS MAP Funding
Checklist

Everything required to qualify, apply, and get approved for Migration Acceleration Program funding — without the details that get submissions denied.

Program: Migration Acceleration Program (MAP)

Eligible: Select, Advanced & Premier Partners

Funding: Up to 25% of migration project value

AWS MAP is one of the highest-value funding programs available to AWS partners — and one of the most commonly mishandled. Submissions fail not because the project is ineligible, but because of incomplete evidence, ACE prerequisites that weren't met, or documentation that doesn't match what AWS expects.

This checklist walks through all four stages: partner eligibility, ACE opportunity setup, MAP assessment submission, and post-approval compliance. Work through it before you submit — not after you get rejected.

What's Inside

Partner eligibility prerequisites — confirm before starting
ACE opportunity setup requirements (must exist before MAP submission)
MAP assessment submission checklist with documentation requirements
Post-approval compliance steps and milestone tracking
Most common MAP denial reasons — what to check twice

Get the full checklist

Access the MAP Funding Checklist

Enter your details below and the full interactive checklist unlocks immediately — no email required after this.

✓

You're in.

Unlocking the checklist now.

Checklist Progress

0 / 22

01

Partner Eligibility

Confirm First

Active APN status at Select, Advanced, or Premier tier Required
Registered-tier partners are not eligible. Verify your tier in APN Partner Central.
At least two current AWS-certified individuals on staff Required
Certifications must be active (not expired) and tied to employees, not contractors.
At least one completed migration customer reference on file
Referenced in your APN profile. AWS may validate this during review.
Active PDM (Partner Development Manager) relationship
Having an active PDM significantly improves MAP approval rates. Establish this before applying.
No outstanding compliance flags in APN Partner Central
Open compliance issues can block MAP approval. Check Partner Central for any pending actions.

02

ACE Opportunity Setup

Must Exist Before Submitting

ACE opportunity created in Partner Central for this project Required
MAP cannot be applied retroactively. The opportunity must exist before the MAP assessment begins.
Opportunity stage set to Prospect or later — not Closed Won Required
MAP is for in-progress migrations. Completed projects do not qualify.
Estimated AWS revenue populated in the ACE record
AWS uses this to size the funding allocation. Underestimating will cap your award below eligibility.
Customer AWS account ID included in the ACE record Required
Required for MAP. If the customer has no AWS account yet, this blocks submission.
Opportunity shared with AWS (co-sell collaboration enabled)
MAP is a co-sell motion. AWS field teams must be able to see the opportunity before assessment.
Customer contact information included in the ACE record
AWS may contact the customer to validate scope during the assessment process.

03

MAP Assessment Submission

The Application

MAP tier selected: MAP Lite, MAP Standard, or MAP Advanced Required
Requirements and funding percentages differ by tier. Confirm the right tier with your PDM before applying.
Migration scope document prepared
Should cover: workloads being migrated, current environment, target AWS architecture, timeline, and expected post-migration AWS spend.
Customer commitment confirmed — signed SOW or LOI
AWS needs confirmation the project is real. A signed SOW is ideal; an LOI with project schedule is acceptable.
Discovery and planning deliverables ready Standard/Advanced
Typically: Application Portfolio Assessment, infrastructure discovery report, migration wave plan. Templates in AWS Migration Hub.
MAP-trained partner resources documented Advanced Tier
Document names, training completion dates, and role on the project for each MAP-trained team member.
Funding request amount calculated correctly
Typically up to 25% of migration project AWS spend, with a minimum threshold. Confirm the formula with your PDM.
Submission made through APN Partner Central — not via email Required
Email submissions to AWS contacts are not accepted and will not be processed.

04

Post-Approval Requirements

After MAP Is Approved

MAP agreement reviewed and countersigned Required
Funding does not activate until the MAP agreement is fully executed. Don't let this sit unsigned.
AWS service credits applied to the correct customer account
Verify credits land on the right AWS account ID. Misapplied credits require a support ticket and can take weeks to correct.
Migration milestone tracking established from day one
MAP requires milestone reporting at defined intervals. Retroactive documentation causes problems.
Project completion report submitted at migration close
Required to close the MAP engagement. Includes final workload count, AWS spend achieved, and customer sign-off.
Joint customer success story submitted to APN Recommended
Partners who submit success stories after MAP projects are consistently prioritized in future funding cycles.

Most Common MAP Denial Reasons

No ACE opportunity on file

The most common failure. Partners apply before creating the ACE record in Partner Central.

Missing customer AWS account ID

Required on the ACE record. Applications without it are returned immediately.

Vague scope documentation

AWS needs to see what is being migrated, from what, to what, and when.

Project already completed

MAP cannot be applied retroactively. The application must precede or accompany the migration.

Need help getting MAP approved?

Grnmrk Group manages MAP submissions for AWS partners. We've never had a properly-scoped MAP application denied. Let's talk about yours.

Book a Free Strategy Call Send an Email