When you export from Affinity, you get a flat file. Contacts lose their depth. Companies no longer know their parents or subsidiaries. The influence chains that made your relationship graph valuable—the reason you paid for Affinity in the first place—collapse into a spreadsheet. This is not a technical failure. It is a structural one. Affinity stores relationship context as metadata, as UI-driven connections, as graph traversal. A CSV or JSON export has no semantic grammar for 'this contact works at Company A but influences decisions at Company B' or 'this company is a subsidiary of a holding group I service as an ecosystem.' The data lives in the export; the meaning does not. If you are moving to Orin, you have 60 days to recover that meaning before it costs you deals. This playbook shows you what survives the export, what does not, and how to rebuild relational context so that your next revenue conversation starts from relationship depth, not orphaned contact records. What Affinity exports capture—and what they lose An Affinity export typically contains: Contact name, title, email, phone Company name and basic company fields Interaction history (emails, calls, meetings) List membership and tags Custom fields you created Notes and activity timestamps What does not travel: Parent-subsidiary relationships. If you mapped Company A as the parent of Company B, that hierarchy vanishes. You get two flat records. Cross-company influence links. A contact record shows only the primary company. Secondary affiliations—the CFO who sits on three boards—disappear. Network chains. Affinity's graph view traces introduction paths and warm introductions. The export loses that provenance. Interaction context. A note saying 'met at conference with CEO' survives; the implicit relationship to that CEO does not auto-link. Relationship stage and signals. Affinity's scoring and stage metadata is custom per workspace and rarely exports cleanly. This is why 40% of migrating users report a 30–45-day dip in pipeline velocity after switching platforms. The data is there. The relationships are not. Audit your Affinity graph before export Do not export blind. Spend 3–5 days in Affinity identifying the relationship patterns that matter most to your business. Step 1: Map your key account structures. Run a report in Affinity (Admin → Organization → Structure or use API) to list: All parent-subsidiary relationships Holding companies and their portfolio Strategic partnerships and co-investment structures Export this as a separate reference CSV. Include parent company ID, child company ID, relationship type (subsidiary, acquisition, joint venture), and the date the relationship was established. You will hardcode these into Orin. Step 2: Identify multi-company contacts. Find contacts with secondary affiliations—board members, advisors, investors who span multiple organizations. Affinity labels these. Export a reference list of contact ID, primary company, secondary companies, and the nature of each link (board member, investor, advisor, employee). Step 3: Tag influence chains. In Affinity, add a temporary tag called 'INFLUENCE_CHAIN' to any contact who is central to multiple deals—the connector, the decision-maker, the introducer. Note their tier (executive sponsor, influencer, technical evaluator). This becomes your roadmap for rebuilding relationship depth in Orin. Take a screenshot or export these lists. You will reference them for 60 days. Export and structure in Orin Orin's native CRM structure supports parent-child relationships, contact role hierarchies, and cross-company links natively. Unlike flat exports from other platforms, Orin allows you to encode relationship depth on import. Step 1: Prepare your contact CSV. Export your Affinity contacts with these columns (in this order): Contact ID (from Affinity) First Name Last Name Email Phone Company ID (from Affinity) Title Department Tags (comma-separated) Notes (last interaction, key info) Created Date Last Activity Date Do not include Affinity's metadata fields that do not map to Orin. Strip them out. Orin will ingest this cleanly; Affinity's custom scoring will live in your audit sheet, not in the platform. Step 2: Prepare your company CSV. Export Affinity companies with: Company ID Company Name Website Industry Employee Count (if available) Annual Revenue (if available) Parent Company ID (leave blank for now; you will fill this in next) Company Type (holding, subsidiary, portfolio company) Tags Notes Step 3: Rebuild parent-child relationships in a staging sheet. In a separate Excel file, create three columns: Child Company (Orin ID after import) Parent Company (Orin ID after import) Relationship Type (subsidiary, acquisition, joint venture, portfolio) Fill this in using your Affinity audit. After your initial import into Orin, you will bulk-update the Parent Company field for all subsidiaries. This rebuilds your org hierarchy in Orin. Step 4: Map cross-company contacts. For contacts w