When you export Affinity, you get contacts and companies. What you lose is the graph—the interaction threads, the influence clusters, the nodes that show who's connected to whom and why. Affinity doesn't expose its relationship engine via API, and CSV export flattens everything into rows. If relationship depth is why you chose Affinity in the first place, losing it on the way out feels like leaving money on the table. The good news: you can rebuild it. Not overnight, and not automatically, but deliberately and completely. Here's how to extract what Affinity holds, structure it in Orin's native contact and deal framework , and walk away with richer relationship data than you had before. What Affinity exports—and what it doesn't Affinity's CSV export includes: Contact names, emails, phone numbers Company associations Custom fields you've defined Deal stage and value (if associated) Last activity date What's missing: Interaction history (emails, calls, meetings logged in Affinity) Relationship clusters (the "people you know" graph) Influence and decision-maker scoring Internal notes and context threads Historical relationship changes (when someone moved companies, changed roles) The interaction history is the killer. Affinity stores this in a relational database that the export doesn't touch. You can request it manually through their support team, but it comes as PDF reports or raw data dumps—not structured, machine-readable exports. The core problem: Affinity treats relationships as the product (not a feature). Its competitive advantage is precisely what doesn't export. So by design, leaving Affinity means losing graph depth. Extract what you can: Three data sources 1. Affinity's native export + activity log Start here. Log into Affinity and pull two exports: Contacts CSV: Go to Contacts → select all → Export . This gives you the master list with fields, companies, and deal associations. Activity timeline (per contact): For each contact, open their profile and scroll to Activity . Screenshot or copy-paste the thread into a shared doc or spreadsheet. This is manual but preserves context. For high-value contacts (top 20–30% by deal size or strategic importance), spend 10 minutes per contact documenting the relationship arc: when they joined their company, what triggered engagement, who introduced them, which deals they influenced. 2. Email archive + calendar Affinity syncs email and calendar data. If your team uses Gmail or Outlook: Export calendar events tied to Affinity contacts (many calendar tools allow you to filter by attendee or search by name). Search your email for threads with Affinity contacts and export them (Gmail: use filters like from:contact@email.com , then export as .mbox or .csv). This reconstruction takes time but gives you the actual communication trail Affinity logged. 3. Affinity's relationship data via support Email Affinity support and request a data export that includes relationship mappings or influence scores. They may provide: Lists of contacts by relationship strength or interaction frequency Account hierarchies showing decision-maker chains Historical role or company changes This isn't guaranteed and may take 5–10 business days, but it's worth the ask if you have large, complex deals in Affinity. Re-link manually in Orin: The relationship rebuild Once you've imported contacts into Orin (a straightforward CSV import), the work starts. You're going to formalize the relationships you've extracted. Map contact roles and reporting lines Orin's CRM lets you create custom fields and link contacts to companies. Use these to rebuild what Affinity's graph showed: Add a "Reports To" field (linked contact field) to show hierarchy. Add a "Primary contact" field on each company record to flag the first point of entry. Create a "Introduced by" field to track who brought someone into your pipeline. Add a "Relationship strength" field (dropdown: Strategic / Core / Transactional) based on interaction frequency and deal size. Log historical interactions For each contact, create an internal note or activity record that documents: First engagement date and channel Key meetings or milestones Influencers or decision-makers in their orbit Any role or company changes (and when) Orin's notes field is searchable, so you're building an institutional memory that survives the person who held the relationship. Link contacts to deals—and re-weight them In Affinity, influence was implicit (baked into the graph). In Orin, you make it explicit. For every deal: Add all contacts who influenced it (even tangentially). Assign a role field (Decision-maker / Sponsor / Influencer / End-user). Flag the primary contact (usually the sponsor or decision-maker). This flattens the graph into rows, but it's searchable and auditable. You can now query "Show me all deals where this contact was a decision-maker" or "Which contacts have never been on a closed-won deal?" Formalize ongoing relationship capture The rebuild is one-time