When you export from Affinity, you get a flat file. Contacts, organizations, and the threads that connect them arrive in your new system as separate, often disconnected entities. The deal context evaporates. Relationship history fragments. A contact who closed three deals with one buyer suddenly appears as isolated rows with no trace of the prior relationship or the decision maker who made it happen. This isn't a technical failure—it's the nature of how Affinity structures its data. Relationships, influence maps, and deal chains live in Affinity's relational database, but they don't translate cleanly to CSV. If you're migrating to Orin's CRM or Pipedrive , you'll need a deliberate 60-day rebuild process to restore what the export can't carry forward. What survives the export—and what doesn't Affinity's export delivers these core fields intact: Contact name, email, phone, title, company — the surface layer Organization details — revenue, location, stage, subtype Interaction history — dates, notes, event records (if you include them) Custom fields you've defined — any text, dropdown, or numeric field Tags and lists — usually exported as comma-separated values What dies in transit: Relationship mapping — the "person A influenced person B" connections Deal ownership clarity — who owns the relationship vs. who owns the deal Influence chains — the documented path from initial contact through buying committee Contact-to-contact relationships — peers, referrers, decision influencers Historical deal associations — which contact drove which closed deal and when Account mapping depth — org hierarchies, parent-subsidiary links The painful truth: you can recover the facts, but the narrative gets fragmented. A contact exported with a note "met at conference, referred to CFO Sarah Chen" tells you there's a relationship, but your new system won't automatically link you to Sarah or flag that the referral came from this person. The 60-day rebuild framework: phases and priorities Don't try to rebuild everything at once. Prioritize by deal impact and recency. Days 1–14: Baseline import and audit Export from Affinity cleanly. Include all custom fields, tags, and interaction history. Disable any fields you know are broken or unused—they add noise to the mapping work. Map fields to your new platform. Affinity's "Title" becomes "Job Title" in Orin. "Organization" becomes "Account." Custom fields often need renaming. Document every mapping in a spreadsheet. Run a sample import (50 contacts, 5 organizations). Check for data loss, character encoding issues, or field overflow. Fix the mapping before full import. Import the full base. Assign all contacts and orgs to a holding owner or queue for review. Audit the result. Count imported contacts, orgs, and deals. Spot-check 10 orgs to see if relationships are present in notes or custom fields. Document what's missing. Days 15–30: Restore active deal relationships Focus only on deals in flight or closed in the last 90 days. These have the highest revenue impact and the freshest recall. Export your pipeline from Affinity as a separate CSV. Include deal name, stage, amount, close date, and all associated contacts. For each deal, manually verify the contact chain in your new system. Is the primary contact linked to the deal? Are influencers and decision makers present as contact records? Are they linked to the deal or just mentioned in notes? Create missing relationships. If a contact is mentioned as "champion—referred by John at Acme," but John doesn't exist as a separate contact or isn't linked to the deal, create him now and link both to the deal record. Use a standard field for relationship type. In Orin or Pipedrive, add a field called "Role in Deal" (Contact, Decision Maker, Influencer, Champion, Economic Buyer, etc.). Populate it from your notes and Affinity history. Link decision chains. If Sarah (CFO) reports to Tom (COO), and Tom owns the budget, create that hierarchy in your account. Use org fields or custom relationship fields to document it. Days 31–45: Recover lost contact-to-contact relationships Many of your best opportunities come from referrals and warm intros. Affinity's data often captured these as notes or tags. Extract them. Search your interaction history for relationship markers. Terms like "referred by," "introduced to," "works with," "reports to." Flag them. Build a referral/relationship matrix for high-value accounts. If Account Acme has 12 contacts, map who knows whom. This lives in notes or a custom multi-select field in your CRM. Create explicit "Relationship" records if your platform supports them. Orin's contact and deal tracking lets you link contacts within an org. Use this to document peer, reporting, and referral relationships. Audit completed deals for missing relationships. Did you close a deal with Acme in the last two years? Search for all contacts at that org, cross-reference the deal notes, and recreate the buying committee in your system now. You'll