Field mapping is configured per-CRM in Settings → Developers → Integration → [CRM name], the same place described in CRM mapping. Each field below can be mapped with one of three directions:
- Bidirectional ↔ — changes in either system propagate to the other
- CRM → Qwoty — the CRM is the source of truth
- Qwoty → CRM — Qwoty is the source of truth
How Qwoty objects map to each CRM
The tables below list the fields available for mapping on each object, using Qwoty’s naming. The equivalent CRM-side field is whatever you select in the mapping dropdown for that CRM.
Quote (Project) fields
Status driving the deal/opportunity stage or pipeline step is handled separately from field mapping — see the “stage automation” section on each CRM’s integration page.
Customer fields
Contact fields
These fields map onto the customer’s primary contact (Contact or Person, depending on the CRM — see the table above).Product fields
Custom fields
Any custom field you’ve created on the Quote, Customer, Contact, or Product object in Qwoty can also be mapped to a CRM field, exactly like the fields above. In the mapping screen, custom fields are listed with aCustom: prefix to distinguish them from the fields in this reference.
See CRM mapping for the full mapping workflow, compatible field types, and how missing values are handled.
Related
Pipedrive
Connect Pipedrive and see how objects are synchronized end to end.
Salesforce
Connect Salesforce and see how objects are synchronized end to end.
HubSpot
Connect HubSpot and see how objects are synchronized end to end.
CRM mapping
Where field mapping lives, sync directions, and compatible field types.

