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).
For a full list of every Mobly field, what it holds, and where the data comes from, see the Mobly fields reference.
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:
Go to Integrations → [your CRM] → Mapping
For each object section (Persona, Company, etc.), click Set Defaults
Review the auto-populated rows, change anything that doesn't fit your CRM's schema
Move on to the Qualifiers and Campaigns 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 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:
For Marketing Automation field mapping, see Field mapping (MA).
Choosing what Mobly overwrites
Once fields are mapped, you can decide for each one whether Mobly should overwrite what's already in your CRM or leave existing values alone. Set the gear icon on any mapped field row to configure it — see Write behavior for the details.
Related articles
Write behavior — decide per-field whether Mobly overwrites or preserves the CRM value
Qualifiers — for qualifier mapping (separate from field mapping)
Mapping campaign fields — for per-event campaign sync
Reconciliation — see field-level errors
Last updated
Was this helpful?