# MAP Eligibility — Partner Checklist (July 2026)

MAP terms are **AWS + Partner qualified** — treat public ARR bands as directional. Confirm with your account team / Migration Competency Partner before promising credits.

## Qualify (do not invent numbers for the customer)

- [ ] Net-new or incremental workloads to AWS (not rebadging existing spend)
- [ ] Projected post-migration AWS ARR estimated with a written TCO
- [ ] Partner path confirmed (Migration Competency often required for standard MAP)
- [ ] Timeline fits program rules (Lite pathways often shorter than multi-year enterprise MAP)

## MAP 2.0 mechanics

- [ ] Cost allocation tag for MAP activated on the payer account
- [ ] Eligible services tagged per current MAP 2.0 tagging guide
- [ ] Assess → Mobilize → Migrate & Modernize plan documented
- [ ] Dual-run (source + target) cost window modeled — credits often matter most here

## Tools commonly used in Migrate

| Workload | Tool |
| --- | --- |
| Server rehost | Application Migration Service (MGN) |
| Database | DMS (+ SCT where schema conversion needed) |
| Large offline data | Snow Family / DataSync as appropriate |
| VMware decisions | EVS vs MGN vs native — separate decision guide |

## Monday morning

1. Rough server/DB inventory + target ARR band
2. Book partner eligibility check (do not self-commit credit %)
3. Decide whether Mobilize (landing zone) is in or out of wave 1