CRM compatibility
CRM lead source compatibility, field by field.
How each major CRM records lead source, how the source reaches it from Lead Source, and what each setup can write. Verified data only, so you pick the setup that lands the real source on every record.
Free to start · no card
Lead Source records the same details for every CRM. Only the connection differs.
Whatever CRM you run, Lead Source captures the real source and campaign, the landing page and the full journey on every form submission.
-
A page of their own: Salesforce, HubSpot, Pipedrive, Keap, Close
- Source lands on the record through the Zapier app or a signed webhook.
- Runs alongside the CRM’s own source field.
- A setup guide for each, linked in the matrix.
-
Verified Zapier connector: Copper, Zoho, monday, Freshsales, Dynamics 365, Insightly
- Connects through the CRM’s own Zapier connector.
- Creates or updates the relevant record.
- Fills the fields the connector exposes.
What differs is which field the source can land in once it reaches your CRM. Five CRMs have a page of their own; six more are covered by a verified Zapier connector. Want to see what your form records today first? Test your form and see what a submission would carry.
The compatibility matrix.
Native field names appear only where they are a standard, documented field. “Not verified” means we did not confirm it, so we do not claim it.
| CRM | Native source field | How the source arrives | Where it lands | Last verified |
|---|---|---|---|---|
| Salesforce | Lead Source picklist | Zapier app or a signed webhook | On the record, beside the picklist | Our own Zapier app and webhooks |
| HubSpot | Original Source property | Zapier app or a signed webhook | On the contact, alongside Original Source | Our own Zapier app and webhooks |
| Pipedrive | Source field on the lead | Zapier app or a signed webhook | On the lead or person record | Our own Zapier app and webhooks |
| Keap | Lead Source field | Zapier app or a signed webhook | On the contact record | Our own Zapier app and webhooks |
| Close | Lead source custom field | Zapier app or a signed webhook | On the lead record | Our own Zapier app and webhooks |
| Copper | Standard Source field | Zapier: Create/Update Lead | Standard Source field and Tags (verified) | Zapier, 11 Nov 2026 |
| Zoho CRM | Lead Source picklist | Zapier (Premium): Create/Update Module Entry | Module entry fields; custom-field write not verified | Zapier, 11 Nov 2026 |
| monday | None native (board column) | Zapier: Create Item, Update Item | Board column values, including custom columns | Zapier, 11 Nov 2026 |
| Freshsales | Lead source field | Zapier (Freshsales Suite): Create Contact, Update Contact, Create Deal, Update Deal | Contact or deal fields; custom-field write not verified | Zapier, 11 Nov 2026 |
| Dynamics 365 | Lead Source option set | Zapier (Premium): Create Lead, Update Lead, Create Contact, Update Contact | Lead or contact fields; custom-field write not verified | Zapier, 11 Nov 2026 |
| Insightly | Lead Source field | Zapier: Create Record, Update Record (object-driven) | Object record fields; custom-field write not verified | Zapier, 11 Nov 2026 |
Every row captures the same source, landing page and full journey; only the route and the destination differ. Zapier connector details last verified 11 November 2026. For the why behind all of it, read the CRM lead source guide.
Three things the table is telling you.
Read across the rows and the same three patterns repeat, whichever CRM you run.
Native field is a single value. Every native source field, picklist, option set or column holds one channel value. None of them hold the campaign, landing page or journey, in any CRM.
The destination is the difference. For the five CRMs with their own page, the source lands on the record. The other six create or update the record through Zapier; only Copper’s verified setup writes a standard source field.
The capture is the constant. Lead Source captures source, landing page and journey at submission and stores every lead in your own dashboard. The CRM is the last step, and never the only copy.
CRM compatibility, questions answered.
Which CRMs does Lead Source connect to directly?
Salesforce, HubSpot, Pipedrive, Keap and Close each have a page of their own, and the source reaches them through the Lead Source Zapier app or a signed webhook. Copper, Zoho, monday, Freshsales, Dynamics 365 and Insightly connect through their own Zapier connector. Lead Source writes to no CRM natively, so every route runs through Zapier, a webhook or a CSV export.
Can the source land on a custom field in every CRM?
Not in every one, and the matrix says which. For the five CRMs with their own page, the source lands on the record. The Zapier-connected CRMs create or update the record; Copper additionally writes its standard Source field, which is verified. Where a custom-field write on a standard record was not verified, the table says so rather than implying it works.
How current is this compatibility data?
The Zapier connector details were verified against zapier.com on 11 November 2026. The five CRMs with their own page are covered by our own Zapier app and signed webhooks. Anything we did not confirm is marked not verified rather than guessed, so the table stays trustworthy.
Keep reading
See where your CRM stands.
Sign up free and Lead Source records the source, landing page and journey on every form, then sends each lead to whichever CRM you run.
Free to start · no card









