Affinity CRM is built for relationship intelligence. It ingests news, social data, and deal flow into slick timelines. For wealth advisors managing relationships across multiple touchpoints, the relationship graph is genuinely useful—it shows you who knows whom, where the money sits, and which introductions matter. But relationship mapping alone doesn't close retainer deals or keep invoices paid. Wealth practices need to invoice for advisory retainers, draft and sign engagement agreements, chase unpaid fees without sounding desperate, and keep their team in sync across call notes, contract status, and payment terms. Affinity handles the first part beautifully. It stops there. Most wealth teams end up juggling Stripe, DocuSign, and Slack alongside Affinity—and that toolstack complexity costs more than consolidation would. This playbook walks you through the practical migration path: what you can export cleanly, what gets messy, and why an all-in-one platform matters more for retainer teams than it does for transactional sales. Why wealth teams hit Affinity's ceiling Affinity's strength is relationship context: who connected you, what articles they've read about your firm, what their board looks like. For relationship-driven wealth management, that's valuable. But wealth advisory also requires: Invoicing and payment tracking —Affinity has no native billing. You export a list, invoice in Wave or FreshBooks, and manually log payment receipts back into Affinity. That handoff is where unpaid invoices hide. Contract lifecycle management —Engagement letters, fee schedules, and amendments need signatures and version history. Affinity stores PDFs. It doesn't track signature status, route approvals, or flag expiring agreements. Team alignment without silos —Affinity feeds relationship notes into email. Your team still misses context because updates live in Affinity, decisions live in Slack, and payments live elsewhere. You're not actually unified. Revenue forecasting from actual contracts —Your CRM can't forecast retainer revenue if it doesn't know contract value, start date, or renewal terms. Affinity stores these as notes in deal records. Reporting is guesswork. For practices managing three to fifty client relationships at $50k–$500k AUM each, these gaps compound. A single missed invoice follow-up or unsigned amendment can cost more than the software savings you're celebrating. What exports cleanly from Affinity Affinity lets you export contacts, companies, and custom fields as CSV. The export is straightforward—it's what comes next that matters. Step 1: Data audit before export Before you export anything, answer these questions in Affinity: Which contacts are active clients vs. prospects vs. archived? What custom fields do you actually use? (If a field is 90% empty, you probably don't need it.) Which deals are in flight vs. closed vs. lost? Do you have relationship hierarchies (who introduced whom, who's the decision-maker)? Export three separate files: Contacts (with all custom fields), Companies , and Deals . Open each in a spreadsheet and spot-check 5–10 rows for data quality. If you see mostly empty columns, contact your Affinity admin—you may be exporting test data alongside production data. Step 2: Export and clean Affinity's export format is clean for a CRM standard. When you import into Orin, the hardest part is usually not technical—it's deciding which Affinity columns map to which Orin fields. Common mapping challenge: Affinity stores relationship data as free-form text in notes or custom fields. "John introduced us to Sarah in 2021." When you import that into Orin, it's still just text. If you want to query "all clients who came through John," you'll need to standardize that into a lookup field first. In practice, this means: Export your Affinity data as CSV. In the spreadsheet, create a new column for any relationship field you want to track systematically (e.g., Referred By ). Populate it by parsing or manually updating your notes. Clean phone numbers, standardize country codes, and flag any missing email addresses before import. Import into Orin's CRM using the bulk import tool. What gets complicated in the handoff Three categories of Affinity data don't migrate cleanly: Deal history and relationship timelines Affinity's value prop is the timeline: you see every news mention, email, call, and interaction date in one view. When you export a deal, you get the deal name and stage, but the timeline—the sequence of touchpoints that built the relationship—gets left behind. In Orin, you can reconstruct this partially: store key deal milestones as closed activities, attach relevant emails to the deal record, and use team chat to keep conversation context linked. But you're not migrating the timeline itself; you're recreating it forward. Mitigation: For your ten most important clients, manually summarize the relationship in a text field called "Relationship summary" or "Background." Export that summary with yo