Affinity's relationship graph is built on connection—who knows whom, which contact led to which deal, how decision-makers relate to each other. That's the whole point of the platform. But when you export from Affinity, you get a flat file. Contacts. Companies. Deals. The connective tissue—the reason you picked Affinity in the first place—doesn't translate into a standard CSV. Move to Orin without a plan, and you'll land all your data but lose the context that made it valuable. This playbook walks you through a 60-day migration that preserves your relationship depth. You'll identify which connections matter most, map them systematically, and rebuild them in Orin before you go live. No orphaned records. No lost deal context. No starting over. Why Affinity's export doesn't capture relationship depth Affinity stores relationships as graph edges—Person A is connected to Person B, both are linked to Deal X, and the system tracks how that connection influenced the outcome. When you export, you get rows: contact name, email, company, title. You get deal records with their associated contacts. But the actual relationships—the 'why' and 'how' that made those connections meaningful—exist only in Affinity's internal model. A CSV can't express a graph. It can express a table. This is why most migrations from relationship-graph tools feel flat on arrival. You've preserved the entities, but not the logic that connected them. Orin's CRM pipeline model organizes around deals, contacts, and companies—a relational structure, but one that requires you to explicitly map connections. This isn't a limitation; it's the cost of portability. The good news: once you know which relationships matter, re-linking them is systematic and fast. The 14-day audit: Map your deal-contact topology Before you export anything, spend two weeks understanding your Affinity graph. Pull a deal export from Affinity for the last 12 months. Include deal value, stage, close date, and associated contacts. Don't filter yet. Identify high-context deals —those involving 3+ stakeholders, multi-stage approval chains, or deals that took 60+ days to close. These are your relationship-heavy records. Flag 20–30% of your deal set. Map the contact graph for each deal . For every high-context deal, document: who initiated? Who approved? Who did the champion report to? Who was the technical evaluator? These aren't just contacts; they're roles in a relationship network. Audit for phantom links . Affinity sometimes connects contacts who were never actually engaged—a person added to a thread but never part of the deal. These inflate your relationship map and clutter your re-linking work. Mark them for removal during migration. Document lost context . In Affinity, you might have a note that 'Maria introduced us to the CFO.' That note exists in a field somewhere. Before you migrate, extract those narrative connectors and store them separately. You'll need them during re-linking. Output: A spreadsheet with deal ID, high-value contacts, their roles, and the relational narrative. This is your re-linking roadmap. The 30-day re-linking sprint: Rebuild connections in Orin Now export your contacts, companies, and deals into Orin. The import will be clean—every record lands. But they're not yet connected the way they were in Affinity. Your re-linking sprint has three tracks: Track 1: Deal-to-contact associations In Orin, every deal can list associated contacts. Use your audit output to assign the right contacts to each deal. For high-context deals, assign all stakeholders. For simpler deals, assign only the primary contact. This takes 1–2 weeks for most migration sets (500–2000 deals). Use Orin's bulk import or automation rules to assign contacts based on matching criteria (same company, similar deal stage timing, historical close patterns). This accelerates re-linking and reduces manual error. Track 2: Contact relationship fields Affinity lets you link contacts to one another. Orin supports custom relationship fields on contacts—'Introduced by', 'Reports to', 'Champion at'—depending on your setup. In your 30-day window, populate these fields with the connective relationships you mapped during the audit. For each high-context deal, update the champion contact's record with links to supporting stakeholders. Use a standard naming convention: 'Introduced by [contact name]' or 'Technical approver: [contact name]'. Consistency here compounds during deal reviews—your team will immediately see how stakeholders relate. Track 3: Deal narrative fields Orin CRM deals can include deal notes, custom fields, and activity timelines. During re-linking, migrate the relationship narrative from Affinity into Orin deal notes. Example: 'Deal opened by inbound from Maria at Acme Finance. She reports to CFO James. Technical evaluation led by Platform team (contact: Alex Chen).' This prose context ensures nothing is lost in the transition. Assign this work to 2–3 team members who know your deals intimately