Map fields before a CRM import
Choose which normalized connector field fills each CRM field, with simple text rules. The mapping is versioned, and a real import only runs with the mapping its preview used.
Steps
- Open Connections, find the connected CRM and open Import field mapping. Owners and administrators can edit; everyone with access can read it.
- For each CRM field choose a source field and a text rule: keep original, trim spaces, lowercase or uppercase. Only the fields this connector normalizes are listed; this is not discovery of every custom field in the source system.
- Save. The version goes up by one. If someone else saved first you are asked to reload, so two people never overwrite each other silently.
- Run a fresh preview. Preview stays disabled while a change is unsaved, and the Import button only unlocks for a preview that ran with the current mapping version.
- While an import is active or paused the mapping is locked. Finish or cancel the run first. Replacing the connection token keeps the saved mapping, but start a new preview.
- Identity, relations, consent and amounts are never remapped, and existing CRM values are still protected: an import only fills empty fields.
- Brand My Inbox MCP: crm_import_mapping (leads:read) reads the profile; crm_save_import_mapping (owner or admin, leads:write) saves it with expected_version. Pass expected_mapping_version to crm_start_import so a mapping saved after the preview returns a conflict instead of importing.
Questions
- Does a mapping keep two systems in sync?
- No. It applies to the initial import from that connection. Continuous or two-way sync is not enabled by a mapping.
Updated 2026-10-30 · llms-full.txt