Sync patterns
Direction, key, and a winner.
A sync pattern is the rule for one flow: which object, which way, what identifies a match, and what happens when both sides changed.
| Pattern | Use it when | The winner |
|---|---|---|
| One way in | Invoices, inventory, legal names | The system that already holds them |
| One way out | A closed deal the ERP should see | HubSpot, for that event only |
| Two way | A field with one owner on each side | Named per field, never “both” |
| Order to one record | A cart should stay a cart | The order id |
Email is a key, not a field both sides edit. Rate limits mean you batch, back off, and log the skipped call. A retry loop is how a portal gets flooded.
Two systems writing the same field will not take turns. One of them will win by accident.
Conflict
A key you did not write down is a key the connector chose.
Match