Map your pipeline
Settings → Rules decides which deals in your CRM go to AWS, through which account and with what; Settings → Mapping decides when, and how their fields become an ACE opportunity. Every save on either creates a new, numbered version of the mapping, and the mapping check at the top of both says whether a deal crossing the gate could be submitted right now. While something needs fixing the check stays open; a mapping that is ready with nothing to report folds to one line (the stage that sends deals to AWS and the account they go through), and Show details opens it.
The mapping is long, so On this page, beside it, jumps to each part and marks the one you are reading. Save
mapping stays at the bottom of the window and says whether anything is unsaved; Discard changes goes back to the
version in use. Deal owners and versions sit below it and save on their own. Save mapping turns on once you
change something. Under Versions, View says what a version does and how it differs from the version in use;
the JSON as saved is folded below that (the "version" numbers inside it are the format of the field and stage maps,
not the mapping's version).
Stages and the submission gate
Each stage in your CRM maps to an ACE stage (Prospect, Qualified, Technical Validation, Business Validation, Committed, Launched, Closed Lost). One of your stages 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.
Reason for loss, under the stages, names the field your CRM keeps a lost deal's reason in (Zoho CRM orgs made
since 2024 call it Reason_For_Loss__s) and the AWS reason each of its values means. A reason left as Other reaches
AWS as "Other". A lost deal with no reason, in a stage whose name says it was lost to competition, is sent as Lost to
Competitor - Other. The mapping check says when the field is missing and names the one your CRM has.
Rules
Settings → Rules decides what happens to each deal, in one ordered list. The first rule a deal matches decides; a deal no rule matches follows the default rule, Everything else, which is always last. Each rule is a row in the list: its place, its name and conditions, where its deals go, its solutions and defaults, what happens before AWS, and whether AWS may change the deal. Edit opens the rule in its own editor; the arrows beside its number move it up or down; Remove asks first. Every change is saved at once as a new mapping version, so an earlier one can be restored under Mapping → Versions. A workspace holds at most 20 rules.
In a rule's editor:
| Part | What it decides |
|---|---|
| Name | What the rule is for ("EMEA deals"), shown in the list and the mapping check |
| Which deals | Conditions on your CRM's deal fields: picklists, multi-selects, checkboxes and text, matching all or any. No conditions means every deal |
| What happens to them | Send to AWS or Don't send |
| AWS account | The linked account the deals are created in; the default account unless you choose another |
| Before it goes to AWS | As the workspace does (Settings → General), Send at the gate stage, or Hold for review |
| Changes from AWS | AWS may update the deal (two-way), or AWS may not change the deal's fields (one-way) |
| Solutions and defaults | Solution IDs from that account's Partner Central, what these deals usually need from AWS, and a delivery model, sales activities or a customer use case. Whatever is left empty is the default rule's |
Nothing in the editor is saved until Save rule; Cancel, Escape or the close button leave the rule as it was. A rule turned to Don't send keeps only its name and conditions.
- New workspaces start with one rule, Marked for co-sell (Co-sell with AWS is checked → send), and everything else not sent: a seller opts a deal in by ticking the box.
- Two-way lets AWS's changes reach the deal's own fields: close date, next steps, business problem and (for AWS
referrals) spend, and the deal's stage. A stage comes over when AWS moved the opportunity and nobody moved the
deal in your CRM since: forward only (AWS keeps a new opportunity at Prospect while your deal is further on, and
that never pulls the deal back), or closed as lost with AWS's reason in your own word for it (your word for
"Other" when your reason field has none). A deal your CRM already closed is left alone, and so is one AWS turned
down: a rejected co-sell is not a lost customer. A stage your stage map has no CRM stage for (Launched, where your
won stage maps to Committed) only reaches the
ACE_fields. - One-way keeps the CRM the only one that changes the deal. AWS's status (review, stage, seller, sync) still
reaches the
ACE_fields, but AWS's close date, next steps, business problem, spend and stage never overwrite the deal's own fields, and the CRM's values go to AWS whenever you change them. - Hold for review sends each of the rule's deals to the review queue first, even when the workspace sends at the gate; Send at the gate stage sends them on their own, even when the workspace reviews every deal.
- After a deal is sent, it stays in its AWS account and keeps the solutions it was submitted with. Review and changes from AWS follow whichever rule the deal matches now.
- Closed deals are never sent, whatever the rules say. A person's approval in the review queue sends a deal no rule sends.
Preview against your CRM, under a rule's conditions, shows which recent deals those conditions take; Close preview puts it away, and changing a condition closes it too. Preview on recent deals, above the list, runs the saved rules in a window you close when done: how many deals each rule takes, and where each of the most recently changed deals would go. The mapping check, above the list, warns when a rule reads a field your CRM doesn't have, points at a missing or unverified account, submits through another account with the default account's solutions, or has no conditions while rules follow it (it takes every deal, so they never apply).
A mapping saved before rules (a deal filter and routing rules) reads as the rules it amounts to, decides exactly as it did, and becomes rules with the first change. Where a routing rule and the filter could not be one set of conditions, the rule keeps the filter as a second group, And also, kept from the mapping before rules.
The default rule
Edit on Everything else sets:
- Deals no rule takes: Don't send, or Send through the default account, as the workspace does.
- Partner solution IDs (1 to 10, from Partner Central, such as
S-1234567), or what you offer when you have no registered solution. The solutions in your default account are offered for one click. - What you usually need from AWS, used when a deal doesn't say what it needs from AWS. Tick as many as apply.
- When an opportunity has none of its own, send AWS: a default delivery model, sales activities and customer use case. AWS refuses a submission without these. The defaults fill a deal that has nothing for them in your CRM. A deal's own values always win. Once AWS has taken a deal's submission, the defaults no longer apply to it, so nothing set in Partner Central is overwritten. Only AWS's own values can be chosen.
Every rule that sets no solutions, needs or defaults of its own takes these.
Import rules
Rules work the other way too. Import rules: which AWS opportunities come into your CRM, below the rules, decide which opportunities made or changed in AWS Partner Central come into your CRM on their own when no deal carries them yet. The first import rule an opportunity matches decides: Bring into your CRM, or Don't import. Everything else covers the rest and imports them unless you change it.
A condition reads the opportunity's own AWS fields: origin (AWS Referral or Partner Referral), title, customer name, customer country code, industry, AWS stage, review status, opportunity type, AWS involvement, marketing campaign and source, use case, delivery models, primary needs, and the partner owner's email. For example, CampaignName contains Aarohan → Don't import keeps a campaign's opportunities out of your CRM.
- They apply to opportunities that come in on their own (Settings → General → Bring Partner Central opportunities into your CRM) and to Import all of them on the Opportunities page. With automatic import off, the card says so.
- An opportunity you import from the Opportunities page by hand comes in regardless, as a deal you send by hand goes to AWS regardless of the rules.
- Only open opportunities whose close date has not passed come in on their own, whatever the rules say.
- AWS referrals are not affected: you accept or decline those on the AWS referrals page.
Deal owners
The Deal owners card sets who owns the deals CoSell creates in your CRM from AWS referrals and imports, in this order:
- the CRM user the opportunity is assigned to in Partner Central (its partner account manager, else its owner), matched by email;
- the owner you chose for the AWS account the opportunity came through;
- the default owner;
- if you set none of these, your CRM decides, usually giving the deal to the user CoSell connects as.
If your CRM refuses the chosen owner (an inactive user, for example), CoSell still creates the deal, without that owner.
Keep owners the same in your CRM and AWS also mirrors later changes:
- CRM → AWS. When a deal gets a new owner in your CRM, CoSell assigns the opportunity to them in Partner Central (as its partner account manager) once the deal has synced. The person must be a Partner Central user in your account. If AWS won't reassign an opportunity during its review, CoSell tries again once the review allows it.
- AWS → CRM. When an opportunity is assigned to someone else in Partner Central, they become the deal's owner in your CRM if they are a user there. This covers production opportunities only: Sandbox owners are placeholders.
Owners that already differ when you turn this on are left as they are; only later changes are copied. If both systems change the owner at once, or an owner keeps changing back and forth, CoSell copies nothing and adds an owner conflict to Sync errors for you to settle. Owner problems never stop a deal from syncing.
Fields
The field map (advanced) connects your CRM's fields to ACE fields. The defaults cover what AWS requires:
| ACE field | Source in your CRM |
|---|---|
| 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 deal's ID in your CRM |
Target close date, next steps and the business problem also come back from AWS when AWS changes them.
The AWS fields in your CRM
AWS asks about things a CRM seldom has a field for: the customer use case, delivery models, sales activities, what you
need from AWS, the competitor and the customer's AWS account. The default mapping reads them from AWS_Use_Case,
AWS_Delivery_Model, AWS_Sales_Activities, AWS_Primary_Needs, Competitor and Customer_AWS_Account_ID. On
Zoho CRM, Re-activate under Settings → CRM creates the ones your mapping reads that the org lacks, as picklists of
AWS's own values, so what a seller picks needs no translation. AWS Expected Monthly Spend (a currency field) and
AWS Competitor are created too when the mapping reads them. On other CRMs an admin adds them.
Until sellers fill them, the rules and the default rule give each deal its use case, delivery model, sales activities and needs. A deal made from an AWS opportunity shows AWS's values in these fields.
The mapping check names every field the mapping reads that your CRM does not have: an error when AWS requires it, a warning otherwise.
A picklist value is matched to its translation without regard to case, "&" for "and" or punctuation ("HealthCare", "Software & Internet"). An industry that has no AWS equivalent is sent as Other with your CRM's own value beside it.
A deal whose only need from AWS is Do Not Need Support from AWS Sales Rep is submitted for AWS's visibility only: AWS refuses a co-sell submission with that need. Asking for no support together with co-sell needs keeps the co-sell needs.
Field names in each CRM
The field map, deal filters and routing rules use CoSell's names for fields, which are the same whichever CRM you connect (they match Zoho CRM's). CoSell translates each name to your CRM's own, so one mapping works everywhere. Where the two differ, the Mapping page and the review form also show your CRM's own name, which is the one to look for in its setup:
| CoSell's name | Zoho CRM | Salesforce | HubSpot | Dynamics 365 Sales | LeadSquared |
|---|---|---|---|---|---|
Deal_Name |
Deal_Name |
Name |
dealname |
name |
as your opportunity type names it (mx_Custom_1, …) |
Amount |
Amount |
Amount |
amount |
estimatedvalue |
as your opportunity type names it |
Closing_Date |
Closing_Date |
CloseDate |
closedate |
estimatedclosedate |
as your opportunity type names it |
ACE_Opportunity_ID |
ACE_Opportunity_ID |
ACE_Opportunity_ID__c |
ace_opportunity_id |
new_aceopportunityid |
the mx_Custom_N field you added for it |
Custom fields follow each CRM's own rule: Salesforce adds __c, HubSpot uses lower case, Dynamics 365 puts your
publisher prefix in front (new_ unless the connection names another), and LeadSquared numbers them (mx_Custom_N).
A field of your own, such as Cloud_Provider__c in Salesforce, can be used under the name your CRM gives it.
Write-back fields
CoSell writes AWS's view of each deal into ACE_ fields on the deal in your CRM: the opportunity ID, ACE stage, AWS
review status and comments, the AWS seller, sync status and so on. The card lists each one under your CRM's own name.
- Switch a field off under What CoSell writes back when you don't need it. A common reason is the CRM refusing a new field because there is no room left (Zoho answers Field limit reached on some editions). CoSell then stops writing that field and no longer creates it.
- After saving, activate your CRM again under Settings → CRM to clear a warning about the field.
- The field itself stays in your CRM. Delete it there if you want its slot back.
- ACE Opportunity ID cannot be switched off: CoSell finds each deal by it.
Amounts and currency
ACE takes expected spend per month, in USD only, and AWS referrals arrive in USD. When your CRM connects, CoSell reads the currency it works in and, if it keeps several, the ones switched on and their rates. Zoho CRM, Salesforce, HubSpot and Dynamics 365 Sales report them, and CoSell reads them again every day; LeadSquared does not, so a LeadSquared workspace enters its currency by hand under Currency in (your CRM). Any ISO 4217 code works: INR, EUR, GBP, AED, SGD, JPY and the rest.
Amounts in any currency other than USD are converted both ways: from your CRM to USD for ACE, and from USD spend in AWS referrals into the deal's amount, rounded the way the currency is written (whole yen, three decimals for dinars). Exchange rates to USD says where the rates come from:
- Daily reference rates (the default). The European Central Bank's reference rates, published every working day, cover about 30 currencies (EUR, GBP, INR, JPY, AUD, SGD, CAD, CHF, ZAR, BRL and more). Currencies fixed to the US dollar (AED, SAR, QAR, OMR, BHD, JOD and several in the Caribbean) take their official peg.
- Rates in (your CRM). The rates kept in your CRM's own currency settings, so amounts convert exactly as your CRM converts them. Offered when your CRM keeps several currencies; it needs US Dollar among them.
- Rates I set. Only the rates you type. They stay as they are until you change them.
The table lists your CRM's currency and every other one it has switched on, each with its rate, where the rate came
from and an example. A currency the chosen source leaves out (KWD in the daily rates, say) shows a field: type
1 USD = … for it. Without a rate, deals in that currency stop at needs information and say why, and the
mapping check names each currency that has none. AWS's own figure is always kept in the ACE Expected Spend field
(ACE_Expected_Spend, or ACE_Expected_Spend__c in Salesforce; see
Field names in each CRM), for example USD 12,500 / Monthly.
A mapping saved before these choices existed keeps its single rate as its currency's own, under Rates I set. A workspace that keeps its deals in CoSell CRM only has nothing to set: CoSell CRM keeps amounts in USD, as AWS does.