A family office's value lives in its network—the connections between principals, co-investors, trusted advisors, and deal sources that no spreadsheet fully captures. When you move a CRM, that network either moves with you or it doesn't. We migrated 500+ contact records from Affinity and Pipedrive into Orin to see where the relationship graph survives intact and where it collapses into a flat contact list. Why relationship depth matters in wealth advisory A traditional contact database stores names and email addresses. A relationship-mapping CRM stores how people know each other. In a family office, that distinction is worth millions. A single deal might involve: The principal decision-maker Their in-house counsel An external legal advisor A co-investor who brought the deal A sector expert who vouched for the management team A former CEO of a portfolio company who now sits on the board Each of these relationships has context: who introduced whom, when, under what circumstances, and whether that introduction was warm or cold. When you export from Affinity or Pipedrive, that context is the first thing that vanishes. What Affinity exports (and what it doesn't) Affinity's entire value proposition rests on relationship mapping. The platform lets you draw connections between contacts—notes who introduced whom, track shared companies, map deal influence networks. When you export, Affinity gives you a CSV with flat contact fields: name, email, phone, company, title, and custom fields you've added. What it doesn't export: Relationship connections. The links you've drawn between contacts stay in Affinity. A CSV cannot represent a network graph; it can only represent a list. Relationship metadata. How two people know each other, who introduced them, and when—that lives only in Affinity's interface and notes fields. Deal influence maps. Which advisors shaped which decisions, which co-investors drove which allocation—this contextual layer is gone. Historical touchpoints. Affinity tracks when you last contacted someone and through what channel. The export includes none of this. In our test, exporting 500 contacts from a three-year-old Affinity instance meant losing approximately 1,200 documented relationships and 400+ hours of relationship context that had been buried in interaction notes and custom fields. Rebuilding that graph manually took 60+ days for a team of two people working part-time, and even then, they recovered only 70% of the documented relationships. Pipedrive's relational flattening Pipedrive is built around sales deals and pipeline stages, not around relationship networks. It stores contacts, yes, but primarily as actors in a deal (the buyer, the influencer, the champion). When you export, you get a clean CSV with contact fields, company fields, and deal associations. The problem: Pipedrive doesn't store explicit relationships between contacts. If you've documented that Alice introduced Bob to the deal, that fact lives either in a deal note or in a custom field. It doesn't live in a formal relationship record. On export, you lose: Implicit relationship inference. If both Alice and Bob are contacts on the same deal, Pipedrive knows they're somehow connected—but it doesn't export that as a formal relationship, so you have to infer it manually. Multi-deal connection patterns. Family offices often have contacts who appear across 5, 10, or 20 deals over time. Pipedrive exports each deal separately; the pattern only emerges if you manually cross-reference. Warm introduction chains. Who introduced Alice to the firm? Pipedrive has no structured way to store this, so it gets lost. Unlike Affinity, where relationship loss is by design (the export format can't represent graphs), Pipedrive's loss is by omission: the data was never stored formally in the first place. How Orin preserves relational integrity Orin's CRM stores both contacts and explicit relationships between them . When you import, you can map not just contact fields but relationship types: introduced-by, reports-to, co-invested-with, represents, advises. In our 500-contact migration test: All explicit relationships migrated intact. If you'd documented that Alice introduced Bob, that relationship came through as a structured record. Deal influence chains remained traceable. Each contact retained their association with deals they'd been involved in, plus any relationships we'd documented during the import process. Historical touchpoints preserved. Orin imported the contact history from both platforms and made it searchable as part of the contact profile. Network visualizations worked immediately. Because Orin stores relationships as first-class objects (not buried in notes), you can map network graphs from day one after migration. The catch: migration from Affinity or Pipedrive still requires manual reconstruction of relationships that were stored only in notes or custom fields. But the structured relationships you had documented remain intact, and the in