You set up bi-directional sync between Affinity and Google Contacts expecting seamless flow: your wealth team adds a prospect to Affinity, it appears in Gmail, someone finds them in Google Contacts and updates a field, it syncs back. Clean. Organized. Instead, you get duplicate contacts, missing relationship notes, collapsed custom fields, and a data graveyard that takes someone 3 hours to untangle every Friday. The problem isn't that syncing exists—it's that Affinity and Google Contacts are fundamentally different beasts. Affinity is built for relationship intelligence: notes, interaction history, relationship mapping, custom fields that track deal context, investor sentiment, follow-up urgency. Google Contacts is a flat phone book. When you sync between them, the richer tool's depth dies on arrival. Why the sync breaks your data Affinity stores relationships as multi-dimensional objects. A single contact record might hold: Interaction notes ("Partner is skeptical of revenue assumptions, prefers monthly updates") Relationship history ("Met at Demo Day 2023, warm intro from Sarah") Custom fields (Deal stage, investor type, check size, co-investment preference) Activity log (Last call, last email, next touchpoint) Relationship map (connections to other contacts, entity affiliations) Google Contacts speaks a simpler language: name, email, phone, company, job title, a few notes field, maybe custom labels. When Affinity pushes to Google Contacts, custom fields either map to the notes field (collapsing readability), disappear entirely, or create orphaned data that syncs back malformed. Worse: Google Contacts doesn't understand Affinity's relationship hierarchy. If you have both a contact record and an entity record for the same person (common in wealth management), Google Contacts sees them as separate. Sync them both, and you now have two copies of John Smith in Gmail—one pulling from the contact, one from the entity. The duplicate avalanche Bi-directional sync creates a specific type of duplicate problem: the same person exists in both systems, but their identifiers don't match perfectly . A contact in Affinity might be listed as "John Smith" with email john.smith@fund.vc. Google Contacts captures "J. Smith" from an old Gmail signature. The sync engine doesn't recognize them as the same person. Both sync. Now your Gmail autocomplete shows John Smith twice. Sales rep emails the wrong one. You discover it two weeks later when follow-up fails. Duplicates also cascade when your team manually maintains both systems. Someone adds a contact to Google Contacts directly (not through Affinity)—maybe a quick meeting grab from a business card scan. The next sync pulls it into Affinity as a new record. Someone else, not knowing it exists, creates another Affinity record for the same person from your email history. You now have three versions of the same person across two systems. Merging them later is manual, painful, and lossy. Affinity doesn't automatically merge the activity logs. You have to choose which version to keep and manually review three records' worth of interaction history to rebuild a complete picture. Custom fields collapse into a notes graveyard Affinity's custom fields are how wealth teams track deal-critical context: investor stage (prospect, warm, committed, passed), check size, portfolio focus, decision timeline, co-investment appetite. These fields filter your pipeline, automate follow-ups, and drive your forecast. Google Contacts doesn't have custom fields in the same way. The sync either: Maps them to the notes field —your carefully structured data becomes free text, unsearchable, unusable for automation or reporting. You can't filter "all Series A investors open to co-invests" anymore; you have to read notes. Drops them entirely —the field syncs one direction only, and any updates in Google Contacts don't pull back to Affinity. Your team updates a deal stage in Gmail, it disappears when they return to Affinity. Creates phantom fields —the sync tool creates a "custom fields" column in Google Contacts with raw JSON or concatenated text, unreadable and unmaintainable. The worst case: your team relies on Google Contacts as a quick reference during calls (Gmail integration makes it fast), updates a field there, assumes it syncs back, but doesn't. Affinity shows stale data. A follow-up gets scheduled for the wrong date. A deal moves to the wrong stage in your forecast. Relationship depth evaporates Notes are how wealth teams document decision criteria, objections, and relationship context. "Met at TechCrunch Disrupt, introduced by Sarah from Benchmark, expressed interest in B2B SaaS but skeptical of unit economics" is how you remember why this investor matters and what to emphasize next time. Affinity's notes are relationship objects—they store context, emotion, timeline. Google Contacts' notes field is a text box. Sync Affinity's rich notes to Google Contacts, and they truncate, they're unstructured, th