You're leaving Affinity. The deals move easily—Affinity exports pipeline and opportunity data in clean CSV. But the relationship graph doesn't travel. Those multi-threaded connections between companies, individuals, roles, deal influence, and historical interactions? They flatten to a contacts list. Most teams discover this when they're halfway through the first week in the new CRM and realize they've lost the mental map of who talks to whom. This guide walks through a realistic 60-day migration from Affinity to Orin that preserves relationship depth where it matters and rebuilds systematically where it doesn't. We'll show you which data actually exports, which requires manual work, how much labor it costs, and when Orin's native relationship capabilities let you stop exporting and start building. What Affinity Exports (and What It Doesn't) Affinity's export pipeline is straightforward but relationship-shallow. The platform gives you CSV downloads for: Contacts — name, email, phone, title, company, custom fields Companies — legal name, domain, industry, location, custom fields Opportunities — deal name, amount, stage, close date, associated contacts Activity logs — calls, meetings, emails with timestamps What doesn't export at all: Relationship vectors — who introduced whom, influencer vs. decision-maker distinction, warm paths to contacts Deal influence metadata — secondary contacts, stakeholder maps, veto power Interaction context — notes attached to specific relationships (not contacts), discussion threads, relationship sentiment Graph structure — Affinity's core product is the relationship graph itself; the CSV export is a flat projection of it The math is brutal: Affinity's value lives in what it doesn't export. Every relationship you want to preserve requires manual reconstruction. Phase 1: Assess and Audit (Days 1–10) Before you export anything, map what you're actually keeping. 1. Count your active relationships Log into Affinity. For each of your open deals, count the number of contacts tied to that opportunity with interaction history. This is your real data volume. If you have 50 open deals with an average of 4 engaged contacts per deal, that's 200 relationships to document. If half of those have warm introduction paths, you're looking at 100+ manual relationship notes to recreate. 2. Audit custom fields Export a sample of 10–20 contacts and opportunities. Check which custom fields are actually populated and which are cargo-cult fields no one uses. This matters because you'll need to recreate these fields in Orin, and unmapped custom data is wasted effort. 3. Identify your relationship power users Talk to the two or three reps who live in Affinity's graph view. Ask them: which relationships do you reference most? What connections would you lose if we flattened to a contact database? Their answers tell you where manual reconstruction is actually worth the labor cost. 4. Calculate opportunity concentration Pull a count of how many contacts are on each deal. If 70% of deals have 1–2 contacts, your relationship risk is lower. If deals average 5+ multi-threaded contacts, you're migrating relationship depth that matters operationally. Phase 2: Data Export and Structuring (Days 11–25) Export your Affinity data in this order: Step 1: Companies first Export your company list from Affinity. Verify domain formats, clean up duplicates (Affinity sometimes creates them), and standardize any custom fields. This file becomes your company master list in Orin. In Orin, import this directly into the CRM's company database . Step 2: Contacts and their opportunity mapping Export contacts and opportunities separately, then create a lookup table in a spreadsheet: Contact ID → Opportunity ID → Role/Title on that deal. This is your relationship map skeleton. Most teams use a Google Sheet at this stage because it's fast to edit and audit. Step 3: Activity and interaction history Export your activity log (calls, emails, meetings). Keep timestamps. You'll use this to reconstruct relationship timeline context in Orin—specifically, which contacts have interacted and how recently. Most teams don't migrate the full activity log; they migrate a summary: "Last contact 2024-11-15" rather than every individual touch. Step 4: Create a relationship inventory For each open deal, create a simple spreadsheet row: Deal ID Deal name Primary contact Secondary contacts (comma-separated) Warm introduction path (if known) Relationship quality notes (1–2 sentences max) This spreadsheet becomes your migration playbook. You'll use it to manually recreate relationship depth in Orin in Phase 3. Phase 3: Build Relationship Depth in Orin (Days 26–50) Import your core data—companies, contacts, opportunities—into Orin's CRM platform . Orin handles bulk imports and will map standard fields automatically. Reconstruct multi-threaded deals For each open deal with 2+ contacts: Add all contacts to the opportunity record in Orin Use Orin's contact role field