Every CRM vendor likes to make you feel trapped. Switching platforms is expensive, tedious, and full of hidden gotchas—and that's by design. But the moment you realize your current tool doesn't fit your business anymore, leaving becomes unavoidable. The difference between a clean exit and a messy one is knowing what data actually survives the export and what you'll need to manually rescue. This guide walks you through the native export capabilities of the major platforms, shows you exactly what metadata gets left behind, and gives you a concrete checklist to run before you switch. The goal is simple: make sure you don't lose years of customer relationship depth because your new platform doesn't speak the old one's language. The truth about native CRM exports Every major CRM claims to support data export. What they don't advertise is that "export" usually means CSV or JSON of your core tables—contacts, deals, activities—and almost nothing else. The relationship scaffolding, custom logic, and metadata that made your CRM actually work for your business? That stays behind. Here's what a typical export looks like: What you get: Contacts (name, email, phone, basic custom fields), deals (title, value, stage, close date), activities (date, type, notes), and company records. What vanishes: Deal history (old stages, old close dates, date-of-change metadata), activity sequence and timing, relationship maps, field dependencies, automation triggers, and in many cases, the actual conversation thread that led to the deal. A CSV export is a snapshot. It captures what exists right now, not how you got here or why it matters. The platforms themselves vary wildly in what they'll let you take with you. Some make exports easy because they're confident you won't leave. Others make it deliberately painful. What you'll lose in Pipedrive Pipedrive's strength is its visual pipeline. That pipeline is also its lock-in weapon. When you export from Pipedrive, you get: Contacts and companies (all custom fields included). Deals with current stage, value, and expected close date. Activities (calls, emails, meetings) with timestamps. Products and line items (if you use them). What you lose: Deal history. Pipedrive tracks every time a deal moves stages, changes value, or slips a close date. That audit trail is crucial for understanding sales velocity and forecasting accuracy. It doesn't export. You'll lose the ability to answer "when did this deal stall?" or "how many times did we re-forecast this quarter?" Email threads. If you synced email into Pipedrive, those threads live in Pipedrive's servers. The export gives you activity records ("email sent on X date") but not the actual message bodies. You'll need to manually download email archives from your email provider separately. Relationship strength metrics. Pipedrive tracks interaction frequency and recency implicitly. That context disappears in the export. Custom pipeline logic. If you've set up field dependencies (e.g., "show discount only if deal value > $50K"), those rules don't export. Your new platform will have an empty template. Pipedrive exports as CSV by default, with JSON available via API. For a 10-person sales team with 5,000 active deals, plan on 30–60 minutes of export time plus several hours of data cleanup in your new platform. What you'll lose in HubSpot HubSpot's strength is customization. It's also why exporting feels incomplete. HubSpot lets you export: Contacts with all standard and custom properties. Companies and their associations. Deals, tickets, and other object records. Email and activity history (limited). What stays behind: Custom properties metadata. HubSpot's custom fields can have field types (dropdown, checkbox, calculation, rollup), default values, field dependencies, and visibility rules. The export gives you the field names and current values—not the configuration. Recreating a dozen custom fields in your new platform means manually re-entering every dropdown option, default, and formula. Automation and workflow history. If a HubSpot workflow triggered an email or updated a field based on a condition, that logic doesn't export. You'll lose the context of why certain fields have their current values. Association depth. HubSpot associations (contact → company → deal → ticket) export as IDs. If your new platform doesn't use matching ID schemes, you'll need to manually re-establish relationships. Pipeline configuration. Your deal stages, loss reasons, and closing probability mappings stay in HubSpot. Conversation threads from HubSpot's chat widget. If you used HubSpot's embedded messaging , those conversations don't export. You'll need to manually archive them elsewhere. HubSpot exports as CSV via the UI (slow for large datasets) or via API (fast, but requires technical setup). A mid-size HubSpot instance (500+ contacts, 2,000+ deals) usually takes 2–4 hours to fully export and another 4–8 hours to validate in your new platform. What you'll lose in Affinity