Opportunity submission freezes
You can no longer submit or manage ACE co-sell opportunities through the legacy portal.
A TeckPath product
AWS Partner Network · mandatory cutover
Legacy Partner Central is moving into the AWS Management Console under IAM. TeckPath helps Alliance Leads and IAM admins prepare the account, map users, and execute the irreversible cutover without freezing co-sell operations.
DEADLINE SIGNAL · SEPTEMBER 30, 2026
If you wait
Missing migration is not a cosmetic UI issue. Legacy APN workflows stop while your pipeline, channel motions, and Marketplace alignment still need to run.
You can no longer submit or manage ACE co-sell opportunities through the legacy portal.
Accepting AWS referrals and progressing joint deals becomes unavailable on legacy Partner Central.
Reseller relationship approvals and related channel operations move exclusively to Partner Central 3.0.
Legacy catalog and solution metadata management for Marketplace alignment is no longer available.
Without Console Partner Central access, day-to-day APN operations stall until migration completes.
The linked paid AWS account becomes permanent after migration starts. Choosing poorly is expensive to unwind.
What AWS requires
Alliance Lead or Cloud Admin owns the final click in legacy Partner Central. Everything before that is preparation TeckPath can run with your IAM administrator.
| Step | What good looks like | TeckPath support |
|---|---|---|
| 1. Identify primary AWS account | Paid, company-owned member account; billing address matches HQ; not a payer/sandbox account | Account selection checklist + readiness scan |
| 2. Link AWS ↔ Partner Central | Standard PartnerCentralRoleFor* roles with managed policies attached | IAM role provisioning + linking handoff |
| 3. Business verification | Verification status SUCCEEDED before cutover | Verification status tracking |
| 4. Onboard users to IAM | Legacy roles mapped to AWSPartnerCentral* / Marketplace policies or Identity Center | User CSV persona → policy mapping |
| 5. Initiate or schedule migration | Off-hours window; all users notified; 2–6 hour downtime expected | Cutover runbook (final click stays in Partner Central) |
| 6. Validate Console experience | ACE pipeline, Marketplace linkage, and IAM sign-in confirmed | Post-migration validation checklist |
IAM mapping
AWSPartnerCentralFullAccess + AWSMarketplaceSellerFullAccess
AWSPartnerCentralOpportunityManagement + offer management policies for Marketplace linkage
Account management association policy plus full Partner Central and Marketplace access for linking
Skill Builder–only users often need no Partner Central access after migration. Marketing and channel personas map to dedicated Partner Central marketing and channel managed policies.
Cutover facts
All users are blocked on legacy Partner Central while data moves. Schedule off-hours.
After migration begins you cannot unlink or change the primary AWS account. ACE history stays there.
Plan to the date in your Partner Central migration widget. Ecosystem messaging commonly cites September 30, 2026. Do not assume an extension.
No public InitiateMigration API exists. Alliance Lead or Cloud Admin must start Migrate now / Schedule inside legacy Partner Central. TeckPath prepares everything up to that handoff and validates afterward.
A paid, company-owned member account in good standing, with a billing address matching your primary business location. Avoid Organizations management/payer accounts, personal accounts, and sandboxes.
Sentinel is TeckPath’s AWS Cloud Advisor for posture, architecture decisions, and governed remediation. Partner Central migration is a companion engagement for AWS Partners who must move off the legacy APN portal—often the same customers already trusting TeckPath with AWS operations.
TeckPath walks Alliance Leads and IAM admins through account choice, IAM prep, user mapping, and cutover timing—before co-sell goes dark.