HubSpot and Notion integration: what to sync and which side is the source of truth

Sync only what the other team actually needs to see. Typically that is customer, company and deal basics from HubSpot into Notion for delivery and operations, and project status or onboarding progress from Notion back into HubSpot for sales and support.

Mirroring everything is the most common mistake. It doubles the places a mistake can hide and makes every field rename a problem. We start from a short list of fields, each tied to a decision somebody makes, and add more only when there is a reason.

HubSpot should own customers, contacts, companies, deals and anything sales or finance relies on. Notion should own project work, documents, tasks and delivery status. The rule that matters is that every field has exactly one owner, and the other tool only shows a copy.

We write this ownership list down with you before building. It becomes part of the documentation, so a new team member knows where to edit a field and where not to.

For a simple one-way copy, often yes. Ready-made connectors are cheap and quick, and we will tell you if one is enough for your case.

They tend to fall short when you need ownership rules, two-way updates, matching of existing records, or a record of what changed and why. That is where a custom integration pays for itself.

By matching on IDs, not on names. Each HubSpot record stores the ID of its Notion page, and each Notion page stores the ID of its HubSpot record, so an update always finds the exact record it belongs to instead of searching for a similar one.

The sync also recognises its own changes and ignores them, so an update that it just made in one tool does not bounce back and trigger another. Every sync action is logged.

One way for most fields, both ways for the few that two teams legitimately edit, such as a project status. One way is simpler and safer, and it is the right default.

For the fields that do run both ways, we agree a rule in advance about which side wins, so the integration never has to guess.

The owner of the field wins. The other edit is reverted, and the conflict is logged and flagged so a person can see it and decide, instead of data quietly disappearing.

This is why the ownership list matters. Without it, whichever tool saved last wins, which is how teams end up with a customer list nobody trusts.

Usually small changes made by people: a renamed Notion property, a new option in a dropdown that the other side does not know, a deleted or archived record, or either tool slowing down how fast it accepts changes.

We build checks for each of these and send an alert with the reason, instead of letting the sync stop quietly. A sync that fails without telling anyone is worse than no sync.

We have not published a HubSpot and Notion project, so we will not present one as a result. What we have done is HubSpot sync work: for a B2B services company we built a real-time two-way sync between HubSpot and Pipedrive with clear conflict rules, reaching zero discrepancies over 6 months, and the project paid for itself within 30 days.

That project did not involve Notion. The method carries over: one owner per field, matching by record ID, and written conflict rules.

Read the full case study → HubSpot work →

Clutch Top Company 2023 · Upwork Top Rated, $500K+ delivered · Fortune 500 work delivered under NDA. We do not demo. We deploy, with tests, monitoring, and documentation, the same way we have shipped 200+ times.