Checked 31 August 2026
Clarify and HubSpot: what actually syncs
Clarify's integrations page describes a two way sync. Clarify's own documentation says it is one way. The documentation is the operative statement, it is dated more recently, and the difference decides whether you can run both systems side by side or have to pick one.
The discrepancy, in both parties' own words
We are not paraphrasing either one. Both are quoted and both are linked.
The integrations page says
"Keep Clarify and HubSpot in a two-way sync so contacts, companies, and deals stay current in both systems automatically."
The help documentation says
"One-way synchronization. Changes made in HubSpot automatically update in Clarify. Updates made in Clarify will not sync back to HubSpot. Bi-directional sync is on the roadmap."
Treat the documentation as correct. It is the more specific of the two, it carries a date, and it names the limitation against its own product, which is not the direction marketing copy usually errs in. The help article was updated 22 July 2026.
None of this is dishonesty. A roadmap item gets written into marketing copy early and the docs catch up later. But if you plan around the integrations page you will build something that quietly does not work.
Sources: clarify.ai/integrations and the HubSpot import article, both read 31 August 2026. Worth re-checking, because the roadmap item may well have landed by the time you read this.
What crosses, in the direction it does cross
HubSpot to Clarify is thorough. It is the return leg that does not exist.
| Object | What comes across | Goes back? |
|---|---|---|
| People and contacts | Names, email addresses, custom fields | No |
| Companies | Names, domains, descriptions, custom fields | No |
| Deals | Names, amounts, stages, close dates, custom fields (optional) | No |
| Relationships | The connections between contacts, companies and deals | No |
| History | The initial import brings your historical HubSpot data, then it keeps up | No |
Standard fields map automatically. Custom fields can be mapped, and Clarify's own advice is worth repeating: build the custom fields in Clarify before you run the import, so there is somewhere for the HubSpot values to land. Doing it afterwards means a second pass.
Source: docs.clarify.ai, HubSpot import, updated 22 July 2026.
What one way actually means for you
HubSpot stays the system of record
Marketing keeps running in HubSpot, your reps work in Clarify, and Clarify reads. Nothing your team does in Clarify has to reach HubSpot for this to be useful.
You are moving, in stages
Fine, as long as the direction of travel matches the sync. Anything typed into Clarify during the overlap lives only in Clarify, so the cutover date is the date HubSpot stops being true.
Both systems, both edited
If anyone updates a deal stage in Clarify and anyone reads that stage in HubSpot, they will disagree, silently and permanently. Pick one place where the truth is written.
If you need the return leg today
The sync does not do it. Three things will, in rising order of effort.
Zapier, for the simple cases
Clarify's Zapier app carries real triggers, including Record Updated, so a change in Clarify can push a HubSpot update. Good for a handful of fields. It is not a sync, it is a set of rules you maintain.
Under an hourWebhooks, if you want events rather than polling
Clarify supports outbound HTTP webhooks, so your own service can receive real time events and write to HubSpot. More work, and far more reliable than a pile of Zaps once there is more than a few fields.
A day or twoThe API, if the mapping is genuinely yours
Read and write against records, workspace users and meeting data with a Workspace key. This is the honest answer when the field mapping has business logic in it rather than being a copy.
Scoped per case
Trigger list from the Zapier article; API detail from the Clarify API article. Both read 31 August 2026.
Common questions
Is the Clarify HubSpot sync two way or not?
One way as documented on 22 July 2026: HubSpot to Clarify only. The integrations page describes it as two way, and Clarify's own help article says bi-directional sync is on the roadmap. Check the help article rather than the marketing page before you plan around it.
Can I run HubSpot and Clarify at the same time?
Yes, if HubSpot remains the place changes are written. The moment both are edited they drift, because nothing carries a Clarify edit back.
Does the import bring my historical HubSpot data?
Yes. The initial setup imports history, then ongoing updates keep Clarify current with HubSpot changes.
Do custom fields come across?
Standard fields map automatically and custom fields can be mapped. Create the matching custom fields in Clarify first or the values have nowhere to land.
Is deal sync included?
Deals sync with names, amounts, stages and close dates. Custom fields on deals are marked optional in the documentation, so confirm that in setup rather than assuming it.
What about Salesforce?
Clarify describes the Salesforce integration as bi-directional across accounts, contacts, opportunities and activity. We have not verified that against documentation the way we did HubSpot, so treat it as their claim until you have.
Where we come in
We make the two systems agree, or we pick one
Running both is fine right up until two people edit the same deal in different places. We decide where the truth is written and build the wiring that keeps everything else reading it, rather than syncing.
- A decision on which system holds the truth, made once and written down
- The HubSpot import mapped to fields that exist before the import runs
- The return leg built where you genuinely need it, through Zapier or the API
- A cutover date, so nobody is guessing which system is current
Free, no call required
The Clarify setup guide
Not ready to talk to anyone? Take this instead. One email, nothing else unless you ask for it.