HubSpot and Salesforce Integration Guide

Start with the business handoff

HubSpot and Salesforce can support a shared marketing and sales process when both teams agree on what information should move between them. The integration is not simply a way to copy every record. It should help a salesperson understand a qualified lead and help marketing understand what happened after the handoff.

Document one workflow before connecting systems. For example, marketing qualifies an inquiry in HubSpot, sales receives the agreed information in Salesforce, and the resulting sales status becomes available for follow up and reporting. Define who owns each step, what makes a record eligible, and what should happen when the record is incomplete.

Confirm access and integration requirements

Review the current HubSpot Salesforce integration requirements before choosing a setup. Availability, supported objects, permissions, and API limits depend on your subscriptions and configuration. Do not assume that every custom object or relationship will synchronize just because contacts can.

Choose an authorized integration account with only the permissions it needs. Record who maintains that account and how credentials will be managed when an employee leaves. Use the supported connector when it meets your workflow. Consider a custom integration only when a documented requirement cannot be handled by the available configuration.

Assign a source of truth for each field

Decide which system is authoritative for important fields before turning on synchronization. Sales may own opportunity stages, while marketing owns campaign context. Contact details may require a separate rule. Record these decisions in a mapping sheet instead of relying on assumptions.

For every mapped field, capture its business meaning, object, format, allowed values, update direction, and handling of blank values. Check that a value in one system means the same thing in the other. A lifecycle stage is not automatically equivalent to an opportunity stage.

Pay special attention to consent, email preferences, and suppression rules. A transferred address does not itself establish permission to send marketing messages. Your teams should review the intended behavior against their applicable consent requirements.

Clean records and define matching rules

Review duplicate people and companies, invalid addresses, inconsistent country values, and missing ownership information. A connector can distribute existing data problems more quickly; it does not automatically resolve them.

Understand how your chosen connector matches records and handles leads, contacts, accounts, and associations. Test records that share a company domain, people who change employers, and records that already exist in both systems. Keep a recoverable export before making bulk changes.

Test with a controlled group

Start with a small set of approved test records rather than the whole database. Check creation, updates, assignment, stage changes, blank fields, duplicate matches, and any supported deletion or suppression behavior. Test both the initial import and later changes.

Verify the result inside each application, not just the connector status screen. A successful synchronization can still put a value in the wrong field or associate it with the wrong company. Confirm that workflows do not repeatedly trigger each other and that notifications reach the intended owner.

Record expected results and have both marketing and sales approve them. Document how to pause synchronization, investigate a failure, and recover records without creating more duplicates.

Monitor the integration after launch

Assign an owner to review synchronization errors, unmatched records, processing delays, and unexpected changes in record volume. Investigate permissions, field changes, validation rules, and API limits when synchronization fails.

Reconcile a sample of records regularly. Agree on reporting definitions before comparing dashboards: attribution, time periods, lifecycle stages, and opportunity inclusion rules can differ between systems. An integration alone does not make two reports equivalent.

Treat new fields, changed workflows, and connector upgrades as controlled changes. Update the mapping documentation and repeat the relevant tests before expanding the integration.

Launch checklist

• Confirm subscription requirements, permissions, and supported objects.
• Approve field ownership, matching rules, and consent handling.
• Back up records and test a controlled group in both systems.
• Check workflows, notifications, reporting definitions, and recovery steps.
• Assign ongoing monitoring and documentation responsibilities.