Skip to content
Per-pair page

HubSpot + Salesforce: bridge two CRMs without losing data.

Sync HubSpot contacts and Salesforce records during migrations, dual-CRM operations, or M&A scenarios. Avoid sync loops with directional field ownership.

Trigger app
HubSpot as the trigger

Workflows fire when something happens in HubSpot.

See all 18 triggers →
Action app
Salesforce as the action

Workflows do something in Salesforce, instantly.

See all 13 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

HubSpotSalesforce

When something happens in HubSpot, do it in Salesforce.

18 HubSpot triggers wired to 13 Salesforce actions. Most-used pairing: New CompanyConvert Lead.

SalesforceHubSpot

Or fire it the other way around.

0 Salesforce triggers wired to 23 HubSpot actions downstream.

  • Use any trigger in the catalog as the upstream.
See SalesforceHubSpot
Popular pairings

Common HubSpot → Salesforce workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 234 combinations
When new company in HubSpot, convert lead in Salesforce.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, create account in Salesforce.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, create contact in Salesforce.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, create note in Salesforce.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When company deleted in HubSpot, convert lead in Salesforce.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, create account in Salesforce.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, create contact in Salesforce.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, create note in Salesforce.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company property changed in HubSpot, convert lead in Salesforce.

Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).

How it works

Connect HubSpot and Salesforce in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize HubSpot and Salesforce

    Open Tiny Command, authorize HubSpot and Salesforce once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a HubSpot trigger

    Drop the HubSpot → New Company trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/hubspot.trigger-company-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Salesforce action

    Drop the Salesforce → Convert Lead action below it. Map fields from the HubSpot payload into the Salesforce inputs.

    salesforce.convert-lead
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about HubSpot + Salesforce.

When do organizations run both HubSpot and Salesforce?
During CRM migrations (gradual switchover), in M&A scenarios (acquired company had different CRM), or when different business units chose different tools. The pair keeps both in sync while you decide.
How do I sync HubSpot contacts into Salesforce?
HubSpot Contact Created or Updated → Salesforce Find or Create Lead/Contact by email → Update fields. Use HubSpot ID as Salesforce external_id custom field for idempotent upserts.
Can I sync Salesforce Opportunities back to HubSpot Deals?
Yes. Salesforce Opportunity Updated → HubSpot Find or Create Deal by Salesforce ID custom field → Update Deal with stage, amount, close date. Pick one side per field as source-of-truth.
How do I avoid sync loops?
Pick one direction per field. HubSpot owns marketing fields (lifecycle, lead source); Salesforce owns sales fields (stage, owner). Or vice versa. Document field ownership rules clearly.
Can I sync custom objects between HubSpot and Salesforce?
Possible but complex. HubSpot custom objects map to Salesforce custom objects (__c suffix). Maintain a field-level mapping table; expect this to be a multi-week setup effort.
How do I respect Salesforce API limits when syncing high HubSpot volume?
Use Salesforce Bulk/Composite API for batched updates. Filter HubSpot triggers to changes only (not every contact, every update). Most orgs stay under SFDC's 15K-150K daily call limit.
Related

Other apps that pair well with HubSpot.


Wire HubSpot to Salesforce in 2 minutes.

Free tier available. No credit card. No onboarding call.