> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwoty.io/llms.txt
> Use this file to discover all available pages before exploring further.
# CRM sync fields
> Reference of the Qwoty fields that can be synchronized with a connected CRM (HubSpot, Salesforce, Pipedrive), beyond each integration's base object mapping.
Beyond the base objects described in each CRM integration page (Customer, Primary contact, Project/Quote, Line items, Product), Qwoty exposes a common set of additional fields that can be mapped to a field on your connected CRM. This reference applies the same way across [HubSpot](/developers/integrations/crm/hubspot), [Salesforce](/developers/integrations/crm/salesforce), and [Pipedrive](/developers/integrations/crm/pipedrive).
Field mapping is configured per-CRM in **Settings → Developers → Integration → \[CRM name]**, the same place described in [CRM mapping](/user-guide/data-model/reference/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
Leaving a field unmapped keeps it local to Qwoty.
## How Qwoty objects map to each CRM
| Qwoty object | HubSpot | Salesforce | Pipedrive |
| --------------- | ------- | ----------- | ------------ |
| Customer | Company | Account | Organization |
| Primary contact | Contact | Contact | Person |
| Project (Quote) | Deal | Opportunity | Deal |
| Product | Product | Product2 | Product |
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
| Field | Description | Typical direction |
| ----------------- | ------------------------------------------------------------------ | ---------------------------- |
| Quote ID | Qwoty's internal identifier for the quote | CRM → Qwoty (reference only) |
| Quote number | Human-readable quote number | Qwoty → CRM |
| Status | Current quote status (draft, sent, accepted, expired, lost, …) | Qwoty → CRM |
| Title | Quote title | Qwoty → CRM |
| Issue date | Date the quote was issued | Qwoty → CRM |
| Expiration date | Date the quote expires | Qwoty → CRM |
| MRR | Monthly recurring revenue generated by the quote | Qwoty → CRM |
| ARR | Annualized recurring revenue generated by the quote | Qwoty → CRM |
| TCV | Total contract value across the full commitment | Qwoty → CRM |
| One-off total | Total of one-time (non-recurring) charges on the quote | Qwoty → CRM |
| First payment due | Amount due on the first payment or installment | Qwoty → CRM |
| Gross margin | Gross margin computed on the quote | Qwoty → CRM |
| Discount rate | Overall discount rate applied to the quote | Qwoty → CRM |
| Number of views | Dealroom engagement: how many times the buyer opened the quote | Qwoty → CRM |
| Last active | Dealroom engagement: last time the buyer interacted with the quote | Qwoty → CRM |
**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
| Field | Description | Typical direction |
| ---------------------- | -------------------------------------------------------- | ----------------- |
| Name | Customer / company name | Bidirectional |
| Tax ID(s) | Tax identification number(s); multiple values are joined | CRM → Qwoty |
| Billing address line 1 | First line of the billing address | Bidirectional |
| Billing address line 2 | Second line of the billing address | Bidirectional |
| Billing city | Billing address city | Bidirectional |
| Billing state | Billing address state or region | Bidirectional |
| Billing postal code | Billing address postal / ZIP code | Bidirectional |
| Billing country | Billing address country (name) | Bidirectional |
| Billing country code | Billing address country (ISO code) | Bidirectional |
## Contact fields
These fields map onto the customer's primary contact (Contact or Person, depending on the CRM — see the table above).
| Field | Description | Typical direction |
| ------------- | ------------------------------------------------------ | ----------------- |
| First name | Contact's first name | Bidirectional |
| Last name | Contact's last name | Bidirectional |
| Email | Contact's email address | Bidirectional |
| Phone | Contact's phone number | Bidirectional |
| Role | Contact's role or job title | CRM → Qwoty |
| ERP ID | External identifier from a connected ERP | CRM → Qwoty |
| Accounting ID | External identifier from a connected accounting system | CRM → Qwoty |
## Product fields
| Field | Description | Typical direction |
| --------------- | ------------------------------------------------------ | ----------------- |
| Product name | Product display name | Qwoty → CRM |
| Reference | Internal product reference | Qwoty → CRM |
| SKU | Stock keeping unit | Qwoty → CRM |
| Description | Product description | Qwoty → CRM |
| Product type | Product category / type | Qwoty → CRM |
| Unit of measure | Unit the product is sold in (e.g. license, hour, unit) | Qwoty → CRM |
| Units per pack | Number of units included per pack, if applicable | Qwoty → CRM |
| ERP ID | External identifier from a connected ERP | Qwoty → CRM |
| Accounting ID | External identifier from a connected accounting system | Qwoty → CRM |
A product's **price**, **quantity**, **tax**, and **line-item discount** on a given quote are always synchronized as part of the line item itself (deal product / opportunity line item, depending on the CRM) — they aren't configured through field mapping.
## 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 a `Custom:` prefix to distinguish them from the fields in this reference.
See [CRM mapping](/user-guide/data-model/reference/crm-mapping) for the full mapping workflow, compatible field types, and how missing values are handled.
## Related
Connect Pipedrive and see how objects are synchronized end to end.
Connect Salesforce and see how objects are synchronized end to end.
Connect HubSpot and see how objects are synchronized end to end.
Where field mapping lives, sync directions, and compatible field types.