Most co-sell advice assumes your sellers live in Salesforce. Many AWS partners run HubSpot, Zoho CRM, Microsoft Dynamics 365, Freshworks' Freshsales, LeadSquared or Pipedrive, and some have no CRM at all. This guide explains what changes when Salesforce is not in the picture, as of November 2026. If your CRM is Zoho, the Zoho CRM and AWS ACE guide goes step by step.
Why so much co-sell material assumes Salesforce
AWS's own integration, the AWS Partner CRM connector, is a managed package on the Salesforce AppExchange. It is free and needs no code. In Salesforce it syncs ACE opportunities both ways, accepts or rejects AWS referrals, attaches solutions, AWS products and AWS Marketplace offers to opportunities, and manages Marketplace private offers and resale authorizations. AWS keeps releasing it: the latest version listed is 3.20, from 17 July 2026.
Two limits matter for everyone else:
- It is Salesforce only. AWS's integration guide says plainly that "the CRM connector only works with Salesforce."
- AWS leads are a separate story. The connector's documentation says partners who receive leads from AWS continue to use their earlier Amazon S3 integrations, and AWS stopped accepting new S3 integrations in 2024.
Because AWS's own tool is built for Salesforce, guides, templates and training tend to be too. The underlying data and rules are the same whatever your CRM.
The routes AWS documents
AWS's integration guide lists three routes: its connector, a third-party integration, and a custom integration built on the AWS Partner Central API. It notes that third-party and custom integrations support a wide range of CRMs, naming Zoho and Microsoft Dynamics as examples.
| AWS Partner CRM connector | Third-party integration | Custom integration | |
|---|---|---|---|
| CRMs | Salesforce only | A wide range | A wide range |
| Cost | Free to install; you pay for setup and upkeep | The provider's subscription | Development and maintenance |
| Effort, by AWS's figures | Low to medium development, plus a Salesforce administrator | Varies by provider | 3 to 12 weeks to build, then 2 to 3 weeks each quarter |
| Upkeep | Your administrator, with little developer help | The provider; you run the CRM side | Your team; upgrades may need code changes |
| Support | Limited support from AWS | The provider | AWS documentation and limited support |
Third-party integrations come in two broad kinds: co-sell and marketplace platforms, which often also cover AWS Marketplace listings and offers, and managed integration services that build and run the link for you.
One point to check before you plan around leads. AWS's integration-options page says custom integrations do not support lead management, yet the Selling API documentation covers lead invitations: accepting them, rejecting them and converting a lead into an opportunity. Read both pages when you decide, and ask any provider to show a lead working end to end.
What you need whatever your CRM
Accounts and access
- AWS Partner Central with the ACE terms accepted, under Sell.
- An AWS account linked to Partner Central. Someone with alliance lead or cloud administrator permissions links it under Account Linking. The API works only through a linked account.
- An IAM role or user in that account with Partner Central permissions. AWS publishes a managed policy,
AWSPartnerCentralOpportunityManagement, and recommends attaching it rather than copying it. - US East (N. Virginia), us-east-1. The Selling API and its events are there. Events reach the account's default Amazon EventBridge bus.
- Your solutions registered in Partner Central. Each opportunity needs at least one, or an AWS Marketplace product, and only solutions in Limited or Public status can be attached.
The fields ACE asks for
Whatever the CRM, the same data has to exist somewhere: the customer's company name, website, industry and country (and state for US customers), an opportunity title, a customer business problem of 20 to 2,000 characters, expected monthly AWS spend, a target close date in the future, and the use case, delivery model and sales activities. The last three take AWS's own values only, and most CRMs have no picklists for them until you add them.
A stage map
Every stage in your pipeline needs an ACE stage. AWS defines seven:
| ACE stage | What AWS means |
|---|---|
| Prospect | The opportunity is identified, from a lead or from research |
| Qualified | The customer agrees the opportunity is real and of interest |
| Technical Validation | All parties understand the implementation plan |
| Business Validation | Pricing was proposed and all parties agree the steps to close |
| Committed | The customer signed, and AWS has not started billing |
| Launched | The workload is complete, and AWS has started billing |
| Closed Lost | The opportunity is lost |
Only Qualified or later can be submitted. If your CRM has several pipelines, each needs its own map.
A plan for referrals and leads
AWS sends two kinds of invitation: referrals, where an AWS seller wants to work a deal with you, and leads from AWS marketing. Both expire if nobody answers. Decide who answers them, how fast, and where each lands in your CRM: a referral usually becomes a deal, a lead a lead.
Somewhere to test
Every Selling API call names a catalog: Sandbox for tests and AWS for real deals. Test the whole flow in the sandbox first. You can simulate AWS's side there, including an opportunity referred by AWS.
Options by CRM
Salesforce
AWS's connector is the obvious first look, and third-party integrations exist for Salesforce too.
HubSpot, Zoho CRM, Microsoft Dynamics 365, Freshsales, LeadSquared and Pipedrive
There is no AWS-built connector for these, so the choice is a third-party integration or your own build on the Selling API. What differs between these CRMs, and is worth checking for yours:
- API limits. Each CRM caps calls per day or per second. A sync reads a deal, its company and its contact, then writes AWS's answer back.
- Change notifications. Webhooks or notification channels let a sync react in seconds; without them it has to poll.
- Custom fields. You need room for AWS's fields and for AWS's view of each deal, and some editions limit custom fields.
- Leads. Whether the CRM keeps leads apart from deals decides where AWS leads land.
No CRM at all
You can co-sell straight from Partner Central. Create opportunities with the wizard or by talking to the Partner Central agent, answer AWS referrals in the Opportunity invitations tab, and use bulk import, plus bulk export and update for up to 1,500 opportunities at a time. This works at low volume.
The limits show as you grow. Partner Central holds only what you share with AWS, so deals AWS is not part of, activities and forecasts end up in spreadsheets. Everyone who works a deal needs Partner Central access.
The other choice is a lightweight CRM from the start: a general CRM that you then connect, or a co-sell tool with a basic CRM built in. Either way, check that it has AWS's fields from day one and that you can export your data.
Questions to ask any integration option
- Who holds the credentials? On the AWS side, does the option use an IAM role in your account that you can inspect and remove, or access keys you hand over? On the CRM side, where are its tokens stored?
- Where does the data live? In whose AWS account, in which Region, and what is kept beyond what passes through?
- Can it run in your own AWS account? Some teams need the integration inside their own account for security or procurement reasons.
- How is it priced? Per user, per Partner Central account, per opportunity or flat? What changes at renewal?
- Does it handle both referrals and leads? Ask to see an AWS lead arrive, get accepted, land in your CRM and become an opportunity.
- Does it check AWS's rules before submitting? Required fields, AWS's picklist values and the stage, or does a seller only learn of a problem after AWS refuses?
- What happens when AWS locks fields? Nothing can change while an opportunity is Submitted or In review, Action Required opens only a few fields, and approval locks the title, country, postal code, industry, website, business problem and partner identifier. Does it skip and explain, or retry forever?
- How does it respect limits? Your CRM's API budget, and Partner Central's quotas of 1 write a second and 10,000 a day per partner account.
- Does it support the Sandbox catalog, and several Partner Central accounts if you have them?
Where CoSell fits
CoSell connects HubSpot, Microsoft Dynamics 365, Zoho CRM and LeadSquared, as well as Salesforce, to AWS Partner Central through the Selling API, and includes its own CRM for partners who have none. It checks each deal against AWS's rules before submitting it, and brings AWS referrals and leads back into the CRM. It runs hosted by HabileLabs or in your own AWS account. It is sold from USD 10 a month on AWS Marketplace; as of November 2026 the offer is for AWS accounts in India. See every CRM CoSell connects and pricing.
Sources
- Integration options (opens in a new tab) and Integration prerequisites (opens in a new tab) (checked 13 November 2026)
- CRM connector overview (opens in a new tab), Available features (opens in a new tab) and Release notes (opens in a new tab) (checked 13 November 2026)
- ACE program (opens in a new tab) (checked 13 November 2026)
- Using the AWS Partner Central Selling API (opens in a new tab) and Setup and authentication (opens in a new tab) (checked 13 November 2026)
- Testing in a sandbox (opens in a new tab), Notifications (opens in a new tab) and Quotas (opens in a new tab) for the Selling API (checked 13 November 2026)
- Manage leads using the Selling API (opens in a new tab) and Working with opportunity updates (opens in a new tab) (checked 13 November 2026)
- LifeCycle (opens in a new tab) and Project (opens in a new tab) data types (checked 13 November 2026)
- Creating an opportunity (opens in a new tab) and Bulk actions (opens in a new tab) (checked 13 November 2026)