Data mappings

A data mapping defines which Nexcal field corresponds to which field in the connected system. Mappings concern the integrations of the Power and Enterprise plans.

Last reviewed: 2026-07-22

Data mappings

A data mapping defines which field in Nexcal corresponds to which field in the connected system. This ensures that leads and conversation results arrive in the right place. Mappings are the basis of every CRM integration and every programmatic lead handover.

Availability

Data mappings concern the integrations of the Power and Enterprise plans, in particular HubSpot, Salesforce, the Form API and public lead intake. In Starter and Pro, these integrations are not available. For an overview, see plans and feature scope.

What mappings are needed for

  • Assigning contact fields when importing leads.
  • Assigning result fields when writing conversation results back.
  • Avoiding records that end up in the wrong field.

Standardized or individual

  • Power: standardized payloads and defined mappings with set limits.
  • Enterprise: custom mappings for differing data structures. See enterprise system connections.

Preparing a clean mapping

  1. Clarify which fields you want to hand over from Nexcal.
  2. Determine the matching target fields in the connected system.
  3. After setup, verify with a few records that the values arrive correctly.

Hinweis: An incomplete mapping does not necessarily produce an error message. Values may then arrive in the wrong field or not at all. For that reason, check the handover with spot samples.

Common mapping mistakes

  • A target field was not assigned, so values do not arrive.
  • Two different Nexcal fields accidentally point to the same target field.
  • The target field expects a different format than the value handed over.

After every change to the mapping, check again with a few records that the values arrive complete and in the correct field.

Back to Help Center