> ## Documentation Index
> Fetch the complete documentation index at: https://docs.benefitflow.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How to Sync BenefitFlow Data to Your CRM
> Push Employers, Brokers, and Contacts from a list into your connected CRM.
This guide shows you how to push BenefitFlow records into your CRM — Employers, Brokers, Broker Office Locations, and Contacts — straight from a list.
**First time?** Your CRM has to be connected before anyone can sync. That's a one-time setup an admin does — see [Connecting Your CRM (Admin Setup)](/knowledge-base/crm-integrations-getting-started). Already connected? Keep going.
## Step 1: Add records to a list
Run a search on any tab (Brokers, Contacts, or Employers) and apply your filters. On the **Broker Contacts** and **Employer Contacts** searches, you can also use the [CRM Filter](/knowledge-base/crm-filter) to focus on people who aren't already in your CRM.
Use the checkbox on each row, or click **Select All**.
Click **Add to List**, then choose an existing list or create a new one.
If you're using FlowPilot, skip the manual steps and just ask in plain language, e.g. *"Add these search results to my list"* or *"Create a new list called Q4 Texas Prospects and add these."*
## Step 2: Open the list
Navigate to the **Lists** tab and open the list you just built (e.g., Brokers, Broker Contacts, Employers, Employer Contacts).
## Step 3: Sync to CRM
From inside the list, click **Sync**. Push records **one-by-one**, or use **Sync to CRM** to bulk sync the entire list.
**Smart Sync Logic** — BenefitFlow checks your CRM before pushing anything:
* ✅ **Net-New** — the record doesn't exist in your CRM yet, so it gets added
* 🔁 **Update** — the record already exists; only approved mapped fields are updated
* ✔️ **Synced** — the record exists and no changes are needed
**Other tools in the list view:**
* **Assign Owner** — manually reassign CRM record ownership
* **Export** — push to CSV instead of, or in addition to, a CRM sync
## How matching works
BenefitFlow prevents duplicates by matching on these unique identifiers:
| Object | Unique Identifier | Example |
| :---------------------- | :--------------------- | :------------------------------------------------------ |
| Employers | Website | walmart.com |
| Employer Contacts | Email | [john.smith@walmart.com](mailto:john.smith@walmart.com) |
| Brokers | Website | mercer.com |
| Broker Office Locations | Website + City + State | mercer.com + New York + NY |
| Broker Contacts | Email | [john.smith@mercer.com](mailto:john.smith@mercer.com) |
BenefitFlow retains historical email addresses, so it can still match a contact even if your CRM has a stale email on file.
## Good to know
* The **broker → office → contact hierarchy** is built automatically on every sync. You don't need to create it. (See [Association Architecture](/knowledge-base/crm-association-architecture).)
* **Employers sync as standalone accounts** and are *not* automatically linked to their primary broker office. That association has to be added manually. See [Linking Employers to Their Primary Broker Office](/knowledge-base/crm-employer-broker-linking).
* **Field mappings are set by your admin.** If a field isn't syncing the way you expect, check with them. (Admins: see [Connecting Your CRM](/knowledge-base/crm-integrations-getting-started).)
## Where to go next