$200K is the credit tier where the Migration Acceleration Program enters the composition. Activate Portfolio ($100K) provides the institutional base; MAP credits ($75K–$150K) fund the actual migration work — Assess sizing, Mobilize pilot, Migrate cutover. The combination is qualitatively different from the standard $150K stack: it covers infrastructure for what you're building AND subsidizes the labor of moving workloads off Heroku, GCP, Azure, or on-prem. This page walks through the MAP mechanics, the realistic credit timing across migration phases, and the tagging discipline that determines whether $50K of MAP credits actually lands in your account.
The $150K stack (Portfolio + Build for Startups + Bedrock POC) tops out at the ceiling of "standard" Activate-family applications. $200K is not "the $150K stack plus extra" — it's a different composition entirely, defined by the presence of Migration Acceleration Program credits.
AWS organizes its credit programs along two axes. The first axis is purpose: general infrastructure (Portfolio), discrete projects (Build for Startups), AI inference (Bedrock POC), migrations (MAP), AI-native cohorts (Generative AI Accelerator), committed-spend discounts (EDP). The second axis is mechanic: partner-filed via ACE, direct application via web form, sales-team negotiation. A $200K credit position requires combining programs across both axes — Portfolio (general purpose, partner-filed) plus MAP (migration purpose, partner-led with AWS Migration Hub instrumentation).
The MAP layer is what makes the $200K tier qualitatively different. Portfolio credits fund AWS consumption you would already be doing. MAP credits subsidize the actual labor and infrastructure cost of moving workloads from another platform — they're tied to migration milestones, tracked via Migration Hub, and conditional on tagging discipline. A startup that doesn't have substantial migration scope can't access MAP regardless of stage or fundraise size.
The eligibility profile reflects this. Pure Series-A startups building greenfield on AWS rarely reach $200K — there's no migration to fund. Series-B startups migrating off Heroku Enterprise, GKE on GCP, AKS on Azure, or on-prem datacenters routinely reach $200K and beyond because the migration cost is real and MAP is calibrated to fund 25%–50% of it. Bootstrapped companies migrating off legacy hosting (typically $20K+/month bills on managed Heroku, Salesforce Heroku Postgres, or aging VMware deployments) also fit the profile.
The $200K page exists because the credit composition at this scale is consistently different from the $150K page below it and the $300K page above it. The $300K page is dominated by the Generative AI Accelerator (competitive cohort selection); the $200K page is dominated by MAP (qualifying migration scope). Two different mechanics, two different application processes, two different eligibility filters.
The dominant $200K composition is Activate Portfolio plus MAP. A minority of Series-B startups assemble $200K via Portfolio plus Build for Startups plus Bedrock POC plus a MAP Assess phase. The dominant pattern accounts for roughly 70% of $200K credit positions in CloudRoute's routed engagement data.
The composition: Activate Portfolio funds your post-migration AWS infrastructure (the workloads that will run on AWS after the migration completes). MAP funds the migration itself (Assess sizing, Mobilize pilot, Migrate cutover).
Eligibility: Series-A late-stage to Series-B startup; ongoing migration with $500K–$1M total projected migration cost; existing cloud or on-prem spend at $10K+/month; commitment to substantial post-migration AWS consumption ($15K+/month projected).
Why this pattern dominates: the two layers have no overlap. Portfolio describes "the company's general AWS use case post-migration." MAP describes "the migration work itself." AWS reviewers don't flag overlap because the use cases are structurally distinct — one is about steady-state consumption, the other is about a discrete transition project.
What MAP doesn't cover here: the steady-state AWS bill after migration completes. MAP credits are migration-scoped. Once the migration is done, ongoing AWS consumption uses Portfolio credits (and any remaining MAP balance, which usually expires at month 24 from issue).
The composition: the full $150K stack from the prior tier, plus a MAP Assess phase that contributes approximately $50K. The Assess phase sizes the migration scope and earns credits for the discovery work — even when the full Mobilize and Migrate phases happen later or with a different partner.
Eligibility: Series-B startup; migration in early planning stage (haven't committed to Mobilize/Migrate budget yet); AI workload that fits Bedrock POC scope; distinct non-overlapping project that fits Build for Startups scope.
Why some Series-B startups assemble $200K this way: the four-layer approach front-loads credits. Portfolio + Build + Bedrock POC arrive within 18–21 days; MAP Assess arrives at week 4–6. By the time the company is ready to make the full Mobilize and Migrate commitment, they have $200K of credits already deployed, which de-risks the broader migration decision.
The tradeoff: this variant requires three distinct use cases (Portfolio infrastructure, Build for Startups discrete project, Bedrock POC AI workload) plus a credible MAP Assess. Many Series-B startups don't have the discrete-project framing for Build for Startups, in which case the dominant Portfolio + MAP pattern is simpler.
Some startups pursue the $200K target and land at $150K or $175K. The common reasons:
MAP Assess approves but Mobilize doesn't commit: if the company can't commit to a Mobilize budget within 90 days of the Assess phase, the MAP engagement effectively stops at Assess. MAP Assess alone returns roughly $25K, not the $75K–$150K that includes Mobilize. Total: $100K Portfolio + $25K MAP Assess = $125K, not $200K.
Migration scope too small for MAP: AWS partners typically don't pursue MAP for migrations below $300K total cost. The partner-led MAP overhead (Migration Hub setup, tagging convention, milestone reporting) doesn't justify the partner economics. Below the threshold, the company gets Portfolio + Build for Startups + Bedrock POC at $150K and forgoes MAP.
Tagging discipline missed mid-migration: Mobilize credits earn at 25% of correctly-tagged Mobilize phase cost. Resources spun up without the MAP tags earn $0. A team that spins up $200K of Mobilize-phase infrastructure but only tags $100K of it correctly earns $25K of MAP, not $50K. The other $25K evaporates.
The Migration Acceleration Program is structured around three phases. Each phase has its own eligibility criteria, deliverables, and credit calibration. Understanding the phase structure is what makes the $200K credit position realistically achievable rather than aspirational.
MAP is partner-led. AWS does not run the migration directly — a Migration Competency Partner runs the engagement and reports milestones to AWS via Migration Hub. Credit issuance is tied to partner-reported milestones, not customer self-reports. This is operationally important: the partner is incentivized to report milestones accurately because their MAP engagement funding (separate from customer credits) also depends on it.
Migration Hub is the AWS-side instrumentation. It tracks the migration inventory (what workloads exist, what their current state is, what their target state is), the migration progress (which workloads have moved through Assess, Mobilize, Migrate), and the tagged resource cost (which AWS resources are spinning up under MAP tags). The partner configures Migration Hub at the start of the engagement and updates it through the migration. Credit calculations pull from Migration Hub data.
Phase credit calibration reflects AWS's economic logic: subsidize the early high-friction work (Assess, where companies often abandon) at a flat rate, then accelerate credit issuance through Mobilize and Migrate where the company has already committed.
What happens: the partner conducts a Migration Readiness Assessment. This is a structured discovery process that sizes the migration: inventory of current workloads, target architecture on AWS, projected migration timeline, projected post-migration AWS spend, identified risks.
Duration: 2–6 weeks depending on scope. For a 40-engineer Series-B startup migrating off Heroku Enterprise, Assess typically runs 3 weeks.
Credit issued: approximately $25K, paid at completion of the Assess deliverable. Sometimes structured as direct credits in the AWS account; sometimes structured as partner-labor subsidy (the partner doesn't charge for the Assess engagement and receives the equivalent from AWS).
What gets approved: the Assess deliverable must include a Migration Readiness Assessment document, a Cloud Migration Plan, and a populated Migration Hub inventory. AWS reviews the deliverable before issuing credits — sloppy or incomplete Assess deliverables get held in review.
What happens: the partner runs a pilot migration. Typically 10%–20% of the total workload migrates as a proof point, with full instrumentation, tagging convention, monitoring, and rollback procedures in place. The Mobilize phase establishes the migration playbook that the Migrate phase will follow at scale.
Duration: 6–12 weeks. The pilot scope determines the duration — a Mobilize phase covering 4–6 microservices typically takes 8 weeks.
Credit issued: 25% of correctly-tagged Mobilize phase AWS consumption. For a Mobilize phase that consumes $100K of tagged AWS resources, MAP returns $25K. At the upper end ($300K Mobilize phase consumption), MAP returns $75K.
Why 25% and not 50%: the Mobilize phase has higher unknowns. AWS doesn't commit the higher subsidy rate until the company has demonstrated commitment by completing the pilot. Mobilize at 25% is the "credibility test"; Migrate at 50% is the reward for completing it.
What happens: the bulk of the migration. The remaining 80%–90% of workloads cut over from the source platform to AWS using the playbook established in Mobilize. This is the highest-credit-density phase because AWS is now subsidizing 50% of correctly-tagged consumption.
Duration: 12–36 weeks depending on scope. A 40-engineer Series-B migration from Heroku Enterprise typically runs Migrate for 16–24 weeks.
Credit issued: 50% of correctly-tagged Migrate phase AWS consumption, with a per-engagement ceiling. For a Migrate phase consuming $300K of tagged AWS resources, MAP returns $150K. At substantial enterprise scale ($1M+ Migrate phase consumption), MAP returns $500K. At the $200K page tier, Migrate typically contributes $75K–$125K (i.e., 50% of a $150K–$250K Migrate phase).
Why 50% works: the company has already committed by reaching Migrate. The remaining cost is largely AWS resource cost (compute, storage, data transfer) plus partner-labor cost. AWS subsidizes the AWS-resource side at 50% to remove the financial friction of completing the migration.
MAP credit calculation pulls from tagged AWS resource cost. The tag schema is defined at the start of the engagement; resources spun up without the tags don't count toward MAP credit calculation. This is the single most common failure mode in MAP engagements, and it's entirely preventable with discipline.
AWS Migration Hub looks for specific tags on resources to attribute them to a MAP engagement. The canonical tag schema includes map-migrated (boolean flag), map-program (engagement identifier), and resource-specific metadata tags. When AWS calculates MAP credits at the end of each phase, it queries the Cost Explorer for tagged resource cost in the phase window. Untagged resources are invisible to the credit calculation.
The trap appears innocuous. A platform engineer spins up a new RDS instance during the Mobilize phase because the pilot needs a database. The engineer doesn't apply the MAP tags because the tagging convention wasn't documented in the team's runbooks. The RDS instance runs for 8 weeks at $1,800/month. That's $3,600 of consumption that should have earned $900 of MAP credit (at 25% Mobilize rate). It earns $0.
Scale this across a typical Mobilize phase. If 30% of Mobilize-phase resources are untagged due to missed convention discipline, $30K of $100K Mobilize consumption is invisible, forfeiting $7.5K of credit. Across the full migration (Mobilize + Migrate), the cumulative loss can reach $50K or more for a $200K-tier engagement.
The fix is procedural, not technical. The partner installs the tagging convention before the first MAP-phase resource is created. Tagging is enforced via AWS Config rules that flag untagged resources, Service Catalog products that bake tags into provisioning templates, and Terraform/CloudFormation modules that include the tags as required parameters. The engineering team's runbooks specify the tagging convention. Pull request review checks for tag compliance.
CloudRoute partners report that engagement-time tagging discipline determines whether the MAP credit issuance lands at the high end or low end of the calibrated range. The same migration scope can return $75K MAP or $125K MAP depending on tagging discipline alone. This is the operational reason partner-led MAP outperforms self-service: the partner installs and maintains the convention. Self-service teams routinely lose $30K+ to drift.
At the $200K tier, the AWS relationship is qualitatively different from the pure-credit relationship of earlier stages. Series-B companies are typically also negotiating the Enterprise Discount Program, are assigned dedicated AWS account teams, and are starting to think about multi-year AWS commitments. The credit conversation happens against this broader backdrop.
A Series-A startup pursuing $150K credits interacts with AWS primarily through the partner that files Activate. There's no dedicated AWS account team, no sales cycle, no EDP conversation — just the partner-filed credit application. The economic relationship is "AWS gives credits; the startup consumes them; partner gets paid by AWS."
A Series-B startup pursuing $200K credits via Portfolio + MAP usually has at least the beginnings of an AWS account team relationship. The MAP engagement itself is partner-led but AWS-tracked; AWS assigns a Customer Solutions Manager to the migration; the company's monthly burn rate is large enough that AWS is paying attention. Once the burn crosses roughly $20K/month sustained, EDP negotiation becomes feasible.
EDP (Enterprise Discount Program) is structurally different from credits. EDP is a committed-spend discount: the company commits to a minimum annual AWS spend (typically $250K+/year for the first tier); AWS gives tiered discounts beyond a threshold (typically 10%–25% off list pricing). EDP is direct AWS (not partner-filed), negotiated through the AWS account team, and structured as a multi-year contract.
The credit + EDP combination is qualitatively different from pure credits. Credits expire (24 months for Portfolio, 12 months for Bedrock POC, 24 months for MAP). EDP discounts compound across the contract term and don't expire — every dollar spent gets the discount. For a Series-B startup spending $25K/month on AWS, a 15% EDP discount returns $45K/year in direct savings, recurring annually. Stacked over a 3-year EDP contract, that's $135K — qualitatively similar in dollar value to the $150K stack but structurally permanent.
CloudRoute partners filing the $200K MAP-included credit stack often surface EDP eligibility during the engagement. The conversation usually happens late in Mobilize or early Migrate, once the post-migration AWS spend projection is concrete enough to inform EDP commitment levels. Some companies pursue credits and EDP in parallel; others use credits to fund the migration and then transition to EDP economics post-migration. Both patterns are common.
The honest framing for Series-B founders: $200K of credits is one part of the AWS economic picture; the second part is the EDP discount you'll start negotiating in 12–18 months. Optimizing only for credit dollars and ignoring the EDP runway is a Series-A pattern; Series-B founders increasingly think about the combined credit + EDP position.
Not every Series-A or Series-B startup reaches $200K. The composition requires substantial migration scope, which is a specific situation rather than a stage-defined one. Here's the realistic eligibility profile from CloudRoute's routed engagements.
The $200K tier filters on migration scope first, fundraise stage second. A Series-A startup with a substantial migration ($500K+ total migration cost) reaches $200K. A Series-B startup with no migration (greenfield-on-AWS from the start) does not reach $200K — they typically cap at $150K because there's no MAP layer to add.
The $200K credit position doesn't land in 18 days the way the $150K stack does. The Portfolio portion arrives fast; the MAP portion trickles across the migration phases. Understanding the timeline shape avoids the founder pattern of expecting all $200K to be available before the migration starts.
Day 0 — Submit CloudRoute inquiry. Indicate migration scope (source platform, projected migration cost, target AWS region, team size). 3 minutes.
Day 1 — Routed within 24 hours to a Migration Competency Partner with the relevant source-platform expertise (Heroku, GCP, Azure, on-prem). Discovery call scheduled.
Day 2–3 — 60-minute discovery call covering current state, migration drivers, target architecture, MAP eligibility check.
Day 4–5 — Partner files Activate Portfolio ACE record ($100K) and registers the MAP engagement in Migration Hub. Two parallel tracks open.
Day 6–18 — Portfolio approval and credit issuance. $100K lands in the AWS account on the standard partner-filed timeline.
Week 2–6 — MAP Assess phase. Partner runs Migration Readiness Assessment, produces deliverables, populates Migration Hub. ~$25K MAP credits issued at Assess completion.
Week 4–14 — MAP Mobilize phase. Pilot migration runs with tagging discipline in place. MAP credits accrue throughout the phase at 25% of tagged consumption; final issuance at Mobilize completion. Typical Mobilize credit issuance: $25K–$75K.
Week 12–24 — MAP Migrate phase. Bulk migration. MAP credits at 50% of tagged consumption. Typical Migrate credit issuance: $50K–$150K depending on scale.
Week 24 — Full $200K credit position in account. Portfolio ($100K, fully usable since day 18). MAP Assess ($25K) + Mobilize ($25K–$75K) + Migrate ($50K–$150K) cumulatively summing to $100K+ depending on scope.
AWS designed MAP credit issuance to follow migration progress, not precede it. The economic logic is straightforward: companies that abandon migration mid-stream don't earn the back-end credits. This protects AWS's credit budget while still subsidizing the work that completes. For founders, the implication is that $200K planning needs to assume the Portfolio $100K covers the first 4–6 months of AWS consumption, with MAP credits arriving in time to fund the back half of the migration and the early post-migration phase.
Across CloudRoute's routed Series-B migrations, the engagement shape is consistent. Here's the composite walk-through for a 40-engineer B2B SaaS migrating off Heroku Enterprise.
The starting position: 40-engineer B2B SaaS, Series-B with $25M raised, currently spending $11K/month on Heroku Enterprise (compute dynos, Postgres, Redis, Kafka). Migration driven by scale limits hit on Heroku Postgres at 2.3 TB and unit-economics pressure (Heroku Enterprise pricing scales unfavorably above $10K/month). Total projected migration cost: $400K (engineering labor, partner-labor for cutover, AWS parallel-run cost, data transfer).
The credit composition: Activate Portfolio at $100K (filed against post-migration AWS consumption projection of $18K/month). MAP at approximately $100K cumulative — Assess at $25K, Mobilize at $25K (at 25% of $100K Mobilize phase consumption), Migrate at $50K (at 50% of $100K Migrate phase consumption). Total: $200K.
The engagement sequence: day 1 partner match; day 4 Portfolio ACE filed and MAP engagement registered; day 18 Portfolio credits issued; week 4 Assess deliverable complete and $25K MAP credit issued; week 12 Mobilize phase complete (10% of workloads migrated as pilot), $25K MAP credit issued; week 24 Migrate phase complete (remaining 90% of workloads cut over), $50K MAP credit issued.
The operational notes: tagging convention installed in week 3 before the first Mobilize resource was created; AWS Config rules enforced tag compliance throughout Mobilize and Migrate; Migration Hub kept current with weekly partner check-ins; phase transitions explicitly checkpointed with tag refresh.
The post-migration position: by end of week 28, the company is fully on AWS, MAP engagement closed, $200K credits in the account, projected to last 11 months at $18K/month consumption. EDP conversation opened with the AWS account team in week 26 for a multi-year commitment to begin once credits start to deplete.
The $200K composition is not a replacement for the $150K stack — it's an extension. The Portfolio + Build for Startups + Bedrock POC layers from the $150K page can still apply (in the Series-B variant); the difference is the addition of MAP, which only makes sense with substantial migration scope.
The dominant $200K composition (Portfolio + MAP) skips the Build for Startups and Bedrock POC layers entirely. This isn't because they're forbidden — it's because most Series-B migrations don't have clean Build-for-Startups-distinct projects or Bedrock-POC-AI-workloads in the same window as the migration. The migration is the focus; Build and Bedrock POC don't add cleanly until post-migration.
The Series-B variant ($100K Portfolio + $25K Build + $25K Bedrock POC + $50K MAP Assess) is a transitional composition that some Series-B startups use to front-load credits while keeping migration optionality. The full $200K is in-account within 6–8 weeks (Portfolio + Build + Bedrock POC by week 3; MAP Assess by week 6). Migration commitment to Mobilize and Migrate happens later if at all.
The eligibility shifts between the two stacks. The $150K stack requires three distinct use cases — general infrastructure (Portfolio), discrete project (Build), AI workload (Bedrock POC). The $200K stack requires the Portfolio use case plus substantial migration scope; the discrete project and AI workload are optional. This makes the $200K composition more accessible for migration-heavy companies that don't have AI workloads.
The honest comparison between the two adjacent credit tiers.
| Variable | $150K stack | $200K stack |
|---|---|---|
| Composition | Portfolio + Build for Startups + Bedrock POC | Portfolio + MAP (dominant); or Portfolio + Build + Bedrock POC + MAP Assess (variant) |
| Programs involved | 3 (all standard Activate-family) | 2 (Portfolio + MAP, the latter cross-program) |
| Use cases required | 3 distinct (infrastructure, discrete project, AI POC) | 2 (infrastructure + migration; discrete + AI optional in variant) |
| Eligibility filter | Series-A; AI workload + distinct project | Series-A late-stage to Series-B; substantial migration scope ($500K+ total cost) |
| Application mechanic | Three ACE records, same week | One ACE record (Portfolio) + MAP engagement registration via Migration Hub |
| Time-to-balance (full ceiling) | 18–21 days | Portfolio: 18 days · MAP: across 6–24 weeks following phase milestones |
| Partner role | Files all three ACE records | Files Portfolio ACE + runs MAP engagement (partner-led migration) |
| Approval risk | ~20% cumulative | ~15% Portfolio risk; MAP risk concentrated in tagging discipline and phase completion |
| Best for | Series-A with AI + distinct project, no migration | Series-A late / Series-B with substantial migration off Heroku, GCP, Azure, on-prem |
| What extending one to the other unlocks | Add MAP layer if substantial migration emerges | Add Build/Bedrock POC layers post-migration if non-overlapping use cases emerge |
Situation: B2B SaaS, Series-B with $25M raised, 40-engineer team. Running on Heroku Enterprise at $11K/month — compute dynos, Heroku Postgres (2.3 TB, hitting scale limits), Heroku Redis, Apache Kafka. Migration driven by Postgres scale ceiling and unfavorable Heroku Enterprise unit economics above $10K/month. Total projected migration cost: $400K (engineering labor + partner-labor + AWS parallel-run + data transfer). Target architecture: ECS Fargate for compute, Aurora PostgreSQL for the database tier, ElastiCache for Redis workloads, MSK for Kafka.
What CloudRoute did: Routed within 22 hours to a Migration Competency Partner with Heroku-to-AWS expertise. Discovery call confirmed MAP eligibility (migration scope $400K, post-migration AWS projection $18K/month, 40-engineer team). Partner filed Activate Portfolio ACE on day 4 ($100K against post-migration consumption projection) and registered the MAP engagement in Migration Hub. Tagging convention installed in week 3 before the first Mobilize resource was spun up; AWS Config rules enforced tag compliance throughout. Assess deliverable complete week 4. Mobilize phase ran weeks 6–14 covering 4 microservices and the Postgres database as pilot. Migrate phase ran weeks 14–24 cutting over the remaining workloads.
Outcome: Total credits secured: $200K. Portfolio $100K applied from day 18, covering the first ~5 months of parallel-run cost. MAP Assess credit ($25K) issued week 4. MAP Mobilize credit ($25K at 25% of $100K Mobilize phase tagged consumption) issued week 14. MAP Migrate credit ($50K at 50% of $100K Migrate phase tagged consumption) issued week 24. Migration complete week 28; final Heroku Enterprise contract terminated week 30. Post-migration AWS spend stabilized at $17.8K/month — close to the $18K projection that justified Portfolio. EDP conversation opened with AWS account team in week 26 for a 3-year committed-spend contract beginning once credit balance starts depleting in month 8 of post-migration operation.
engagement window: 28 weeks · founder time: ~18 hours total · credits secured: $200K · cost to customer: $0
CloudRoute routes Series-A late-stage and Series-B startups to AWS partners who file Activate Portfolio and run the MAP engagement. Portfolio credits arrive in 18 days; MAP credits arrive across migration phases over 6–24 weeks.