When you export from Affinity, you get a contact list. Not a relationship graph. The nuance that made your pipeline readable—who knows whom, which companies matter, why a deal stalled—evaporates into flat CSV rows. The export preserves names and email addresses. It does not preserve context. This is not a Affinity problem uniquely. Most CRM exports flatten by design. But Affinity's strength was the relationship lens: deal rooms, stakeholder mapping, connection history. Losing that during migration feels like leaving money on the table. It is. Over the next 60 days, you will rebuild that depth in Orin using contact tagging, company hierarchy, deal-context fields, and a systematic audit of where deals hide in your export. This playbook shows you where the gaps are, how to fill them, and what to do first so you don't spend three months in spreadsheet hell. Where your deals disappear in the Affinity export Affinity's CSV export includes contact records and a separate deals table. But the linkage between them—who is the economic buyer, who is the champion, who is just cc'd on emails—lives in the deal room, not in the export. When you pull the CSV, you see deal names and stage labels. You do not see which contacts own which deals or why a deal is stuck. Run this audit first. It takes 90 minutes and tells you what actually survived the export. Count your deals in Affinity. Note the total in your workspace settings. Count rows in your deals export. Are there gaps? If you have 300 deals but the export shows 250, investigate. Archived deals, deals in read-only access, or deals shared across multiple workspaces often vanish. Check deal-to-contact relationships. Affinity exports usually include a 'created by' and 'last modified by' field, but not the stakeholder list. Open five random deals in Affinity. For each, count the stakeholders in the deal room. Then check your export row. You will see one or two contact fields (maybe 'primary contact') but not the full team. Look for deal notes without owners. Affinity lets you log activities and notes inside a deal room. Those live in Affinity, not in the export. Your CSV has a deal name and maybe a description, but not the three months of email threads, call logs, or relationship notes. What this means: your export is incomplete by design. The missing data is not lost; it is still in Affinity, and you need a strategy to recover it before you cancel the account. The three types of relationship depth you must preserve Before you migrate, define what relationship depth means for your business. Affinity encoded this in three ways. Orin handles all three, but you must map them intentionally. 1. Multi-stakeholder deals (the deal room problem) A typical enterprise deal involves five to eight people: a primary sponsor, a technical evaluator, a procurement owner, an end user, maybe a consultant. In Affinity, these all live in one deal room. The context is spatial: you see them all on the same screen. In a CSV export, you see one contact field called 'contact' or 'primary contact'. The other stakeholders are invisible. Solution in Orin: Use contact tagging and deal stakeholder fields . When you import your Affinity data, create a custom deal field called 'stakeholders' (multi-select contact field). Then, before you import, manually map the stakeholder list for your top 50 deals. It takes time, but those 50 deals probably account for 60–80% of your pipeline value. For smaller deals, use a tag-based approach: tag contacts with their role ('procurement', 'technical buyer', 'end user'). When you query your deal, you can filter by tag to surface the right person to call. 2. Company hierarchy and relationship trees Affinity lets you build parent-subsidiary relationships and track which contacts belong to which companies. An export shows company name and maybe a parent company field, but the full tree—holding company, regional offices, acquired subsidiaries—often compresses into a single row. This matters because a deal at the holding company is not the same as a deal at a regional office. Context is everything. Solution in Orin: Use company hierarchy fields. Orin lets you set parent and child companies, track company relationships, and attach contacts to multiple entities. When you import, map the parent company field from your export. Then, in your first two weeks, audit your top 20 accounts and manually build their corporate trees. For example, if you have a deal with 'Unilever North Asia', create parent-subsidiary relationships for the regional holding company, the country office, and the specific business unit. Tag each with 'subsidiary_of' or 'parent_company'. This takes four hours. It pays for itself the moment a prospect says 'we just merged our regional teams' and you can instantly see all your opportunities across the combined entity. 3. Deal context and the paper trail Affinity's deal rooms are not just lists; they are activity hubs. Emails, notes, calls, proposals—everything rela