DO ONE THING WELL
Map Form Fields to CRM Fields
Listen to this guide
English narration. Duration shown in the player.
Read the narration transcript
Field mapping tells a connector where each answer belongs. Start small: one form, one CRM object, and only the information the workflow needs. A volunteer form might send a person's first name, last name, and email to a contact record.
After the connection has passed its checks, open Mappings and logs for that connection. Choose the source form and a supported destination object. A contact, company, and deal are different objects, even when several of their fields have similar names.
Use the field definitions returned by the CRM. Check the internal field name, data type, and required status. A familiar label does not guarantee a compatible field. Two fields called Status may accept different values or belong to different objects.
Here is a simple planning example. First name maps to the contact's first name, last name to last name, and email address to email. These are illustrative labels. Confirm the actual property names in your connector before saving a mapping.
Review more than the field names. Dropdown values must match values the CRM accepts. Dates and numbers must use a compatible format. Decide what a blank answer should do, and check the connector's behavior before allowing it to clear an existing CRM value.
Choose the supported record action deliberately. Create adds a record. Update changes an existing record. Upsert combines matching with an update or a create. Define the matching key separately from the field mapping, and review any suggested mapping before accepting it.
Validate the mapping, then test delivery with one fictional submission in your test environment. Validation checks configuration; it is not evidence that a record was written. Inspect the destination record, including required fields, blank handling, and any returned record identifier.
Your next step is to review the mapping field by field and confirm the intended record action. Keep a short mapping table with the written guide. Continue with Create, Update and Upsert to understand matching and duplicate prevention.
Watch the narrated slides
Music: A Kind Of Hope by Scott Buckley, licensed under CC BY 4.0. Edited for length, fades and background level.
Decide exactly where each answer belongs and how to handle required values and blanks.
Give each answer a destination
Field mapping tells a connector where each answer belongs. Start small: one form, one CRM object, and only the information the workflow needs. A volunteer form might send a person's first name, last name, and email to a contact record.
- Start with one form
- Choose one CRM object
- Send only the fields you need
Select the form and object
After the connection has passed its checks, open Mappings and logs for that connection. Choose the source form and a supported destination object. A contact, company, and deal are different objects, even when several of their fields have similar names.
- Open the connection’s Mappings & logs
- Choose the source form
- Choose the supported CRM object
Read the actual field definitions
Use the field definitions returned by the CRM. Check the internal field name, data type, and required status. A familiar label does not guarantee a compatible field. Two fields called Status may accept different values or belong to different objects.
- Confirm the internal field name
- Check the data type
- Identify required fields
Example: a volunteer contact
Here is a simple planning example. First name maps to the contact's first name, last name to last name, and email address to email. These are illustrative labels. Confirm the actual property names in your connector before saving a mapping.
- First name → Contact first name
- Last name → Contact last name
- Email address → Contact email
Check values and blank answers
Review more than the field names. Dropdown values must match values the CRM accepts. Dates and numbers must use a compatible format. Decide what a blank answer should do, and check the connector's behavior before allowing it to clear an existing CRM value.
- Use accepted dropdown values
- Keep dates and numbers compatible
- Decide whether a blank may overwrite
Choose the record action
Choose the supported record action deliberately. Create adds a record. Update changes an existing record. Upsert combines matching with an update or a create. Define the matching key separately from the field mapping, and review any suggested mapping before accepting it.
- Create → add a new record
- Update → change a known record
- Upsert → match, then update or create
Validate, then test delivery
Validate the mapping, then test delivery with one fictional submission in your test environment. Validation checks configuration; it is not evidence that a record was written. Inspect the destination record, including required fields, blank handling, and any returned record identifier.
- Validate the mapping
- Use one fictional submission
- Inspect the destination record
Your next step
Your next step is to review the mapping field by field and confirm the intended record action. Keep a short mapping table with the written guide. Continue with Create, Update and Upsert to understand matching and duplicate prevention.
- Every source field has a purpose
- Every destination field is correct
- The write action is intentional
Examples illustrate decisions and do not report a completed CRM transaction.