--- title: "Migrating to the New AWS Partner Central (ACE)" url: https://www.suger.io/resources/blog/migrating-to-aws-partner-central/ canonical: https://www.suger.io/resources/blog/migrating-to-aws-partner-central/ type: Blog description: "Migrating to the new AWS Partner Central: the AWS Console move, the S3-to-API co-sell switch, and what breaks in your CRM connector during the cutover." --- # Migrating to the New AWS Partner Central (ACE) > Canonical HTML version: https://www.suger.io/resources/blog/migrating-to-aws-partner-central/ 1. [Home](/) 2. / 3. [Resources](/resources/) 4. / 5. [Blog](/resources/blog/) 6. / 7. Migrating to the New AWS Partner Central (ACE) # Migrating to the New AWS Partner Central (ACE) AWS moved Partner Central into the AWS Console and is retiring the S3 co-sell integration. What migrating actually changes for your ACE data and CRM. [![Sabrina Xie](/authors/sabrina-xie.jpg)](/resources/blog/author/sabrina-xie/) [Sabrina Xie](/resources/blog/author/sabrina-xie/) Aug 24, 2026 ![Migrating to the New AWS Partner Central (ACE)](/images/blog/migrating-to-aws-partner-central/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fmigrating-to-aws-partner-central%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fmigrating-to-aws-partner-central%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fmigrating-to-aws-partner-central%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fmigrating-to-aws-partner-central%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with Perplexity") Table of Contents - [What is changing with AWS Partner Central?](#what-is-changing-with-aws-partner-central) - [The migration, in four steps](#the-migration-in-four-steps) - [The bigger change underneath: S3 to API](#the-bigger-change-underneath-s3-to-api) - [What breaks in your CRM connector](#what-breaks-in-your-crm-connector) - [How Suger helps](#how-suger-helps) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _Migrating to the new AWS Partner Central means moving your partner experience into the AWS Console with account linking and IAM, and switching your co-sell data flow from the legacy Amazon S3 exchange to a real-time API — a change that touches your ACE workflow and your CRM connector._ * * * If you run co-sell through AWS Partner Central, two changes are converging on your team. AWS has moved the Partner Central experience into the AWS Console, and it is retiring the old Amazon S3 file exchange that ACE integrations were built on in favor of a real-time API. Neither has a loud deadline, which is exactly why they’re easy to defer past the point where they should have been planned. Here is what actually changes, what breaks in your CRM connector if you don’t prepare, and how to sequence the migration. * * * ## **What is changing with AWS Partner Central?** Two distinct things, often conflated. First, the **platform move**: existing APN Partners get a self-service tool to migrate to the new Partner Central experience in the AWS Console, after which access runs through a linked AWS account using IAM roles and credentials instead of standalone APN sign-in. Second, the **co-sell capability**: partners can now associate one or more AWS Marketplace solutions and products directly to a co-sell opportunity in Partner Central — up to 10 solutions and 10 products per opportunity — and a Marketplace solution, Marketplace product, or partner solution must be associated to advance an opportunity to Committed or Launched. The same association is available through the AWS Partner Central Selling API. This tightens the link between a co-sell opportunity and the [Marketplace private offer](/platform/private-offers/) that transacts it. * * * ## **The migration, in four steps** The platform migration is self-service and runs in a defined sequence: 1. **Readiness checklist** — confirm your APN account is ready to move. 2. **Link an AWS account** to the APN account. This linked account becomes primary and is charged the APN membership fee going forward. 3. **Set up user access** through IAM managed policies, so the right people can reach Partner Central in the Console. 4. **Schedule and initiate** the migration. Plan for downtime: during migration, all users are blocked from Partner Central, and it typically takes between two and six hours depending on data volume. Run it outside business hours so a co-sell team isn’t locked out mid-deal. * * * ## **The bigger change underneath: S3 to API** The change most likely to break something quietly is the co-sell data integration. The legacy model exchanged ACE data through a managed Amazon S3 bucket; the new API-based integration replaces that with real-time, bidirectional synchronization through IAM roles and APIs, with inbound updates pushed via EventBridge instead of polled from a bucket. The status matters: the S3-based integration is deprecated and no longer available to new users, and AWS advises partners still on it to plan their move to the API to avoid service degradation. There is no published end-of-life date on the migration pages — AWS defers the S3 backend timeline to its CRM integration documentation — so don’t invent one, but don’t treat “no deadline” as “no urgency” either. The one hard prerequisite for the API upgrade is AWS account linking; you do not have to complete the full Partner Central console migration first. * * * ## **What breaks in your CRM connector** If you run the AWS co-sell integration through a CRM connector, the switch is not transparent — several things change and a few actively break if left alone: - **Install the latest CRM connector** from AppExchange; older versions are built for the S3 model. - **Legacy fields are retired.** “Sync with AWS” and “Has Updates for AWS” are no longer used, replaced by an “Enable Share with AWS Integration” setting. - **Deactivate and delete the old APN scheduled jobs.** Lingering jobs are a known cause of duplicate opportunities after the switch. - **Swap the legacy buttons** — “Send to AWS” becomes “Share with AWS,” and “Link Private Offer” becomes an associate/disassociate action. - **Deactivate legacy validation rules and flows**, and run a backfill to populate the Last Modified Date field the API sync relies on. One caveat to know before it surprises you: solutions created in the new experience use a `soln-` identifier format that the CRM connector does not yet support — it still expects the legacy `S-` format for the solution offered. Existing `S-` solutions keep working, so this is a “don’t assume the new IDs flow through yet” caution, not a blocker. The co-sell mechanics all of this plumbing serves are covered in [how co-sell works](/resources/blog/how-co-sell-works/), and the ACE workflow itself in the [AWS ACE guide for ISV sellers](/resources/blog/aws-ace-guide-for-isv-sellers/). * * * ## **How Suger helps** Co-sell is only useful if the opportunity, the CRM record, and the Marketplace offer stay in sync — which is exactly what a mid-migration integration threatens. [Suger](/platform/cosell/) automates co-sell across AWS, Microsoft, and Google Cloud and keeps opportunities synced with your CRM, so a team moving to the new Partner Central runs one integration rather than hand-maintaining the ACE connection through the cutover. The co-sell opportunity and the private offer that transacts it stay in one record, on the current integration path. * * * ## **Frequently asked questions** **What is changing with AWS Partner Central?** Two things: the Partner Central experience moved into the AWS Console (accessed via a linked AWS account and IAM), and the co-sell data integration is moving from a legacy Amazon S3 file exchange to a real-time, bidirectional API. **Is there a deadline to migrate?** The platform migration is self-scheduled with no fixed calendar date, and AWS has not published an end-of-life date for the S3 integration on its migration pages. But the S3 model is deprecated and closed to new users, so plan the move rather than deferring it. **How long does the Partner Central migration take?** Typically two to six hours, depending on your data volume. All users are blocked from Partner Central during migration, so AWS recommends running it outside business hours. **What breaks in my CRM connector?** Legacy fields (“Sync with AWS,” “Has Updates for AWS”) and buttons are replaced, old APN scheduled jobs must be deleted to avoid duplicate opportunities, and you install the latest connector. New `soln-` solution IDs aren’t supported by the connector yet; legacy `S-` IDs still work. **Do I have to migrate the console before switching to the API?** No. The one hard prerequisite for the S3-to-API upgrade is linking an AWS account. You can upgrade the co-sell integration to the API without first completing the full Partner Central console migration. * * * ## **Takeaways** - Two changes are converging: Partner Central moved into the AWS Console (linked account + IAM), and the S3 co-sell exchange is being replaced by a real-time API. - The platform migration is self-service, blocks users for two to six hours, and makes the linked AWS account primary and billable for the membership fee. - The S3 integration is deprecated and closed to new users; there’s no published end-of-life date, but plan the API move now. - Prepare your CRM connector: update it, retire legacy fields and jobs, run the backfill, and know that new `soln-` IDs aren’t connector-supported yet. * * * Keep co-sell in sync through the cutover: see how [Suger automates co-sell](/platform/cosell/) across AWS, Microsoft, and Google Cloud, and [book a demo](/schedule-demo/). ## Sources Primary sources for the platform rules cited above. Last verified August 24, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [AWS: Associate AWS Marketplace listings to co-sell opportunities in Partner Central](https://aws.amazon.com/about-aws/whats-new/2026/07/aws-marketplace-co-selling-support/) — Associate up to 10 solutions and 10 products per opportunity; a Marketplace or partner solution must be associated to advance an opportunity to Committed or Launched; also available via the Partner Central Selling API. - [AWS Partner Central: Migrating to Partner Central in the AWS Console](https://docs.aws.amazon.com/partner-central/latest/getting-started/migrating-to-partner-central.html) — Self-service migration; four steps (readiness, link an AWS account, IAM user access, schedule/initiate); users blocked during migration, typically 2 to 6 hours; the linked AWS account is charged the APN membership fee. - [AWS Partner Central: Upgrading from Amazon S3 to API-based CRM integration](https://docs.aws.amazon.com/partner-central/latest/crm/upgrade-crm-api.html) — The API integration replaces the legacy S3 bucket model with real-time, bidirectional sync via IAM roles and APIs (EventBridge inbound); S3 is deprecated and unavailable to new users; account linking is the prerequisite. ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.