Bi-directional keeps both systems current but needs conflict rules; one-way is simpler and safer for fields with a clear owner. Best practice: bi-directional for contact/account state, one-way for enrichment (turgo→CRM) and opportunities (CRM→turgo).
Bi-directional
Changes on either side propagate to the other, with the conflict rule (most-recent-wins default) resolving simultaneous edits. Right for fields both systems legitimately update: contact ownership, lifecycle stage, engagement status.
One-way turgo → CRM
Enrichment data should flow one way: turgo's provenance-tracked values overwrite CRM blanks and staleness, and manual CRM edits to those fields shouldn't flow back to pollute the Golden Record.
One-way CRM → turgo
Opportunities and deal stages are CRM-owned: turgo reads them for context and triggers but never writes deal state. This keeps the CRM the uncontested system of record for revenue.
Configure per object and field
Direction is set per object with per-field overrides in the mapping screen. When in doubt, start one-way and open up later — loosening is safer than untangling a bad bi-directional sync.
