Conflicts happen when both systems change the same field between syncs. The default most-recent-wins rule resolves silently and logs; field-level rules can prefer a side; unresolvable structural conflicts queue for human review.
The default rule
Most-recent-timestamp wins, applied per field (not per record — different fields can resolve differently). Every resolution is logged with both values retained in provenance.
Field-level authority
Override per field: "CRM always wins" for rep-owned fields (owner, notes), "turgo always wins" for enrichment fields. Set in Field Mapping → Conflict Rules.
Human-review queue
Structural conflicts — merge disagreements, type mismatches, records deleted on one side and edited on the other — can't auto-resolve. They queue in Integrations → Conflicts with side-by-side views and one-click resolutions.
Reducing conflicts
Chronic conflicts on a field usually mean two teams both think they own it. Fix the ownership question organizationally, then encode it as a field-level rule.
