Connecting HubSpot and Salesforce is the easy part. Keeping them in agreement — without overwriting good data or syncing junk back and forth — is where most teams struggle. Managing the integration settings means deciding what syncs, in which direction, and under what rules — because the defaults rarely match how your business works, and a misconfigured sync can quietly corrupt both systems. Here's the practitioner's read on the settings that matter and how to keep the two platforms honest.
What do the integration settings actually control?
They control three things — which records sync, which way data flows, and how conflicts resolve — and those three decisions shape every record that moves between the systems. The sync isn't a single on-off switch; it's a set of rules. You choose which objects sync (contacts, companies, deals or opportunities), whether each field flows one way or both, and what happens when the same field differs in each system. Get these right and the two platforms stay aligned. Get them wrong and you can have HubSpot overwriting fresh Salesforce data, or the reverse, on every sync. The settings are the steering wheel; ignoring them means trusting defaults that weren't built for your data.
How should you handle sync direction and field mapping?
Decide field by field which system is the source of truth, and set the sync direction to match — because the wrong direction means your good data gets overwritten by your worse data. For each mapped field, ask which system owns it. Sales-owned fields like deal stage might flow from Salesforce to HubSpot; marketing-owned fields like email engagement might flow the other way; some fields sync both ways. Map deliberately rather than accepting the defaults. Worked example: a lifecycle or status field that marketing maintains in HubSpot should flow into Salesforce — but if it's set to sync the other direction, every Salesforce update wipes out the marketing team's careful work. The mapping and direction together decide who wins, and you want that decided on purpose, not by accident.
How do you control which records sync?
Use the sync filters to control which records cross over — because syncing everything floods both systems with records that don't belong there and inflates your costs and your noise. The integration lets you set rules — often based on a list or criteria — for which contacts and records actually sync to Salesforce, so you're not pushing every cold lead into the sales system. Decide intentionally: maybe only marketing-qualified leads sync to Salesforce, while everything stays in HubSpot. Worked example: a portal with tens of thousands of top-of-funnel contacts that should live in HubSpot only, with a filter sending just sales-ready leads to Salesforce — versus an unfiltered sync that dumps everything into Salesforce, clutters the reps' view, and can run up costs. The filter is how you keep each system holding the right records.
How do you keep the sync healthy over time?
Monitor it and revisit the settings as the business changes — because a sync configured once and forgotten drifts out of true the moment your fields, processes, or teams change. Check the sync health and error logs periodically; sync errors are early warnings of mapping or data problems. When you add a new property, decide whether it should sync before it causes a mismatch. When a team changes which system owns a field, update the direction. The common failure is an integration set up during onboarding and never touched, so a year later it's overwriting data nobody meant it to. A periodic review — are the mappings still right, are there errors piling up, do the filters still match the strategy — keeps both systems trustworthy. This is the same hygiene discipline that keeps any portal reliable.
The IV-Lead take
A HubSpot–Salesforce integration is powerful and unforgiving: configured well, the two systems reinforce each other; configured carelessly, they corrupt each other on a schedule. The work isn't in connecting them — that's a few clicks — it's in the deliberate decisions about direction, mapping, and filtering, and in revisiting those decisions as the business evolves. Treat the integration settings as living configuration that deserves the same care as the data itself, and the two platforms stay in honest agreement instead of quietly fighting.
Worried your HubSpot–Salesforce sync is overwriting good data or syncing the wrong records? Book a 30-minute portal audit — we'll check your mappings, direction, and filters and tell you what's drifting. For the bigger picture, see how we approach CRM integrations.
Frequently asked questions
Can I sync data both ways between HubSpot and Salesforce?
Yes. You can set each mapped field to sync one direction or both. The key is choosing per field which system is the source of truth, so a two-way sync doesn't let your weaker data overwrite your stronger data.
How do I stop every contact from syncing to Salesforce?
Use the integration's sync filters — typically based on a list or set of criteria — so only the records you want (for example, marketing-qualified leads) cross into Salesforce, while the rest stay in HubSpot.
What happens when the same field differs in both systems?
The conflict resolves according to your sync direction and settings for that field. That's exactly why deliberate field mapping matters — it decides which system wins when the values disagree.
How do I know if the sync is having problems?
Check the integration's sync status and error logs regularly. Sync errors usually point to a mapping mismatch or a data issue, and catching them early keeps small problems from corrupting records across both systems.
