AWS Migration Acceleration Program (MAP) funding helps organizations offset the cost of migrating to AWS through service credits, professional services discounts, and training allowances. This guide covers eligibility requirements, funding tiers, tagging setup, and the application process.
Understanding AWS MAP Funding
MAP funding is a financial incentive program designed to reduce the upfront investment required for cloud migration. Unlike a grant or loan, MAP funding takes the form of AWS service credits applied to your account after migrated workloads are tagged and verified. The program recognizes that dual-running costs (maintaining both on-premises and cloud infrastructure during transition) are a significant barrier to migration.
MAP funding is available exclusively through AWS Partners with the Migration Competency designation. Your partner submits the MAP enrollment on your behalf and manages the credit allocation process throughout the engagement.
MAP Funding Tiers
Funding levels scale with migration scope — larger migrations receive proportionally more credits and additional support services.
| Funding Component | What It Covers | How It Is Allocated |
|---|
| Assessment funding | Discovery tools, readiness assessment | Fixed amount per engagement |
| Mobilization funding | Landing zone, training, pilot migrations | Based on migration scope |
| Migration credits | Dual-running costs, compute and storage | Proportional to tagged workloads |
| Professional services | AWS PS engagement fees | Up to 25% discount |
| Training allowance | AWS certification and training | Per-person allocation |
Step-by-Step Application Process
Applying for MAP funding involves three main steps coordinated between your organization and your AWS Partner.
- Engage a qualified partner: Select an AWS Partner with active Migration Competency. Opsio holds this designation and manages the full MAP enrollment process.
- Complete the assessment: Work with your partner to run a portfolio discovery and readiness assessment. This produces the business case required for MAP enrollment.
- Submit the MAP enrollment: Your partner submits the enrollment through the AWS Partner portal, including migration scope, timeline, and expected credit requirements.
- Receive approval and begin: AWS reviews the enrollment and approves funding allocations. Credits become available as tagged workloads are verified.
MAP 2.0 Tagging Requirements
Under MAP 2.0, all funding is tied to workload tagging — resources without correct tags will not generate credits. The tagging framework requires:
- Activating the MAP tag key in your AWS Billing console
- Applying specific tag values to every migrated resource (EC2, RDS, S3, etc.)
- Maintaining tag compliance throughout the credit eligibility period
- Using AWS Tag Editor and Config rules for automated validation
Common tagging mistakes include applying tags only to primary resources (missing associated EBS volumes, snapshots, or network interfaces), using incorrect tag values, and failing to tag resources created after the initial migration. See the MAP 2.0 Tagging Guide for technical details.
Strategic Fund Allocation
Maximizing MAP funding value requires strategic planning about which workloads to migrate first and how to allocate credits. Key strategies include:
- Prioritize expensive workloads: Migrate high-compute, high-storage workloads first to maximize credit offset against the largest AWS bills
- Invest in automation: Use mobilization funding to build infrastructure-as-code templates that accelerate subsequent migration waves
- Plan for dual-running costs: Budget for 3-6 months of overlapping infrastructure costs during the transition, using migration credits to offset
- Leverage training allowances: Upskill internal teams during the mobilization phase so they can manage migrated workloads independently
- Coordinate with reserved pricing: Time the transition from MAP credits to Reserved Instances or Savings Plans to avoid cost spikes
For detailed migration cost planning, see our AWS migration process overview.
Frequently Asked Questions
What is the minimum migration scope for MAP funding?
Generally, organizations need at least 10 servers or equivalent workloads to qualify for standard MAP funding. Smaller migrations may qualify for MAP Lite with reduced funding levels.
How quickly are MAP credits available after enrollment?
Assessment credits are typically available within 2-4 weeks of enrollment approval. Migration credits are allocated progressively as tagged workloads are verified, usually appearing on your bill within one billing cycle of tagging.
Can existing AWS customers get MAP funding?
Yes. Organizations already running some workloads on AWS can qualify for MAP funding when migrating additional on-premises infrastructure or modernizing existing AWS workloads at significant scale.
What is the difference between MAP and MAP Lite?
MAP Lite provides a streamlined assessment and reduced funding for smaller migrations. Standard MAP offers full-phase engagement with larger credit allocations for migrations involving 50 or more servers.
Does MAP funding cover third-party software licensing?
No, MAP credits apply only to AWS service consumption. Third-party marketplace purchases, data transfer fees to other providers, and non-AWS software licenses are typically excluded from credit coverage.
Editorial standards: This article was written by a certified practitioner and peer-reviewed by our engineering team. We update content quarterly to ensure technical accuracy. Opsio maintains editorial independence — we recommend solutions based on technical merit, not commercial relationships.
