> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# CRM Field Mapping

> Connect form fields to your CRM so accepted submissions create and update the right HubSpot or Salesforce records automatically.

> CRM Field Mapping wires your forms to your CRM: each field maps to a property, and an accepted submission creates or updates the right records in HubSpot or Salesforce, with no manual re-keying.

## What it does

CRM Field Mapping connects a form's fields to your CRM's objects and properties. When you map a
field, the value a partner submits flows into the matching CRM property, and CRM object
automations decide whether a submission creates a new record, updates an existing one, and how it
attributes that record to the submitting partner. Forms can also prefill from a known CRM record,
so partners confirm rather than retype data you already have.

Because the CRM stays the source of truth, mapped submissions keep your data clean and current
without anyone copying fields by hand. Partner-submitted information lands as structured CRM
records your sales team already trusts, with attribution intact.

## The problem it solves

Re-keying partner submissions into the CRM is slow and error-prone:

* **Submissions are retyped into the CRM** → Mapped fields write straight to CRM properties.
* **Records get duplicated or stale** → Automations control create-versus-update and write behavior.
* **Partner attribution gets lost** → Submissions attribute records to the right partner.
* **Partners retype data you already have** → Prefill known CRM data so they only confirm.

## From problem to solution

CRM Field Mapping makes forms a clean pipe into your CRM. Map fields to properties, set how
submissions create or update records, and keep partner attribution intact. Partner input becomes
trustworthy CRM data automatically, with the CRM as the single source of truth.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  field["Form field"] --> map["Mapped to CRM property"]
  map --> submit["Partner submits"]
  submit --> record["Creates or updates CRM record"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Sync submissions to the CRM" icon="circle-check">
    Write mapped fields straight to CRM properties.
  </Card>

  <Card title="Control create vs update" icon="circle-check">
    Decide when a submission makes or updates a record.
  </Card>

  <Card title="Keep attribution intact" icon="circle-check">
    Tie submitted records to the right partner.
  </Card>

  <Card title="Prefill from the CRM" icon="circle-check">
    Start forms with data you already have.
  </Card>
</CardGroup>

## Impact

* **CRM-native** - Submissions become clean CRM records automatically.
* **Low total cost of ownership** - Partner ops maps fields with no engineering.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Operations" icon="user">
    Maps fields and configures CRM automations.
  </Card>

  <Card title="RevOps" icon="user">
    Ensures submission data lands cleanly and is attributed.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Form Builder" icon="table-list" href="/features/forms/form-builder">
    Mapping is set on each form.
  </Card>

  <Card title="CRM" icon="plug" href="/features/integrations/crm">
    Writes back to mapped CRM fields.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>