When you export Affinity, you get a CSV. When you look at it on screen, you see rows and columns. What you don't see is the shape of the graph that made Affinity useful in the first place: which person knows which person, which introduction bridged which deal, how a contact's company changed three times, why you met someone at a conference six months ago and what you promised them. The export flattens it all. And if you're migrating to a new CRM, that flatten happens once. Then you spend 60 days trying to rebuild signal from noise. This playbook walks you through what actually disappears, how to audit the wreckage, and a structured calendar to get your relationship depth back. What Affinity's export leaves behind A standard Affinity export gives you: name, email, phone, company, title, last interaction date. That's roughly 15 columns. But here's what's missing: Relationship tags and edges. Affinity lets you label how contacts know each other—"knows", "introduced by", "worked with". On export, those relationships vanish. You get a contact list, not a graph. Company linkages over time. A contact worked at Company A, then Company B, then started Company C. Affinity tracks that in its CRM layer. CSV does not. You lose the historical thread. Interaction history depth. Affinity logs every email open, meeting, call note, and note. Export captures only the last interaction date. Every conversation before that—context, promises, pricing discussed—lives only in Affinity's database. Organization structure. Who reports to whom at a prospect account. Who signed the contract. Which person is the budget holder. Export flattens the org chart to a list of individual names. Deal-to-contact mapping. Which contacts are on which deal, in which role (decision maker, influencer, evaluator). You can export deals and contacts separately, but the linkage is fragile and manual to rebuild. Lists and segments. Any manual segmentation you've built in Affinity (high-intent accounts, warm intros, stalled deals) does not port. You start from scratch. The export is a snapshot. The CRM is a living graph. You're moving from one to the other. The gap is 60 days. Days 1–14: Audit what you have and what you've lost Before you start rebuilding, you need to know the scale of the problem. Step 1: Pull your Affinity export Export all contacts , all deals , and all interactions as separate files. Most exports run within 24 hours. If you have more than 50,000 contacts, break it into date ranges (by last interaction or creation date) to keep files manageable. Step 2: Count relationships in the export that you're losing Open Affinity's relationship view and count: Total edges (A knows B) across your entire database. Export the relationship metadata if Affinity allows it; most don't, so you may have to count from the UI or ask Affinity support for a data extract. Contacts with more than 5 relationships. These are your key connector nodes. They'll be hardest to rebuild. Company mergers, name changes, or moves over the past 18 months. Track how many contacts belong to companies that have changed since you met them. Step 3: Identify high-value relationships to prioritize You're not going to rebuild everything in 60 days. Prioritize: Contacts on open deals (by pipeline value). Contacts who've replied to your last 10 emails or attended a meeting in the past 30 days. Contacts introduced by your best referral sources (other customers, board members, advisors). Contacts at accounts where you have multiple relationships (richest networks). Mark these as Tier 1. You'll rebuild these first and with full depth. Everything else is Tier 2 (rebuild with less detail) or Tier 3 (CSV only, link later if needed). Days 15–35: Load, clean, and reconcile data in your new CRM Now you're moving data into your new platform. Using Orin's CRM as your destination: Step 1: Load your contact export Map your Affinity CSV columns to Orin fields. Standard fields to map: First name, last name → Contact name Email → Email (deduplicate first; Affinity sometimes has duplicate emails) Phone → Phone Company → Organization (you may need to create or match to existing company records) Title → Job title Last interaction → Last activity date Set aside any non-standard fields (custom Affinity fields) in a holding area. You'll map these after the base load. Step 2: Deduplicate and reconcile Affinity data often has dupes. Run a dedup pass: Same email, different name capitalization → merge Same person, two company affiliations (old and new) → create a single contact with both companies, or decide if the old company is still relevant for the deal Bounced or invalid emails → quarantine or delete This alone takes 10–15 days if you have 10,000+ contacts. Orin's CRM can flag likely duplicates via API or bulk import settings; use those tools aggressively. Step 3: Load deals and map deal–contact relationships Export deals from Affinity with contact IDs if possible. Map to Orin deals and recreate the many-to