Mapping CRM fields to bont fields

Tell bont which CRM field stores what — industry, company size, region, source, revenue group — so scoring, forecasting and segmentation pull the right values.

Different CRMs (and different orgs within the same CRM) name their fields differently. bont's scoring, forecasting and segmentation features expect a consistent shape, so the field-mapping page lets you tell bont "this CRM field is what I mean by Industry, this one is Company Size," and so on. Mapping is per-app and most consequential in funky bont and pure bont — both of which read this metadata for downstream models.

Step 1 · Open the field-mapping page

Switch to funky bont (or pure bont), then open Settings → Integrations → CRM. With a CRM already connected, scroll past the connected-provider card to the Field Mappings section.

Step 2 · Map the company-level fields

The Company Level block lists the bont-native fields that downstream features expect:

Industry — pick the CRM field that stores company industry (HubSpot's industry, a Salesforce custom field, etc.).
Company Size — number of employees. Numeric or text-bucket fields both work; bont normalises text values into its size bands automatically.
Region — geographic segment (continent, country group, etc.). Used for pipeline cohorts.
Source — original acquisition source (referral, inbound, partner, etc.).

Each dropdown shows the available CRM fields filtered by compatible type. Saving is automatic; there's no separate Save button.

Step 3 · Map the deal-level fields

Below Company Level, the Deal Level block currently maps a single field:

Revenue Group — the bucket bont uses when grouping deals by deal-size band on Insights and Forecasting views. Pick the CRM field most directly tied to deal value (e.g. annual_recurring_revenue, amount, a custom band).

What changes when you remap

Remapping a field doesn't move underlying CRM data; it just changes which CRM column bont reads. Reports and Insights pick up the new mapping on the next refresh (usually within a couple of minutes). Historical events keep the value they had at the time of capture — so cohort views built before a remap may look different from after.

What about pure bont and pitch bont?

pure bont has the same Field Mappings page at pure bont → Settings → Integrations → CRM. Map there too if pure bont's scoring and Data Health features matter for your workflow. pitch bont doesn't expose field mapping directly — it inherits from the connected CRM and the upstream pure bont mapping.

Troubleshooting

My CRM field isn't in the dropdown

Three possibilities: the field is a different data type than the mapping expects (try a numeric field instead of text or vice versa), the field hasn't synced yet (give it a few minutes after the initial CRM connection), or the field is access-restricted on the CRM side (bont's OAuth scope can't see it).

Scoring or forecasting numbers look wrong after I remapped

Reports rebuild lazily. Force a refresh by reloading the dashboard; if numbers still look off after a couple of minutes, the underlying CRM field may have empty values for many records.

I want to undo a mapping

Pick the blank option in the dropdown. bont treats unmapped fields as "skip" — features that need the value fall back to defaults.