Affinity's power lives in its relationship graph: the ability to see that Sarah in procurement knows James in finance, that both have flagged your product in a board deck, and that your CEO met Sarah six months ago. When you export that data, the graph collapses. You get contacts and deal records. You don't get the layers that made Affinity worth paying for. Migrating from Affinity to Orin's CRM is not a copy-paste job. It requires mapping what actually exports, accepting what gets orphaned, and deliberately rebuilding the relationship depth over 60 days with checkpoints to catch gaps. This guide walks you through it. What Affinity exports—and what gets flat Affinity's standard data export includes: Contacts: Name, email, phone, title, company affiliation Companies: Name, domain, location, revenue band, industry tag Deals: Deal name, value, stage, close date, owner Interactions: Call logs, email threads, meeting notes (as text attachments) What does not export: Relationship strength scoring: Affinity's AI-generated "relationship health" metrics are proprietary and don't port. You lose the quantified signal for who your warmest contacts are. Multi-contact deal associations: Affinity links multiple stakeholders to a single deal with role tags (economic buyer, champion, influencer). Most CRM exports flatten this to a single owner field. Interaction linkage: Affinity's timeline ties emails, calls, and meetings to specific contacts and deals. In export, these become detached notes or lose the deal context entirely. Inferred relationships: Affinity's graph infers that two contacts know each other because they appeared in the same meeting or email thread. These inferences are lost. Custom relationship metadata: Fields like "last valuable interaction," "deal sentiment," or "relationship risk" (if you built custom ones) often don't migrate cleanly. The hard truth: Affinity exports 50–60% of the data that made your pipeline visible. The relationship depth—the thing you paid for—requires manual reconstruction. Why this matters: Three ways relationship loss hurts your pipeline 1. Forecast blindness. Without relationship scoring, you can't quickly surface which leads are warm. You'll re-qualify deals you thought were solid and miss the early signals of deals slipping. Expect to spend 20–30 hours in the first 90 days re-scoring existing opportunities. 2. Stakeholder amnesia. If your Affinity export flattens five stakeholders per deal into a single owner field, your reps will call on the wrong person, miss buying committee dynamics, and lose deals to competitors who have a complete picture. 3. Interaction context loss. Sales cycles live in the conversation history. An email from a prospect flagging objections, a call note saying "budget approved in Q2," or a meeting recording where the CFO said yes—these disappear if your migration doesn't deliberately re-attach them to the right deal and contact. The 60-day migration roadmap Days 1–7: Export, audit, and map Export your Affinity data in CSV format. You'll get at least four files: contacts, companies, deals, and interactions (or engagement logs). Audit contact counts: Compare Affinity's contact total to the exported CSV row count. If you have 8,000 contacts in Affinity but the export has 7,200, find out why (inactive contacts, deleted records, or export limits). Work with Affinity support if the gap is > 5%. Check deal completeness: Count deals by stage in Affinity's UI. Export the deal CSV. Verify that each stage's count matches. Look for deals with no close date, no value, or no owner—these are red flags for incomplete records that will confuse your new CRM. Sample interaction export: Pull 50 random interactions (calls, emails, meetings) and verify they include the prospect's name, the date, a summary, and a link back to the deal. If interactions export only as unlinked notes, you'll need a plan to re-attach them in Orin . Document custom fields: List every custom field you built in Affinity (relationship health, deal risk, champion name, etc.). Mark which ones are critical to replicate in Orin and which you can let go. This is where you'll lose 10–15% of metadata but avoid bloating your new schema. Days 8–14: Design your Orin contact and deal model Before you import anything, design your new structure. Affinity's graph was built for relationship mapping; Orin's CRM is built for sales operations. They're different. Multi-stakeholder deals: In Orin, create a custom "Stakeholder" or "Buying Committee" object that links multiple contacts to a single deal with fields for title, influence level, and relationship status. Import Affinity's multi-contact associations here. If your Affinity export only has a single owner per deal, plan to manually add secondary stakeholders for your top 100 deals in week 3. Relationship scoring: Build a custom "Relationship Health" field in Orin (dropdown: warm, neutral, cold, dormant). Do not try to port Affinity's numerical score; instead, w