The owner syncs both ways. An owner reaches Salesforce only if it matches an active user by name and email.
The HubSpot and Salesforce connector copies owners both ways. Used without a plan, it changes the lead owner after Salesforce has routed the lead. This page covers the connector's own rules, as HubSpot documents them.
1. How the connector picks an owner
HubSpot's article on lead owners, last updated 16 September 2026, says:
- HubSpot sends an owner only when it matches an active Salesforce user by name and email.
- An owner that does not exist in Salesforce reverts to its last Salesforce value.
- For a new lead, a matching HubSpot owner is used on the first sync. Otherwise assignment rules apply.
- An existing Salesforce lead with an active owner keeps that owner on the first sync. Assignment rules do not apply.
- After that, an owner change in either system syncs to the other.
- Salesforce requires an owner. A record created from an unassigned HubSpot record is owned by the integration user.
2. Causes
- No match by name and email. The owner never reaches Salesforce, or reverts.
- Two-way owner sync. Whichever system changed last wins. HubSpot says the owner mapping can only be two-way, and the Owner value must match exactly.
- A Salesforce assignment rule on create. It fires when the lead first syncs, then HubSpot may write its own owner.
- Duplicate Salesforce records. The sync may update a different record from the one your rule routed.
3. The four sync rules
- Prefer Salesforce unless blank. HubSpot sends a value only when Salesforce is empty. Salesforce values overwrite HubSpot's.
- Always use Salesforce. HubSpot never sends data to Salesforce for that field.
- Two-way. The most recent change wins, and deletions sync both ways.
- Don't sync. Nothing passes between the systems for that field.
For most fields, Always use Salesforce stops HubSpot writing back. The owner is the exception, because HubSpot says it can only be two-way. To stop the loop, make one system the only place that sets the owner.
4. The check
Turn on field history for the lead owner. Group recent changes by who made them. The steps are in the sync overwriting the owner. See also leads owned by the integration user.
The nightly report counts leads owned by the integration user. The free scan reads your Salesforce rules and flows.
The free scan cannot count who changed each owner. It checks the setup behind it.
Questions
How does the HubSpot Salesforce connector pick a lead owner?
It sends a HubSpot owner only if a Salesforce user has the same name and email. Otherwise Salesforce assignment rules apply on the first sync.
Can I stop HubSpot changing the owner back?
HubSpot says the owner mapping can only be two-way. Make one system the only place that sets the owner.
Have it checked every night instead.
Routing Forensics connects as a read-only user and checks this, and the rest of your routing, against your real leads. Three design partners get a free health report on their own CRM, free for 90 days: what is leaking, where, and what it is worth. Apply for a place.
The free scan cannot count who changed each owner. It reads your routing setup in your browser. Scan your Salesforce or HubSpot routing. The nightly check, open to design partners, counts it.