Skip to content
Guide

Zoho CRM and AWS ACE: getting Zoho deals into ACE and AWS referrals back into Zoho

Your sellers work in Zoho CRM, and AWS sees co-sell deals only in ACE, inside AWS Partner Central. This guide covers the ways to connect the two, how a Zoho deal becomes an ACE opportunity, and what it takes to keep both in step.

9 min readUpdated By the HabileLabs CoSell team

If your team sells from Zoho CRM and co-sells with AWS, each co-sell deal has to exist twice: in Zoho, where your sellers work, and in ACE, the opportunity pipeline in AWS Partner Central. This guide covers both directions, as of November 2026. For the AWS-to-partner direction in more depth, see AWS referrals explained.

What ACE is and why partners log opportunities

ACE (APN Customer Engagements) is AWS's co-selling programme. You share opportunities in Partner Central, AWS reviews each one you submit, and approved ones join AWS's sales pipeline. ACE-eligible partners also receive referrals from AWS.

Partners log opportunities because:

  • AWS sellers can only help with deals they can see. Once AWS accepts one, you can get help with technical validation and pricing.
  • AWS asks partners to keep opportunities up to date to keep their visibility with AWS Sales.
  • AWS referrals and leads arrive in Partner Central, so someone has to watch it anyway.

Your options

Enter deals by hand in Partner Central

Under Sell → Opportunities, Partner Central offers a wizard, or a conversation with the Partner Central agent that fills in the fields for you to approve. It suits a few deals a month, but means double entry, and Zoho never learns what AWS said.

Bulk upload in Partner Central

Import Opportunities takes AWS's Excel template, saved as CSV, which you can fill from a Zoho report export. Export Opportunities and Update Opportunities handle up to 1,500 opportunities at a time. It is still manual, and review results and referrals do not reach Zoho.

Build on the Partner Central Selling API

You write and run it yourself. It involves:

  • A linked AWS account. Someone with alliance lead or cloud administrator permissions links it under Account Linking in Partner Central.
  • An IAM role or user in that account. AWS publishes a managed policy, AWSPartnerCentralOpportunityManagement, and recommends attaching it rather than copying it.
  • One endpoint, partnercentral-selling.us-east-1.api.aws, in US East (N. Virginia). Requests are signed with Signature Version 4, which the AWS SDKs do for you.
  • A sandbox. Each call names a catalog: Sandbox for tests, AWS for real deals. In the sandbox you play AWS's part, for example by setting a review status to Approved yourself.
  • Events. Partner Central sends events such as Opportunity Updated and Engagement Invitation Created to the default Amazon EventBridge bus in us-east-1.
  • Quotas. Writes are limited to 1 a second and 10,000 a day per partner account; reads to 10 a second and 100,000 a day.
  • The Zoho half: an OAuth client, change notifications, custom fields and retries.

AWS's own estimate for a custom integration is 3 to 12 weeks of initial development, then 2 to 3 weeks each quarter for maintenance and upgrades.

Buy a connector or a managed service

AWS's free AWS Partner CRM connector is a Salesforce package, so it does not help a Zoho shop. AWS also lists third-party integrations, and says they, like custom integrations, support CRMs such as Zoho. They come as co-sell and marketplace platforms, and as managed integration services that build and run the link for you.

How a Zoho deal maps to an ACE opportunity

An ACE opportunity draws on three Zoho records: the deal, its account and its contact.

The fields ACE requires

ACE fieldUsual Zoho sourceWhat AWS checks
Customer company nameAccount NameRequired
Customer websiteAccount WebsiteA real domain, not a social media page
IndustryAccount IndustryOne of AWS's values; Other needs a description
Country, postal code, stateAccount billing addressTwo-letter country code; a state for US customers
Opportunity titleDeal NameLocked once approved
Customer business problemDescription, or your own field20 to 2,000 characters
Expected monthly AWS spendAmount, or your own fieldMonthly; USD, or EUR where AWS allows it
Target close dateClosing DateIn the future
Use case, delivery model, sales activitiesCustom picklistsAWS's own values only
Partner opportunity identifierZoho deal IDLets you find the deal again
SolutionsPer deal or per product line1 to 10 of your solutions

Zoho's Industry picklist needs a value map to AWS's, and Billing Country is free text that must become a code such as IN.

Stage mapping

ACE has seven stages. An opportunity must be Qualified or later to be submitted, and AWS says deals already won, launched or lost should not be submitted. One way to map Zoho's standard stages:

Zoho stageACE stage
QualificationProspect (not submitted yet)
Needs AnalysisQualified
Value PropositionTechnical Validation
Identify Decision MakersTechnical Validation
Proposal/Price QuoteBusiness Validation
Negotiation/ReviewBusiness Validation
Closed WonCommitted, then Launched once AWS billing starts
Closed LostClosed Lost

Choose the Zoho stage at which a deal goes to AWS, and map custom stages too. Committed means the customer signed and AWS has not started billing; Launched means the workload is complete and billing has started. AWS asks for the customer's AWS account when you close as Launched, and a reason when you close as Closed Lost.

Not every Zoho deal is a co-sell deal: a checkbox on the deal lets sellers opt in.

Business problem, solutions and spend

  • Customer business problem. AWS asks for this customer's specific pain, what forces them to act now and the outcome they expect. Zoho's Description often holds internal notes, so choose the source field with care.
  • Solutions. Each opportunity needs at least one of your solutions, or an AWS Marketplace product. Only solutions in Limited or Public status can be attached.
  • Expected spend. ACE wants the customer's expected monthly AWS spend. Zoho's Amount usually holds your deal value, a different number, so many teams add a field. Convert other currencies to USD first.

Keeping it in sync both ways

AWS review status

A submitted opportunity moves through Submitted and In review to Approved, Action Required or Rejected, which AWS says can take up to five business days.

  • Submitted and In review: nothing can change.
  • Action Required: AWS's comments say what to fix. Only the address, website, close date, expected spend, business problem and partner identifier can change.
  • Approved: most fields stay editable, but the title, country, postal code, industry, website, business problem and partner identifier are locked.
  • Rejected: read-only.

Write the review status and AWS's comments into read-only Zoho fields so sellers see them, and treat Action Required as a task for the deal owner.

The AWS seller and AWS's view

The AWS opportunity summary holds AWS's side of the deal: the AWS team, whether AWS is co-selling or only has visibility, AWS's stage and next steps, and an engagement score. Fetch it with your own opportunity when an Opportunity Updated event arrives, since AWS sometimes edits yours directly. Keep AWS's stage in its own Zoho field.

Locked fields and refusals

Sellers will edit locked fields in Zoho: skip those fields and tell the seller rather than retrying. AWS notes other restrictions by programme or opportunity type, so handle refusals field by field. For fields both sides change, such as close date and next steps, decide which system wins.

AWS referrals and leads into Zoho

Referrals

An AWS referral arrives as an engagement invitation. Before you accept, you see the title, use case, stage and business problem, but not the street address, city, postal code, customer contact or the customer's AWS account. Invitations expire, so route them to a person quickly.

Accepting creates the opportunity in your Partner Central account. Then create the Zoho account, contact and deal, checking for an existing account first, and store the ACE opportunity ID. Rejecting needs a reason, and you lose access to the opportunity.

Leads

AWS also sends lead invitations from its marketing. Before you accept, you see the company, industry, country, campaign and the contact's job title; the contact's name, email and phone come only after. A lead belongs in Zoho's Leads module, matched by email to avoid duplicates.

When the lead is qualified, convert it through Partner Central, not only in Zoho: AWS's conversion links the new opportunity to the lead, keeping its history and attribution. Then complete the opportunity and submit it.

Zoho API limits and why they matter

Zoho counts API use in credits over a rolling 24 hours. Free has 5,000. Standard has 50,000 plus 250 per user licence, up to 100,000. Professional adds 500 per licence, up to 3,000,000; Enterprise adds 1,000, up to 5,000,000; Ultimate adds 2,000, with no cap.

Most calls cost one credit. Inserts and updates cost one per 10 records, and a COQL query costs 1 to 3 depending on the rows it asks for (up to 2,000 a call). Zoho also limits calls running at once, from 10 on Standard to 25 on Ultimate, and answers TOO_MANY_REQUESTS beyond that.

Every synced deal reads the deal, account and contact and writes AWS's fields back, and other integrations share the budget. Give the integration its own daily budget, and make it pause cleanly when that is spent.

Three Zoho specifics shape the design:

  • Notifications, not polling. Zoho's Notifications API sends the IDs of changed records to your endpoint. A channel lasts at most one week, so renew it.
  • COQL for reconciliation. A periodic COQL query catches anything a notification missed, up to 100,000 records per set of criteria.
  • Data centres. Each Zoho org lives in one data centre, such as US, EU or India, and API calls must go to that data centre's domain.

A checklist to get started

  1. Confirm your company has accepted the ACE terms in Partner Central.
  2. Link the AWS account you will use to Partner Central.
  3. Check your solutions are Limited or Public.
  4. Decide which Zoho deals are co-sell deals and how sellers mark them.
  5. Choose the submission stage and map every Zoho stage.
  6. Add Zoho fields for use case, delivery model, sales activities and monthly AWS spend.
  7. Map industry and country values, and fill them in on accounts.
  8. Decide who answers AWS referrals and leads, and how fast.
  9. Check your Zoho edition's API credits and custom-field limits.
  10. Test end to end in the Sandbox catalog, then go live with a few deals.

Where CoSell fits

CoSell connects Zoho CRM to AWS Partner Central through the Selling API, as it does Salesforce, HubSpot, Microsoft Dynamics 365 and LeadSquared, or its own built-in CRM. It checks each deal against AWS's rules before submitting it, and writes AWS's review status, comments and seller back to the Zoho deal. AWS referrals and leads come back into Zoho as deals and leads. It runs hosted by HabileLabs or in your own AWS account, from USD 10 a month on AWS Marketplace; as of November 2026 the offer is for AWS accounts in India. See CoSell for Zoho CRM and pricing.

Sources

More guides

All guides

Available in AWS Marketplace

Try CoSell free for 30 days

Start the free trial on AWS Marketplace with your AWS account. Your workspace is ready in minutes, and you connect your CRM yourself.