Keep Brixi and Your Existing CRM in Sync
Keep contacts, leads, and deal data aligned between Brixi and an external CRM — whether you're running a migration, operating in parallel with a system the rest of the company uses, or doing periodic reconciliation with a partner team's CRM.
Entry pointAutomation → Integrations
| Article summary | Details |
|---|---|
| Requires | Account admin role in Brixi and admin access in the external CRM. |
| Where to go | Integrations → CRM (search for Salesforce CRM or Zoho CRM). |
Available CRM Integrations
| Integration | Use it for |
|---|---|
| Salesforce CRM | Sync contacts, leads, and deals with a Salesforce org. |
| Zoho CRM | Sync contacts, leads, and deals with a Zoho CRM account. |
More CRM connectors may appear in Integrations → View all depending on your plan and region. If a connector you need isn't listed, ask your admin to check the plan, then reach out via Getting Help.
Who Can Do This
Only account admins should connect CRM apps. CRM connections can affect large amounts of customer data, so agree on ownership and sync rules with sales leadership before installing the connector.
A misconfigured connector can overwrite owners, deal stages, or contact fields across thousands of records. Always test on a small segment first.
When to Use a CRM Connection
Use a CRM app connection when:
- You are migrating from another CRM into Brixi.
- A central operations team still maintains records in another system.
- You need to compare or reconcile accounts before fully moving to Brixi.
- A partner team uses a separate CRM but must share sales records with you.
Avoid connecting a CRM app casually. If both systems update the same fields without clear rules, users lose trust in the data and you end up fixing duplicates by hand.
Before You Connect
Work through this checklist with sales leadership before running the connector:
- Source of truth. Identify the source of truth for contacts, companies, deals, owners, and stages. Both systems can read; only one should write.
- One-time vs ongoing. Decide whether data should be imported once (migration) or kept in sync (parallel operation).
- Matching rules. Define duplicate matching rules — usually phone number, email, or external record ID. Pick the same rule on both sides.
- User mapping. Match external CRM users to Brixi users by email. Plan how to handle inactive users.
- Stage mapping. List the deal stages on both sides and map them 1-to-1. Stages that don't map (e.g., a stage that only exists in Salesforce) need a default destination.
- Test segment. Pick a small test segment (say 20–50 records) before syncing the full dataset.
- Communicate. Let sales users know which system owns what after the sync — and where to report problems.
Connect a CRM App
- Open Integrations and search for the CRM app (Salesforce CRM or Zoho CRM).
- Select Install (or Manage if it's already installed).
- Authorize Brixi with an admin account in the external CRM.
- Review the available sync options (objects, fields, direction).
- Select the objects and fields to connect — start narrow.
- Save the configuration and run a small test sync.
- Review the test records in Brixi — check owners, stages, required fields, and tags.
- Expand the sync only after the test segment looks correct.
For step-by-step setup per CRM, see:
Run the test sync on a workday when sales staff are around. If something looks wrong (owners, stages, tags), they'll spot it faster than reports will.
Reporting Checks
After a CRM sync, review the following in your Contacts list:
- Total imported contacts and deals — does the count match what the external CRM reports?
- Records missing owners, phone, or email — these are the ones sales will skip.
- Stage distribution — a pile-up in one stage usually means a stage map went wrong.
- Duplicate count — search by phone or email; duplicates created by the sync are usually visible as same-day pairs.
- Recent activity on migrated deals — confirm that subsequent activity (notes, calls) is being captured in Brixi.
Common Issues
| Issue | What to check |
|---|---|
| Imported records have no owner | External users may not match Brixi users by email. Map or reassign owners. |
| Deal stages look wrong | Stage names may not match your Brixi pipeline. Re-check the stage map and re-run on a small segment. |
| Duplicate records appear | Matching field (phone / email / external ID) is missing or inconsistent. Tighten the matching rule. |
| Some fields are blank | The external CRM may not expose those fields or they weren't selected during connector setup. |
| Users keep updating both systems | Source-of-truth rule wasn't communicated. Set a clear ownership rule and announce it. |
| Sync stops after first run | Token expired, account changed permission, or connector was uninstalled. See the per-CRM page's troubleshooting section. |
Contact support before a large production sync if you are unsure about field mapping or duplicate handling. Share:
- The CRM name (Salesforce / Zoho / other).
- The object types you want to sync (Contacts / Leads / Deals).
- The expected record count.
- Your intended source-of-truth rule.
Contact support after a sync only if records didn't arrive, duplicates appeared at scale, or the connector status keeps flipping to failed even after reconnecting.