⚠ Deadline: June 30, 2026

AWS Partner Central
Migration Readiness Checklist

The complete pre-migration audit for ISVs running ACE co-sell through Salesforce or HubSpot.

Author: Stefan Tabacaru Published: May 2026 Applies to: AWS ISV Accelerate partners Deadline: June 30, 2026

Section 1

5-Question Readiness Audit

Answer No to any of these and you have a live risk to your co-sell pipeline before June 30.

Portal migration completed

New AWS Console experience active. IAM policies mapped. Users migrated. Solutions live on Marketplace. Typically 4–8 weeks of engineering capacity for a mid-sized ISV.

CRM-to-ACE sync on new Partner Central API (not legacy S3)

The portal migration and the API migration are independent. Completing the portal migration does NOT fix your Salesforce or HubSpot sync. Test this separately.

All required ACE fields mapped correctly in CRM

New Partner Central introduced mandatory fields. Missing fields cause silent submission failures with no error message.

Partner Revenue Measurement (PRM) implemented

Mandatory since January 2026 for ISVA MDF access. Tracks ACR, MBS, and co-sell engagement KPIs. Separate from the migration - many ISVs miss this.

AWS sellers see clean, continuous pipeline through transition

Any gap in ACE activity signals disengagement to your PSM. Brief your PDM before and after migration. The best migrations are invisible to your AWS field team.

Section 2

7-Week Action Plan

W 1–2

Complete the portal migration

Use AWS's one-click migration tool. Map IAM policies. Clazar, Labra, and WorkSpan all offer free advisory for the portal side - use them.

W 2–3

Audit your CRM integration

Confirm you're on the new Partner Central API, not legacy S3. Verify all active ACE opportunities have synced correctly. Don't assume.

W 3–4

Validate field mappings

Confirm all required co-sell fields are populated on live opportunities. Fix gaps before they become rejection patterns.

W 4–6

Run a parallel end-to-end test

Submit a test opportunity through your CRM. Confirm it appears correctly in the new Partner Central console - timestamps, field values, and acceptance status.

W 7

Brief your PSM

Tell your AWS partner manager migration is complete and pipeline is clean. This is a relationship touchpoint, not just a compliance checkbox.

Section 3

CRM Field Mapping - What to Check

The new Partner Central requires 14 mapped fields in your CRM. Missing any will cause silent failures with no error message.

Core opportunity fields mapped and populated

Company name, website, opportunity type, stage, close date, and expected revenue - all required. Several have strict format requirements that differ from the legacy ACE API.

Two new mandatory fields added in January 2026

Two fields became required for all API-based co-sell submissions in January 2026. Both are commonly missing from existing CRM setups and cause silent rejection. I'll confirm whether your setup includes them on the call.

Customer contact fields use domain email (not Gmail/Yahoo)

Primary contact email must be a corporate domain. Submissions with personal email addresses are rejected at validation.

Solution name matches your AWS Marketplace listing exactly

Case-sensitive match required. If your listing name changed during migration, existing CRM field values may no longer match - causing all new submissions to fail.

Note: The specific field names, allowed values, and format requirements vary depending on whether you're using HubSpot or Salesforce. I review the full mapping against your specific CRM setup on the readiness call.

Section 4

Partner Revenue Measurement - MDF Unlock

PRM implementation confirmed with PDM

Required for all ISVs enrolled in ISVA after January 1, 2026 to access MDF. Contact your PDM to verify implementation status.

ACR (AWS Consumed Revenue) tracking active

Trailing 12-month ACR visible in Partner Central dashboard. Required metric for MDF eligibility.

MBS (Marketplace Billed Sales) tracked

Trailing 12-month Marketplace billed revenue. Required alongside ACR for full ISVA MDF access.

Co-sell engagement count meets threshold

Minimum 5 co-sell opportunity launches in trailing 12 months required for MDF eligibility.

Important: PRM implementation is independent of both the portal migration and the CRM API migration. Many ISVs complete both migrations but still can't access MDF because PRM was never set up. Confirm with your PDM before June 30.

Need help with your CRM integration?

I review CRM-to-ACE sync setups and field mappings for ISVs before the June 30 deadline.
Free 20-minute check - no pitch.

Book a strategy call

linkedin.com/in/stefantabacaru