Affinity's relationship graph is its selling point—every introduction, every shared deal, every email thread creates a node in a living web of connections. When you export that graph, it collapses. A CSV shows you a flat list of contacts and their basic fields. The relationships that made Affinity useful? Gone. You're left with names, titles, and phone numbers, orphaned from the context that made them valuable. The difference matters. A contact who influenced a $500K deal three years ago is not the same as a contact you've never met. A person who bridges two business units in your network has different leverage than an isolated stakeholder. Affinity's graph knew this. Your CSV doesn't. This guide walks you through a 60-day process to rebuild relationship depth in Orin's CRM without losing the connective tissue that made your Affinity data work. You'll identify key connection points, map hidden relationships back into your system, validate data integrity, and test deal-to-person associations before you flip the switch. Understand What Affinity's Export Actually Loses Before you migrate, you need to know what you're losing. Affinity's graph-based model captures three types of relationships that don't survive a standard CSV export: Influence depth: Which contacts actually shaped a deal outcome, and when. Your CSV shows a deal and a contact list, but not who spoke in the final board meeting or whose email unblocked a stalled negotiation. Cross-company bridges: Affinity maps people across organizations (a founder who moved from a customer to a partner, a champion who jumped to a competitor). CSV export treats each company instance as a separate record, orphaning the history. Interaction sequences: When Affinity shows you a contact, it pulls threads: who introduced them, what deals they touched, what historical context exists. CSV gives you contact fields only. Most migrations miss this entirely. They treat CSV import as a simple data move: contacts in, deals in, done. Three months later, sales teams find themselves re-learning who knows whom, which introductions are warm, and why certain accounts matter. Audit Your Affinity Export: The 14-Day Baseline Start by running a complete relationship audit against your Affinity export before you touch anything in Orin. You're mapping what survived and what didn't. Step 1: Export Affinity's Complete Graph Affinity's native export gives you two files: Contacts.csv: All contact records with standard fields (name, title, company, email, phone, custom fields). No relationship metadata. Organizations.csv: Company records and their linked contacts, but not the influence or introduction weight. Download both. This is your baseline. Step 2: Map the Hidden Relationships You're Losing Open Affinity and run these three reports to find the relationships your CSV is hiding: Deal influence report: For your top 20 closed deals (by size and recency), list every contact touched. Note which contacts appear in deal notes, email threads, or meeting attendees. Mark who was a decision-maker, influencer, or introducer. Your CSV shows a deal ID and a contact list; this report shows you the role and timing. Multi-touch contact report: Identify contacts who appear in 3+ deals. These are your network hubs. In CSV form, they're just repeated rows. In Affinity's graph, they're high-value nodes. Export the deal IDs and dates each contact touched. Cross-company movement report: Find contacts who moved between organizations in your database. Pull hire dates, previous roles, and which deals they touched at both companies. Your CSV will show two separate contact records; you need to know they're the same person. Export or print these reports. You'll use them to rebuild depth in Orin. Map Relationships in Orin Using Custom Fields and Deal Records Orin's CRM graph works differently from Affinity's model, but it's more flexible. You can encode relationship depth explicitly, making it searchable and reportable. Here's how. Create a Relationship Metadata Layer Before you bulk-import contacts, create four custom fields in Orin to capture relationship context: Deal Influence (multi-select): Identifies which deals this contact shaped. Options: Decision-Maker, Influencer, Introducer, Technical Evaluator, Budget Owner. This is your role field. Relationship Strength (dropdown): Encodes trust and leverage. Options: Direct (you've met), Warm (introduced via mutual), Cold (inbound), Unknown. Affinity showed this implicitly; you're making it explicit. Network Hub (checkbox): True if this contact appears in 3+ active deals. Flags high-leverage nodes. Affinity Relationship Index (short text): Stores the ID or timestamp from your Affinity export. Useful for auditing and backward reference if you need to re-check source data. These fields become your relationship depth in Orin. When a sales rep searches for a contact, they now see not just a name but the explicit context that made Affinity valuable. Rebuild Deal-to-Contact