> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/comparison.md). # Comparing the CRM integrations Mobly supports four CRMs — HubSpot, Salesforce, Pipedrive, Zoho — but they don't all do the same things. Some sync activities; some don't. Some let you sync to multiple object types; others write to a single object. This article is a side-by-side reference for what each integration supports. Use this when: * You're picking which CRM to connect first * You're evaluating whether a feature you need is available for your CRM * A CSM needs a fast answer to "does Mobly do X for \[vendor]?" For setup-specific instructions, jump to the per-CRM [setup guides](/help-center/integrations/crm.md#per-crm-docs). > Looking for a Marketing Automation tool? Mobly also integrates with Marketo and Pardot — see the [Marketing Automation comparison](/help-center/integrations/marketing-automation/comparison.md). ## At-a-glance | | HubSpot | Salesforce | Pipedrive | Zoho | | -------------------------------- | ------------------ | ----------- | ---------------- | ---------- | | **Setup time** | \~15 min | \~30 min | \~15 min | \~20 min | | **Difficulty** | Easy | Moderate | Easy | Moderate | | **Auth** | OAuth | OAuth | OAuth | OAuth | | **Lead/Contact sync** | ✓ | ✓ | ✓ | ✓ | | **Company/Account sync** | ✓ | ✓ | ✓ (Organization) | — | | **Activity logging** | ✓ Engagements | ✓ Tasks | — | ✓ as Notes | | **Campaign sync** | ✓ Marketing Events | ✓ Campaigns | — | — | | **Configurable sync strategies** | — | ✓ 3 modes | — | — | | **Custom object support** | — | ✓ | — | — | ## By feature ### Authentication All four CRMs use OAuth through Mobly's new integration platform. No Connected App, API key, or custom REST role setup is required on your side. ### Lead / Contact sync Every CRM gets the captured lead synced. The CRM-side object differs by vendor: | CRM | Primary object | How Mobly matches existing records | | ---------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------- | | HubSpot | Contact | Contact ID → Email | | Salesforce | Lead, Contact, or Account (configurable — see [Sync strategies](#configurable-sync-strategies) below) | Varies by strategy | | Pipedrive | Person | Email | | Zoho | Lead | Lead ID → Email | ### Company / Account sync Three CRMs let Mobly write Company-level data alongside the lead: * **HubSpot** — creates or updates a HubSpot Company by domain or company name, and associates the Contact * **Salesforce** — creates or updates an Account; Contact is created underneath the Account in the "Accounts and Contacts" sync strategy * **Pipedrive** — creates or updates an Organization and links the Person to it Zoho only syncs the lead-side record; company information goes onto the Lead record as fields rather than a separate Account. ### Activity logging When reps in Mobly take an outreach action — Pulse email, manual note, LinkedIn touch, SMS, call, meeting — that activity can be pushed to the CRM. Coverage differs significantly: | CRM | Activity object on the CRM side | Coverage | | -------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------- | | **HubSpot** | Engagement (Call, Email, Meeting), Note, Communication | **Full** — every activity type lands on the right HubSpot object | | **Salesforce** | Task | **Full** — every activity type becomes a Task with the type in the Subject and detail in the body | | **Zoho** | Note (under the Lead) | **Partial** — all activity types log as Notes on the Lead. No dedicated Task or Activity object | | **Pipedrive** | — | **Not supported** | For Pipedrive, lead activity history lives in Mobly itself — the CRM sees the resulting field updates but no per-activity record. The activity types Mobly tracks: Pulse-sent emails, calls, meetings (booked via Calendly/Chili Piper), LinkedIn touches, SMS, manual notes, social touches (Twitter, Facebook). ### Campaign sync Per-event sync to a campaign-equivalent object on the CRM side: | CRM | Object | Notes | | -------------- | ------------------------- | ---------------------------------------------------------------------------------------------- | | **HubSpot** | Marketing Event | Requires HubSpot Marketing Hub. Member status drivable from Mobly qualifier values | | **Salesforce** | Campaign + CampaignMember | Member Status drivable from Mobly qualifier values | | **Pipedrive** | — | No native campaign object. Use a custom field on the Person/Organization for event attribution | | **Zoho** | — | No campaign object sync | ### Configurable sync strategies **Salesforce is the only CRM with configurable strategies** for where leads land. Set on the Salesforce Connect tab: * **Leads only** — every Mobly lead becomes a Salesforce Lead * **Leads and Contacts** (recommended) — match Lead first, fall back to Contact, otherwise create a Lead * **Accounts and Contacts** — match Contact first, create under matched Account; create both if no match Other CRMs always sync to a single primary object (the one listed in the [Lead/Contact sync](#lead--contact-sync) table above) with no configuration knob. ### Custom objects **Only Salesforce supports custom-object writes** today. You can map Mobly fields to custom objects from the Mapping tab. The other three CRMs only sync to standard objects. Custom *fields* on those standard objects are fully supported across all four — only custom *objects* are Salesforce-only. ### Field type enforcement How strict is each CRM about validating field types? Stricter enforcement means more upfront mapping work but cleaner CRM data; permissive CRMs accept malformed values more readily. | CRM | Strictness | What this means | | -------------- | ---------- | ----------------------------------------------------------------------------------------------------------- | | **Salesforce** | Strict | Restricted picklists, Validation Rules, field-level security — lots of places where a write can be rejected | | **Zoho** | Strict | Picklist values strictly enforced | | **HubSpot** | Moderate | Picklists are strict; text fields are permissive | | **Pipedrive** | Permissive | Pipedrive accepts most type variation; option-list fields are the main strict spot | ## When to use what **Most full-featured:** Salesforce and HubSpot. Multi-object sync, activity logging, campaign sync, custom objects (Salesforce), three sync strategies (Salesforce). **Smaller-team CRMs:** Pipedrive and Zoho. Simpler CRMs and the integrations match — lead sync is solid, activity history lives in Mobly (or partially in Zoho as Notes). If you're already on a CRM, open that CRM's [setup guide](/help-center/integrations/crm.md) for the specifics. ## Per-CRM details * [HubSpot](/help-center/integrations/crm/hubspot.md) * [Salesforce](/help-center/integrations/crm/salesforce.md) * [Pipedrive](/help-center/integrations/crm/pipedrive.md) * [Zoho](/help-center/integrations/crm/zoho.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/comparison.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.