> ## Documentation Index
> Fetch the complete documentation index at: https://hc.starbridge.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Sync contacts to your CRM
> Create and update CRM contacts from Starbridge — including deduplication, account association, and keeping contacts current over time.
Use this flow to sync enriched contacts from Starbridge into your CRM Contact object. Starbridge deduplicates against existing contacts, associates each contact to the correct account, and keeps contact data current over time — including setting an active/inactive flag when a contact's employment status changes.
This article assumes your CRM is connected, account matching is complete, and contact sync is configured. See [Connect your CRM](/admins/connecting-your-crm), [Account matching](/integrations/account-matching), and [Contact sync](/integrations/contact-sync) if you haven't done these yet.
## Standard contact sync
The recommended path for most bridges. Adding a Standard contact sync column inherits your admin's configured lookup rules, field mappings, and run conditions automatically — no additional setup required.
To find contacts to sync to your CRM, first [enrich them in a Bridge](/university/contact-enrichment).
In your Bridge, click **Add enrichment → Configure Integration → Sync Contacts to My CRM**.
Starbridge preselects **Standard contact sync** and preselects the contact to sync to your CRM.
Double-check that Starbridge has preselected the right CRM integration (if you have multiple CRM integrations) and the right contact (if you have multiple contact enrichment columns in the bridge).
Run Conditions are **optional**.
Your admin has already configured their preferred run conditions (the minimum data requirements to sync the contact to the CRM) in the standard contact sync rules.
Any run conditions you define here are **additional** on top of the standard contact sync rules; they do not overwrite or disregard the admin's contact sync rules.
Click **Add & Run Enrichment**. Starbridge will apply your admin's standard contact sync rules to sync the contacts to your CRM.
Each cell in the column enrichment will update to show **Success**, **No Changes Applied**, or **Skipped** if the run conditions aren't meant. Click into any cell to see a full sync history for that row.
If a cell shows **Skipped: Run condition not met**, the contact didn't satisfy your admin's sync rules. The most common cause is that the contact's buyer doesn't have a matching account in your CRM, or the contact is missing one or both of email and phone. Check with your admin if contacts are being skipped unexpectedly.
## Custom contact sync
Custom contact sync is not necessary for most contact sync use cases, and typically only recommended when you have a bridge-specific analysis you want to sync to custom fields on the Contact object.
In your bridge, click **Add enrichment → Configure integration → Pull data from my CRM** and select the Account or Company object. See [CRM enrichment columns](/crm-enrichment-columns) for step-by-step instructions.
Enable **Account matching** so Starbridge resolves the right CRM account for each buyer automatically. This is used when creating new contacts to associate them to the correct account.
Add a second **Pull data from my CRM** column for the Contact object. This tells Starbridge whether each contact already exists in your CRM so the sync column knows whether to create or update.
We recommend an if-else matching structure:
* **IF** Starbridge Contact ID matches CRM Contact object's Starbridge Contact ID
* **ELSE** **IF** Starbridge Contact Email matches normalized CRM Contact object's email
This two-step fallback handles cases where a contact's email has changed since they were first created.
Click **Add enrichment → Configure integration → Send data to my CRM**, select the Contact object, and set the sync type to **Upsert**. See [CRM enrichment columns](/crm-enrichment-columns) for step-by-step instructions.
* If a match exists via email or Starbridge ID → update the contact
* If no match exists → create a new contact
Map each Starbridge contact field to the corresponding CRM Contact field and choose a write behavior for each. See [CRM enrichment columns](/crm-enrichment-columns) for step-by-step instructions.
A few important mappings:
* **Account association** — map the Account ID returned from your account lookup column to the contact's Account or Company relation field. This ensures new contacts are linked to the right account on creation.
* **Starbridge Is Active** — set to **Overwrite** so Starbridge can update this field when a contact becomes inactive.
HubSpot: if the **Company ID (Relation to Company)** value isn't available from your account lookup column, see [HubSpot-specific details](/crm-enrichment-columns#hubspot-specific-details).
Run conditions prevent the sync column from firing on rows where it shouldn't. We recommend:
* **Strongly recommended:** only run if the account lookup column's Record ID is not empty. This prevents contacts from being created without an associated account (orphan contacts).
* **Optional:** only run if the Starbridge email address is not empty. This avoids creating contacts with no usable email address.
* If your team makes outbound calls, **do not add** this run condition as it may prevent you from syncing contacts with a valid phone number.
Once your lookup columns are resolving correctly and your sync column is mapped, run the sync.
When adding the sync column, select **Run** **First 5 rows** and run the sync for those only. Check whether contacts were created or updated as expected — verify account associations, field values, and that no orphan contacts were created. If anything looks off, adjust your field mapping, write behavior, or run conditions before committing to the full bridge. Once you're satisfied, select the column and run for all rows.
Each cell updates to show **Success**, **No action taken**, or **Error**. Click into any cell to see a full history of syncs for that row.
## Keeping contacts current
Once contacts are synced with Standard contact sync, Starbridge will keep them up to date over time. As Starbridge detects changes — email address updates, title changes, or contacts who are no longer active in their role — it will update the corresponding CRM Contact record according to your admin's sync rules.
The **Starbridge Is Active** field is particularly useful here: Starbridge will flip it to `false` when it detects a contact is no longer active, giving your team a reliable signal for contact hygiene without manual work.
When contacts are synced with Custom contact sync, Starbridge will keep them up to date respecting the Custom contact sync's run conditions, rerun settings, and field mappings.
## Next steps
Push job change signals and contacts into your CRM for rep actioning.
Write account enrichment, analysis, and scores to your CRM Account object.