> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/field-mapping.md). # Field mapping Field mapping decides where each Mobly field lands in your CRM. You configure it on the **Mapping** tab inside any connected CRM integration (**Integrations → \[your CRM] → Mapping**). ## What's on the Mapping tab Per-object sections — typically **Persona** (your CRM's Lead or Contact equivalent) and **Company** (your CRM's Account, Company, or Organization equivalent). Some CRMs surface additional objects (custom objects, Event objects, etc.) as their own sections when relevant. Each section is a table of rows: * **Mobly Field** on the left — the field as Mobly knows it (e.g., First Name, Email, Phone Number, Job Title), with a type badge: **TEXT**, **EMAIL**, **URL**, etc. * **CRM Field** on the right — a dropdown to pick the CRM property/field where this Mobly value should land. Leave blank to skip a field. Click the **×** to clear an existing mapping. Two actions in the top right of each section: * **Set Defaults** — auto-populates Mobly's recommended mappings for that object. Good starting point. You can tweak individual rows after. * **Clear object mappings** — removes every mapping for that object. Useful if you're starting over. ## How saving works There's no Save button. Each field change saves immediately when you pick a value (or clear one). If you switch tabs or close the window mid-edit, your last selection on each row is already saved. This is intentional — earlier versions of the Mobly integration could lose mappings when you switched tabs without saving. Auto-save fixes that. ## Setting up mappings for a new integration Quickest path to a working setup: 1. Go to **Integrations → \[your CRM] → Mapping** 2. For each object section (Persona, Company, etc.), click **Set Defaults** 3. Review the auto-populated rows, change anything that doesn't fit your CRM's schema 4. Move on to the [Qualifiers](/help-center/integrations/crm/qualifiers.md) and [Campaigns](/help-center/integrations/crm/campaign-mapping.md) tabs If your CRM has unusual field naming conventions or required custom fields, defaults won't cover them — you'll need to fill those in manually. ## Field types — what to expect The type badge on each Mobly field tells you what kind of CRM field it expects to land in: * **TEXT** — single-line text. Most short fields. * **EMAIL** — email-formatted string. Map to a CRM Email-type field, not a generic text field, so the CRM validates correctly. * **URL** — a full URL (with `https://`). Map to a CRM URL-type field. * **PHONE** — phone-formatted. Map to a CRM Phone-type field. Mismatches between Mobly's type and the CRM's field type usually surface as `DATA_FORMAT_VALIDATION` errors in [Reconciliation](/help-center/integrations/crm/reconciliation.md) once leads start syncing. ## Common gotchas * **Mapping a Mobly URL field to a non-URL CRM field** — the CRM may accept it, but a properly-typed CRM URL field gives you better data quality and validation. * **Mapping email-style values to a Notes-type CRM field** — works, but you lose any CRM-side validation, click-to-email behavior, etc. * **Skipping the Persona section entirely** — Mobly will sync Companies but no Lead/Contact records, which is rarely what you want. * **Changing field types in your CRM after mapping** — if you change a field from Text to Email in HubSpot/Salesforce/etc., revisit the Mobly mapping to confirm the type expectations still match. ## Vendor-specific notes Each CRM has its own per-object structure and field types. See your CRM's setup guide for vendor-specific field naming and configuration: * [HubSpot](/help-center/integrations/crm/hubspot/setup-guide.md) * [Salesforce](/help-center/integrations/crm/salesforce/setup-guide.md) * [Pipedrive](/help-center/integrations/crm/pipedrive.md) * [Zoho](/help-center/integrations/crm/zoho.md) For Marketing Automation field mapping, see [Field mapping (MA)](/help-center/integrations/marketing-automation/field-mapping.md). ## Related articles * [Qualifiers](/help-center/integrations/crm/qualifiers.md) — for qualifier mapping (separate from field mapping) * [Mapping campaign fields](/help-center/integrations/crm/campaign-mapping.md) — for per-event campaign sync * [How data flows from Mobly to your CRM](/help-center/integrations/crm/how-data-flows.md) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) — see field-level errors --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/field-mapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.