Field mapping defines how turgo's canonical schema aligns with your CRM fields. Standard fields pre-map; custom fields need manual mapping. Get title, industry, and lifecycle-stage mappings right — they drive targeting and reporting.
The mapping screen
Integrations → [CRM] → Field Mapping. Left column: turgo canonical fields. Right: your CRM fields. Pre-mapped standards shown in grey; unmapped customs flagged.
Mapping principles
Map to the CRM field your team actually maintains (orgs often have three "industry" fields — pick the live one). Skip fields nobody uses rather than mapping noise. Direction per field: some fields should flow one-way only (e.g. turgo enrichment → CRM, never back).
Taxonomy translation
Picklist fields (industry, lifecycle stage) need value mapping, not just field mapping — turgo's taxonomy values translate to your picklist values via the translation table on the same screen.
Change management
Mappings are versioned. When your CRM admin adds or renames fields, the sync flags unmapped/broken fields rather than silently dropping data. Review flags monthly.
