You chose Affinity because it captured every conversation, every email thread, every person connected to a deal. Your team lives in those interaction histories. Then you looked at HubSpot's lead scoring, nurture sequences, and multi-touch attribution—and realized Affinity doesn't do that. Now you're planning a migration, and you're right to be nervous. Affinity and HubSpot think about sales fundamentally differently. One is depth-first; the other is breadth-first. The migration is not just a data export. Why Affinity and HubSpot aren't interchangeable Affinity was built to help you remember. Every email, every event attendance, every person on the cap table—it's all there, searchable, contextualized. Your sales process probably mirrors that: you nurture three to five key relationships per prospect until they're ready to move. You rely on Affinity to surface that history when you need it. HubSpot was built to help you scale. Lead scoring, automated nurture campaigns, contact segmentation, and pipeline forecasting across hundreds of prospects in parallel. Your process will need to change: instead of depth-first relationship management, you'll be running breadth-first lead workflows. That's not bad. It's just different. And if you're hiring, growing, or entering markets where you need to touch more prospects in less time, breadth-first makes sense. But the transition requires you to rebuild three things: Your data structure (contacts, companies, deal stages) Your workflows (lead scoring, nurture, routing) Your team's daily rhythm (tools, searches, how you flag priorities) The 2-week sprint: Data export and cleanup Start here. You have 10 business days to export Affinity data and map it into HubSpot's schema. Do not skip this. Week 1: Export and audit Day 1–2: Export from Affinity. Use Affinity's native export (Contacts, Companies, Opportunities, and Activities). You'll get CSV files. Open them. Do not assume they're clean. Common problems you'll find: Email duplicates. The same prospect has 3 email addresses. Only one is current. You'll spend 6 hours de-duping if you don't catch this now. Company mismatches. A contact's company field says "Goldman Sachs" but the company object says "GS". HubSpot needs consistency or deduplication fails. Deal stage sprawl. Affinity lets you name stages anything. You probably have "Intro", "Discovery", "Deeper Dive", "Advanced Discussions", and "Close Pending"—which map to what in HubSpot's standard Negotiation / Committed / Closed-Won? Custom fields with no owner. You have a field called "Investor Status" that 40% of contacts populate differently. HubSpot will import it as text. You'll want it as a dropdown. That rebuild is manual. Day 3–5: Standardize before import. Create a single source spreadsheet that maps Affinity exports to HubSpot fields. This is mechanical but non-negotiable: Affinity Contact → HubSpot Contact (name, email, phone, company) Affinity Company → HubSpot Company (name, domain, industry, location) Affinity Opportunity → HubSpot Deal (title, amount, stage, close date) Affinity custom fields → HubSpot custom fields (or archival, if you don't need them) De-dupe as you go. One email address per contact. One record per company name. Day 6–10: Import into a test HubSpot account (not production). Run a test import. Verify record counts match. Check 50 contacts for accuracy. Fix mapping errors. Re-import. Then move to production. What does NOT import cleanly Affinity's interaction history is its superpower. HubSpot can import activity records (emails, calls, notes), but: Affinity's implicit relationship graph ("these 4 people are all connected to this deal") becomes explicit company relationships in HubSpot. You lose the ambient awareness. You have to maintain it manually or via pipeline discipline . Affinity's event and content feeds (e.g., "Raj just joined TechCorp, and we have him in our system") are historical. HubSpot doesn't auto-monitor LinkedIn. You'll need to decide if you want a separate tool (like Hunter or Apollo) to re-enrich. Affinity's personal email threads (emails between you and a prospect outside the CRM) exist only if you forwarded them to Affinity. HubSpot requires you to use shared inboxes or email integration for the same effect. If your team uses Gmail, you'll need to configure Gmail sync or a unified inbox to capture the same history. Plan for this. Some teams decide to keep Affinity read-only alongside HubSpot for 3–6 months. Others archive Affinity as a historical reference and accept that they're starting fresh. Neither is wrong; it depends on deal length and how much you rely on interaction archaeology. The 4-week rebuild: Workflows and automation After data import, you have four weeks to rebuild your sales process in HubSpot. This is where the real work lives. Week 1: Lead scoring and segmentation In Affinity, leads are warm because you know them or you know someone who knows them. HubSpot needs explicit scoring rules. Build a lead scor