Customers
HubSpot sync
Two-way, with one side owning each object — and everything works exactly the same with no HubSpot at all.
If your customers are in HubSpot and staying there for now, contacts, companies and deals sync both ways. If they are not, nothing here behaves differently: the sync is a connection you make, not a mode the product runs in, and every screen works the same with it switched off.
One side owns each object, and the other is told why
Not last-write-wins. Two systems each convinced they are right about a phone number will flip it back and forth every fifteen minutes, and nobody watching either screen can tell what is happening. Where a record is owned elsewhere the field is read-only here and says which system holds it.
What makes it possible at all
Every record has carried sync identifiers since the first migration — before there was a sync to use them. That is the part that cannot be added afterwards: identifiers on records already synced have to be reconstructed by matching, and matching is exactly the thing that creates duplicates.
Where it defers
- A merged-away record is followed, never updated. A pointer is not a destination, so an incoming change lands on the person who survived.
- Where both records were synced, the remote pair is reported rather than fought over. Only the connected system can resolve two of somebody in its own database.
- An erased contact is not recreated. The sync identity goes with the erasure, and the suppression list refuses the address if a fresh record arrives carrying it.
Marketing automation is not synced, because it is not here
Email at volume, landing pages, ad management and workflows stay in HubSpot. That half is a marketing platform rather than a CRM, and it is not something this product intends to replace.