Convert to deal
What this page is — the rules that turn a qualifying lead into a deal with a value, and the field mapping that populates it.
What it is for — getting from an enquiry to a forecastable opportunity without retyping anything.
The problem it solves — this is the point where a CRM starts producing a pipeline figure rather than a list of names. It is also where three fields get silently defaulted or left blank — currency, close date and stage — each of which quietly distorts what the deals board then tells you.
Route: /org/marketing/leads/settings?tab=rules&rule=convert-deal
Permission: Manage Conversion Rules for Lead to Contact or Deal
1. What conversion produces
Converting to a deal produces two records, not one.
The contact is created first, then the deal is created linked to that contact. A deal without a contact is possible when created by hand, but conversion always produces the pair.
2. Field mapping
| Deal field | Source | Fallback if unset |
|---|---|---|
| Title | The rule's mapping | Deal for {company_name}, or Deal for {full_name} if there is no company |
| Amount | The lead's deal_value, or the rule | 0 |
| Currency | The rule | USD |
| Pipeline | The rule | None — the deal has no pipeline |
| Stage | The rule | None |
| Owner | The rule | The lead's owner |
| Contact | Created by the same conversion | — |
| Link back to the lead | Set automatically | — |
If the rule does not set a currency and the lead has none, the deal is created in USD. On a tenant operating in another currency this silently misstates the pipeline value, and the deals board shows a mix of currencies with no total that means anything.
Set the currency explicitly on every deal conversion rule.
Neither is defaulted. Map both, or the deal exists with no board position — the same failure mode as a lead with no status.
3. Fields conversion does NOT set
| Not set | Consequence | Set it |
|---|---|---|
| Expected close date | The deal has no timeline and is missing from date-based reporting | On the deal record |
| Priority | Defaults low or blank | On the deal record |
| Description | Empty | On the deal record |
These are not part of the conversion request at all, so even a fully mapped rule leaves them blank.
4. The Run action
As with contact conversion, Run applies the rules retroactively to every currently-matching lead, creating a contact and a deal for each.
There is no dry run and no summary. A broad rule run against a mature project can create hundreds of deals, each with a contact, and each contributing to your pipeline value. Narrow the conditions and test on a handful of leads first.
5. The admin contract
| Needs | Or |
|---|---|
| A deal pipeline with stages | Deals are created with no board position |
| Currency set on the rule | Deals default to USD. Section 2 |
| Manage Conversion Rules for Lead to Contact or Deal | Rules render and every save fails |
| A converted status to trigger on | Rules never fire automatically |
6. Downstream
| The new deal reaches | As |
|---|---|
| The deals board | A card in its stage |
| The deal record | Where close date and priority get set |
| Pipeline Health | A funnel entry |
| The lead | A back-link, and the lead marked converted |
7. Don't confuse this with…
| This | Not this |
|---|---|
| A lead's status | The new deal's stage |
| A lead pipeline | A deal pipeline |
| The rule's mapping | The Convert dialog on the record, which asks for the same fields interactively |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| New deals are in USD | No currency on the rule. Section 2 |
| A new deal is on no board | No pipeline or stage mapped. Section 2 |
| Deals have no close date | Conversion does not set one. Section 3 |
| Run created hundreds of deals | Conditions too broad. Section 4 |
Deal title reads Deal for … | No title mapped — that is the fallback. Section 2 |