Field mapping
Field mapping is the configuration that tells a system which column or CRM property holds which piece of data, so values from a list or a customer’s CRM land in the right place and mean the same thing.
Where does field mapping happen?
- At list import: you match the organizer’s column names to known fields such as first name, company, title, and email.
- At CRM connection: you map your own properties and picklist values once. Your mapping settles which value marks a customer, which field names the owner, and which flag means do not contact.
Why does it matter?
Most companies customize their CRM. A company-stage field, 3 separate owner fields, a picklist value your CRM admin added last quarter: each one shapes how account matching classifies an account. A wrong mapping misclassifies without warning, and a known customer shows up as net-new on your pre-show list.
Map once, and have your CRM admin confirm the result. Your mapping choices then become rules your team can inspect and correct.
Where do you find it in FieldXM?
You import lists with field mapping, as the lists and enrichment page shows.
Account labels come from your real CRM fields, which you map once at onboarding. If a value is present but unmapped, FieldXM sets the account aside in Review and shows you the reason. Account review covers how that works.
Related terms
- List importA list import is the step that loads an attendee or lead file into a working system, mapping its columns to known fields and matching every row to a contact and an account before the team works it.
- Account labelAn account label is a single tag stating an account's current standing with the selling team, such as net-new, in an open deal, or excluded, derived from CRM data so each account gets the right owner and play.
- Account reviewAccount review is the holding state for accounts a system cannot place with confidence, such as one carrying a CRM value the team hasn't mapped: it sets the account aside with its reason until a person resolves it.
- Account matchingAccount matching is the step that attaches each person on a list to the company account they belong to, usually by email domain, and finds that account in the CRM so every contact inherits its owner and history.
- SuppressionSuppression is a standing rule that removes a contact from outreach; a do-not-contact request, an unsubscribe, a bounce, a regional rule, or a cooldown sets it, and it outranks every other signal about that contact.
See it in FieldXM
- Lists and enrichmentEnrich any list with FieldXM’s built-in waterfall of the best enrichment providers combined with its own powerful algorithm. It fills in domains, emails, and titles.
Browse
- The full glossarySee every term, A to Z.