You've made the decision to leave Affinity. You've negotiated a contract with Pipedrive or Orin . You hit export. And then you open the CSV and realize something critical is missing: the relationship graph that made Affinity useful in the first place is now a flat list of contacts and companies with half their context stripped away. This is not a data format problem. This is a design problem. Affinity was built around relationship intelligence—how people connect, who influences whom, which relationships matter. Its export treats those connections like optional metadata. When you move to a new CRM, nine critical fields either vanish entirely or arrive so mangled that rebuilding them manually costs 80 hours and keeps your sales team blind for weeks. Here's what actually leaves Affinity, why it matters, and the 60-day playbook to get your relationship depth back. The nine fields that vanish on export Affinity's export (CSV or via API) includes contacts, companies, and basic opportunity data. What it does not reliably preserve: 1. Relationship type and depth Affinity stores relationships as edge weights: "Decision maker," "Influencer," "End user," "Evaluator." On export, these arrive as flat contact fields or not at all. Pipedrive can store role, but not the nuance of influence. You lose the answer to "who actually approves this deal?" 2. Relationship history and interaction count Affinity's core metric is interaction frequency (emails, calls, meetings). On export, you get a timestamp or summary, not the full thread. Your new CRM sees "last touch: 45 days ago," not "engaged 23 times over 6 months." Deal momentum becomes invisible. 3. Opportunity linkage across multiple contacts A single deal in Affinity connects to 5–7 stakeholders with different roles. Most CRMs' export format ties each opportunity to one contact (or many 1:1 records). You arrive in Pipedrive or Orin with six separate "opportunity" rows instead of one deal with six stakeholders. Rebuilding the linkage by hand takes 20+ hours per 100 deals. 4. Custom relationship types If you've built custom relationship categories (e.g., "Sponsor," "Budget holder," "Legal review"), Affinity's export drops them entirely. Standard exports do not carry custom picklist values. You land in a new CRM with a generic "relationship type" field and all your taxonomy scattered in notes. 5. Interaction media and channel source Affinity tracks interaction source (LinkedIn message, email, call, event). Exports often collapse this to a single field or omit it. You lose the answer to "where did we meet this person?" and context for outreach strategy. 6. Account-to-account relationship intelligence Company-level relationships (which vendors work with which customers, who has partnership agreements) are often buried in notes or custom fields. Standard exports do not include company-to-company edge data. You export two customers and two vendors, but the export has no way to say "Vendor A works with Customer 1 but not Customer 2." 7. Permission and CRM access history If you've shared relationships or restricted visibility in Affinity, that metadata does not move. Everyone who had read access in Affinity might have different permissions in Orin or Pipedrive, and you have to manually set it up. 8. Engagement scoring and health metrics Affinity may compute or store engagement scores. These are CRM-proprietary and do not export cleanly. You lose a scorecard that helped you rank hot deals. 9. Timeline and deal-stage history Affinity keeps a timeline of interactions and stage changes. Exports usually give you the current stage, not the journey. Missing this context, your sales team cannot see whether a deal has been stalled for 45 days or is moving steadily forward. What actually arrives in your new CRM When you import an Affinity export into Pipedrive, Orin , or HubSpot, you get: Contacts: Name, email, phone, company, job title. Usually clean and complete. Companies: Name, domain, employee count, location. Often missing custom fields. Opportunities: Deal name, amount, close date, stage. One opportunity per contact (or duplicated records per stakeholder). Notes or custom fields: A blob of text where Affinity's structured fields became unstructured. Activity log: If the CRM has an API importer, interaction history may arrive as activity records. But the relationship context (who initiated, what role) is usually missing. What does not arrive: relationship types, interaction counts, account graphs, engagement scores, permission history, or timeline narratives. Field-by-field mapping: what to save, what to rebuild Before you start recovery, map each field in your Affinity export to your new platform. Here's a template: Affinity Field Arrives In Export As Maps To (Orin/Pipedrive) Rebuild Method Relationship type Custom field or notes Contact role or relationship custom field Manual audit + re-entry Interaction count Last interaction date only Activity timeline API import of email/call logs