Skip to main content
This is the complete list of BenefitFlow fields you can map to your CRM. Use it to plan your mapping table before you build it in the app, so you can search the fields here instead of scrolling the dropdowns. You configure mappings in Integration Settings → Field Mappings. For how mapping, matching, and overwrite behavior actually work, see the CRM Integrations: Overview Guide. This page is the reference, not the how-to.

How the fields are organized

BenefitFlow maps to three object types in your CRM. Each has its own field list:
Leads: In Salesforce and Microsoft Dynamics, Leads use the same field list as Contacts. HubSpot has no Lead object, so all people sync as Contacts.
The Label column is exactly what you see in the app. The BenefitFlow field name is the underlying data field, useful when you are matching against a bulk export or SFTP file. The Example column shows a sample value so you can see the shape of the data. Fields marked (Broker Only) or (Employer Only) only carry data for that record type.

Contact fields

For syncing Broker Contacts and Employer Contacts. The example below is a broker contact. It is a fictional person, so the name, email, and phone values are illustrative only.

Account fields

For syncing Broker and Employer records (the top-level company). The example below is an employer, Trader Joe’s.
Benefits-specific fields (Form 5500 details, plan and policy data, premiums, and P&C fields) populate only for employers that have the underlying filing data on record. Employers without a filing on file will show these fields as empty.
Broker records use this same table, but only the general company fields carry data (Company Name, Company Website, Company ID, address, Company LinkedIn URL, Record Type). The employer and benefits fields stay empty. Example broker: Aon · aon.com · Company ID 1358b9d1-eca4-5a31-a6f8-cf44ad89fa3a · Chicago, IL · Record Type Broker.

Child Account fields

For syncing Broker office locations (branches under a broker). The example below is the Aon Los Angeles office.
Allow Overwrite is per-field. For any mapped field, admins can toggle Allow Overwrite on or off. When it is off, BenefitFlow only writes to the field if the current value in your CRM is empty. When it is on, BenefitFlow overwrites whatever is there. See the Overview Guide for details.

CRM Integrations: Overview Guide

How mapping, matching, and duplicate prevention work.

Connecting Your CRM (Admin Setup)

Connect your CRM and build your first mapping table.

CRM Integrations: Association Architecture

How BenefitFlow links brokers, offices, employers, and contacts.
Last modified on August 20, 2026