You're 300 contacts deep in Notion. Deal pipeline looks clean. Team's using it daily. Then someone asks: what happens when we need to move this somewhere with real CRM muscle—Pipedrive, HubSpot, Orin? So you run a test export and realize Notion's native CSV dump captures maybe 60% of what actually exists in your database. The rest? Orphaned. Custom relations, formula fields, activity logs, timeline views—none of it makes the jump. This isn't a Notion failure. It's a data architecture mismatch. Notion treats relationships as views; real CRMs treat them as entities. Notion's formulas live in cells; CRMs need activity history. Understanding what survives and what doesn't—and the rebuild cost for each—is the only way to know if you're moving 300 clean records or 300 gutted ones. What Notion exports capture (and why they're incomplete) Notion's CSV export grabs these fields reliably: Text properties: Company name, person name, title, email, phone. Comes through clean, no surprises. URL and email fields: Exported as text links. Format survives. Your new platform can parse them on import. Select and multi-select: Status, industry tags, list fields. These export as comma-separated values or single selections. Most CRMs can remap these on import—but only if your new system has identical options defined first. Number fields: Revenue, employee count, deal size. Numeric data moves cleanly. Checkbox fields: Boolean flags (is_customer, is_vetted). Export as TRUE/FALSE. Survive intact. Date fields: Creation dates, last contact, close date. Export as YYYY-MM-DD. Standard format, imports cleanly. The catch: Notion exports what's in the record , not what connects the record to anything else . You lose the graph entirely. The four field types that orphan on export 1. Relation and rollup fields (40% of your data value) Notion relations are Notion's superpower—they let you link a Contact to Deals, Companies, Activities, or anything else. On export, these fields appear completely empty. Why? CSV has no concept of a foreign key. A relation in Notion is a pointer to another record in another table. There's nowhere to put that in a flat file. What you lose: Which deals are attached to which contacts—you'd have to remap manually or use a secondary sync tool. Rollup fields (sum of deal values tied to a contact, count of activities) vanish. They weren't data; they were calculated views of relationships. Company–contact associations. If you used a Companies table linked to Contacts, those links are gone. Rebuild effort: High. If you have 50+ deals per contact on average, you're rebuilding 15,000+ relationship records by hand or via API import. A real CRM's import tool can ingest a CSV mapping file (contact_id, deal_id) to rebuild this in minutes. Notion gives you nothing. 2. Formula fields (10–15% of calculated data) Formulas in Notion are read-only. They calculate in real time but don't store values. On export, the result of the formula is sometimes captured—but the logic is not. You lose the formula itself. Examples that break: Deal value × probability = expected value. The export might grab the result (if Notion calculated it before export), but the formula is gone. Days since last contact. On export day, it shows '14'. Next week, it still shows '14' in your new CRM—because the formula didn't migrate. Contact name formatted as UPPERCASE or concatenated fields (first_name + " " + last_name). Exports as the result, not the rule. Rebuild effort: Medium. Your new CRM has native formulas or automation. You'll manually recreate these—10–20 minutes per field type if you have 5–10 unique formulas. The results export cleanly, but you're rebuilding the logic from scratch. 3. Activity history and timeline fields (30% of deal context) Activity tables in Notion (call logs, emails, tasks, notes) are separate records linked to contacts or deals. On export, you export the Activity table separately . But there's no automatic way to tell your new CRM "this activity belongs to that contact" without manually mapping the relationship IDs. What vanishes: A unified timeline for a deal or contact. Your new CRM won't know which activities belong to which record until you rebuild the connection. Conversation threads. If you logged 20 emails with a contact in Notion, they'll export as 20 rows with no parent reference. Your new CRM sees them as orphaned. Task context. A task linked to a deal—the link is gone. It's just a task with a title and due date. Rebuild effort: Very high. If you have 5,000 activities across 300 contacts, you need a mapping file (activity_id → contact_id / deal_id). If you used Notion's linked records, the data exists—you just have to export it separately and import it as a relational sync. Without that, each activity is orphaned. Manual linking is impractical. 4. Timeline and timeline views (your deal progress map) Notion's timeline view is read-only. It's a visual rendering of date fields over time. On export, it doesn't exist. You exp