HubSpot–Salesforce Integration: Setup and Sync Rules

Native connector, managed sync, or custom code?

Do not reject the native connector merely because the requirement says “two-way.” HubSpot documents a Two-way field rule as well as Salesforce-preferred and disabled-sync options. Choose by the actual fields, relationships, and business rules involved. A simple contact handoff and a multi-system customer-data workflow are different evaluations.

Conversely, a managed connector does not remove configuration decisions. Your team still owns record scope, access approval, field ownership, and acceptance. Use the same evaluation worksheet for all approaches so the comparison reflects your workload.

Define the record model and field owners

Resolve the Salesforce Lead/Contact distinction first. A HubSpot contact is not automatically a one-to-one representation of both Salesforce objects throughout conversion. Record the current Salesforce ID and the conversion behavior you expect, then test a converted lead and an existing contact before a full import.

Do not assume field labels are stable identifiers. Compare API names, types, allowed enum values, and whether a property is writable. An “Industry” label in both products can still have different permitted values. Likewise, clearing a field and omitting it from an update can have different meanings.

Set up the native integration deliberately

Confirm eligibility and access requirements in HubSpot’s installation guide. Install Salesforce from the HubSpot Marketplace and authorize the intended Salesforce account. After connection, open Salesforce under Settings → Integrations → Connected Apps. Work in the Data sync area to review objects, field mappings, and sync rules. Keep a record of the configuration before the initial data movement.

• 01Select the objects required for the approved sales handoff.
• 02Match compatible HubSpot properties and Salesforce fields.
• 03Choose the supported rule for each field; avoid a blanket bidirectional default.
• 04Set the appropriate inclusion criteria and review the reverse-direction selection behavior.
• 05Test new, existing, and converted records before expanding the selected set.
• 06Explicitly resync the records needed to populate newly mapped fields.

Two native behaviors deserve a test: existing values do not retroactively populate merely because a new mapping was created, and the initial sync can establish a Salesforce baseline for a previously unsynced field. See HubSpot’s mapping rules. Also test inclusion at first pairing rather than assuming it prevents every initial write; HubSpot documents first-sync exceptions.

How often does the native integration sync? HubSpot documents automatic sync triggers and an approximately 15-minute check for new or updated information. Actual movement still depends on mappings, scope, API capacity, and record health. Measure the handoff you need rather than treating the check interval as a universal delivery guarantee.

Keep the intended business behavior separate from the available product setting. If a native field has special rules, adapt the design or choose an approach that supports your requirement; do not label an unsupported configuration “done.”

Connect the pair with Stacksync

Start with a small representative scope. In Stacksync, create the HubSpot connection, choose the account, and authorize it using the required administrator access. The HubSpot authorization guide documents the Super Admin requirement and region selection. Create the Salesforce connection with the intended integration user following the Salesforce authorization guide.

Review the objects available to both connections, choose the approved mappings, and validate the initial record matches. Configure only the permitted write directions. Include contacts, companies/accounts, and the relevant relationships in the test rather than proving a single isolated contact field.

Salesforce change detection depends on the connector mode and permissions. Stacksync documents Apex triggers where usable and incremental polling otherwise. Object eligibility also varies. Measure the resulting freshness for your selected objects instead of treating a connector-wide latency claim as a guarantee. Review Salesforce connector behavior.

For HubSpot, verify the account’s object access and association requirements. The HubSpot connector documentation lists object availability and account constraints. Supporting an object in the product does not bypass the permissions or subscription restrictions of your account.

Launch with a measurable handoff

Complete a test set covering new contact creation, an existing contact match, lead conversion, a company relationship, an invalid enum, a cleared field, and simultaneous edits. For each case, record the expected owner and destination outcome. Then measure lag during normal activity and an initial-load catch-up period.

Bring the result to the production-readiness review. If evaluating Stacksync, request a HubSpot–Salesforce integration demo with your selected objects, matching rules, expected volume, and hardest exception. The decision should be based on that working handoff.