AWS Partner Central legacy interfaces deprecate on June 30, 2026.
01 What's actually changing
AWS is consolidating partner-facing surfaces, the legacy APN Partner Central, ACE Pipeline Manager, and several adjacent systems, into a unified Partner Central experience with a new Partner Revenue Measurement framework, a re-shaped ACE schema, and modernized integration endpoints replacing the legacy S3-based CRM sync.
Most ISVs will see three operational changes immediately: ACE opportunity fields have been re-mapped, partner-attribution rules now flow through Partner Revenue Measurement, and S3-bucket CRM sync stops working in favor of API-based integration.
If your CRM-to-ACE integration was set up before 2024 and has not been re-validated in the last six months, assume it will break on July 1, 2026. The cost of finding out the day after is the missing co-sell attribution for the entire next reporting cycle.
02 Who's at risk
Three categories of ISV are exposed. The third is the one most likely to be overlooked.
Legacy S3-sync ISVs
CRM-to-ACE integrations that push opportunities through an S3 bucket. These stop functioning entirely; replacement is API-based and requires re-mapping.
Manual ACE operators
Teams submitting opportunities directly into ACE without CRM sync. The UI changes; existing workflows and field placement will need re-training.
ISVs with custom attribution rules
Anyone with bespoke partner-attribution logic, co-sell ratio reporting, MDF eligibility tied to ACE volume, needs to validate the new Partner Revenue Measurement schema.
03 The four pre-cutover checks
These are the checks every engaged ISV should complete before mid-June 2026. The first two are mechanical; the second two require sign-off from finance and revops.
- 1, Integration mode. Confirm whether your CRM-ACE sync runs through S3 or a supported API endpoint. Anything S3-based needs migration.
- 2, ACE field mapping. Open a sample opportunity in the new Partner Central preview and verify every required field, stage, AWS attribution, expected close, dollar amount, maps correctly from your CRM.
- 3, Partner Revenue Measurement alignment. Have revops confirm that co-sell attribution under the new framework still credits the deals your finance team expects to count.
- 4, User provisioning. Audit who has access to Partner Central today and remove dormant users. Permissions are being re-evaluated as part of the cutover.
04 Migration timeline
If you're starting now (May 2026), here's a workable sequence. The hard deadline is June 30; you want everything operational two weeks before that to allow for the inevitable surprise.
Audit current integration
Inventory the existing CRM-ACE sync, mode (S3 vs. API), field mappings, attribution rules, custom logic. Identify owner of each piece.
Build the migration plan
Scope the work: API endpoint changes, field re-mapping, integration testing. Engage your CRM partner-ops vendor or internal team. Schedule the cutover window.
Execute and parallel-run
Implement the new integration. Run both systems in parallel for at least one week to validate that every opportunity syncs correctly. Verify Partner Revenue Measurement attribution against your reporting.
Cutover & user retraining
Decommission the legacy sync. Retrain ACE operators on the new interface. Document the new workflow for finance and exec reporting.
Legacy interfaces deprecated
S3-based sync and legacy Partner Central UI stop functioning. No grace period announced.
05 What we're seeing in client engagements
Across the dozen ISV engagements where we've run this audit in Q1 and Q2 2026: roughly two-thirds were still on legacy S3 sync; one-third had Partner Revenue Measurement attribution misalignments that would have understated their co-sell ratio by 15–40% under the new framework; and almost every client had at least one dormant Partner Central user that needed clean-up.
The migration itself is not technically hard. The risk is that no single person inside the ISV owns the end-to-end integration, it sits between revops, the cloud alliance lead, and an external integration vendor, and ownership ambiguity is what causes the missed deadline.
If you don't know whether your CRM-to-ACE sync runs through S3 or API, that's the first phone call to make. Five minutes with whoever set it up gives you the answer. Everything else flows from there.