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.
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.Related Resources
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.

