You've built your deal network in Affinity. Hundreds of relationships. Warmth scores. Connector maps that show you who can introduce you to whom. Then you decide to move to Orin, export your data, and open the CSV. What you get back is names, emails, companies—and almost nothing else. Affinity's relationship depth is its core value. That depth does not survive export. When you migrate, you lose roughly 40% of what made your graph useful. For wealth advisors and relationship-heavy sales teams, this is not a minor inconvenience. It's a reconstruction project. This playbook shows you exactly what orphans, why it orphans, and how to rebuild the warmth and connector data in Orin's CRM in 60 days without losing deal continuity. The nine relationship fields Affinity doesn't export Affinity tracks nine relationship dimensions that have no native home in a CSV export: Warmth score – The algorithmic rating (1–5) of relationship strength based on interaction frequency, recency, and bidirectionality. Exports as metadata that Orin's import cannot read. Interaction history timeline – The list of emails, calls, and meetings that fed the warmth score. CSV includes contact history fields only. Connector strength and type – Not just that Person A knows Person B, but how strong that connection is and whether it's a direct introduction, shared experience, or mutual contact. Export flattens to a text note if at all. Bidirectionality flags – Whether both parties have each other in their network (mutual) or if it's one-directional. No export field. Relationship origin metadata – How the relationship began (warm intro, cold outreach, shared client, conference). Lost on export. Priority/VIP markers – Custom relationship importance tags. Not mapped to standard CRM fields. Interaction sentiment and context tags – Notes on whether the last interaction was positive, neutral, or stalled. CSV notes field loses the structured tagging. Shared organization networks – Affinity maps people within the same company and across portfolio companies. These mapped relationships export as flat contact lists only. Relationship decay alerts – Affinity flags relationships that haven't engaged recently and suggests re-engagement. Export has no activation logic. The result: you export a contact list and a chronology of emails, but you lose the quality graph —the signal that tells you which relationships are actually warm and actionable. Why export breaks relationship data The CSV standard has no fields for relationship semantics. Affinity's warmth algorithm, connector strength, and interaction sentiment live in Affinity's application layer—they're not stored as importable fields. When you export, the system treats the graph as a detail that enhances the contact record, not as data in itself. A contact record in CSV is flat: first name, last name, email, company, phone. Relationship metadata would need to be encoded as text in a notes field, which means it loses queryability and structure. Most CRM import tools (including Orin's initial data load) read relationship data only if it comes as a specific "related contact" or "relationship type" column—Affinity's export doesn't produce that shape. The math: If Affinity tracks 9 relationship fields per contact pair and you export 600 contacts with an average of 15 relationships each, you're exporting contact records but orphaning roughly 40% of the data that made those relationships valuable—the warmth, the strength, the decay signals. What survives the export (and how to use it) Not everything is lost. Use what does export as your foundation: Contact records: Names, emails, companies, titles, phone numbers. All clean. Deal associations: Which contact is linked to which deal. This is critical; it survives. Email and meeting history: A flat log of all touchpoints with timestamps. No sentiment, but you can read the cadence. Custom fields you created: Any fields you manually added (e.g., "Source," "Net Worth," "Portfolio Company") export as-is. List/segment membership: If you tagged contacts in Affinity lists, those come through if your import maps them correctly. The email history is your most valuable orphan recovery tool. A contact with 47 emails over 18 months is warmer than one with 3 emails over 2 years. You'll use this signal to re-score warmth in Orin. Rebuilding warmth scoring in Orin: the 60-day plan Warmth in Orin is not algorithmic out of the box; it's a field you configure and populate. You have two paths: manual review or AI enrichment. For relationship-heavy teams migrating from Affinity, a hybrid is fastest. Phase 1: Baseline scoring (week 1–2) Create a custom "Warmth" field in Orin as a dropdown or numeric scale (1–5). Import your contact data as normal. Then review your exported email history. Contacts with 40+ emails in the last 12 months → Warmth 5 (very warm). Contacts with 15–39 emails → Warmth 4 (warm). Contacts with 5–14 emails → Warmth 3 (neutral). Contacts with 1–4 emails → Warmth 2 (cold)