Map your pipeline
Settings → Mapping decides which Zoho deals go to AWS, when, and how their fields become an ACE opportunity. Every save creates a new, numbered version, and the mapping check at the top says whether a deal crossing the gate could be submitted right now.
Submission and solutions
- Partner solution IDs (1 to 10, from Partner Central, such as
S-1234567) are attached to every submission. The check lists the solutions in your default account so you can add them with one click. - Default primary needs from AWS are used when a deal doesn't say what it needs from AWS.
Stages and the submission gate
Each Zoho stage maps to an ACE stage (Prospect, Qualified, Technical Validation, Business Validation, Committed, Launched, Closed Lost). One Zoho stage is the submission gate: a deal is sent to AWS when it reaches that stage or a later one.
- Below the gate, a deal is tracked as pending. Nothing is sent.
- Deals that are already Closed Won or Closed Lost when CoSell first sees them are never sent.
- A deal already in AWS keeps syncing when it closes, so AWS learns the outcome.
Which deals go to AWS
Not every deal is a co-sell deal. The deal filter holds rules on Zoho Deals fields: picklists, multi-selects,
checkboxes and text. Only open deals that match are tracked. New workspaces start with Co-sell with AWS is checked,
so a seller opts a deal in by ticking the box. You can add rules such as Cloud_Provider is AWS, and combine them with
all or any.
Preview against Zoho shows the verdict for your most recently changed deals before you save.
Which AWS account gets each deal
With several AWS accounts linked, routing rules pick the account each new deal is created in. Each rule has:
- a name;
- the AWS account;
- conditions on Zoho fields, in the same editor as the deal filter (for example
Region is EMEA); - optionally, that account's own solution IDs.
The first rule that matches wins. A deal that no rule matches goes to the default account. A deal follows the rules on every sync until AWS has it, then it stays in that account. The mapping check warns when a rule points at a missing or unverified account, reads a field Zoho doesn't have, or submits with another account's solutions.
Fields
The field map (advanced) connects Zoho fields to ACE fields. The defaults cover what AWS requires:
| ACE field | Zoho source |
|---|---|
| Opportunity title | Deal name |
| Customer company, website, industry, address, country | The deal's account |
| Customer contact | The deal's contact |
| Target close date | Closing date |
| Expected monthly AWS spend | Amount (in USD, see below) |
| Customer business problem | Description (at least 50 characters, at most 2,000) |
| Next steps | Next step |
| Partner opportunity identifier | The Zoho deal ID |
Target close date, next steps and the business problem also come back from AWS when AWS changes them.
Amounts and currency
ACE takes expected spend per month, in USD only. CoSell reads your Zoho org's currency when Zoho connects:
- If Zoho works in USD, amounts are sent as they are.
- Otherwise, enter the rate 1 USD = … (your currency). CoSell converts Zoho amounts to USD for ACE, and USD spend from AWS referrals back into the deal's Amount.
- Without a rate, deals stop at needs information and say why. AWS's own figure is always kept in
ACE_Expected_Spend(for exampleUSD 12,500 / Monthly).
If CoSell cannot read the currency, enter it by hand under Zoho currency.