At 500 contacts, your Notion CRM is no longer a scratchpad—it's a business asset. But Notion was never designed as a true CRM. Its export function treats relationships like a camera treats depth: it flattens them. You hit export, watch the CSV land, load it into Pipedrive or HubSpot, and discover nine critical fields are gone, orphaned, or corrupted. The contact still exists. The relationship history does not. This is not a Notion bug. It's a deliberate design choice: Notion's relational fields (linked records, rollups, formulas that reference other tables) exist only inside Notion. Export them, and they collapse to plain text or disappear entirely. We've mapped exactly which fields die, which survive as text, and which need rebuilding. And we've built a 14-day checklist to validate nothing is lost before you flip the switch. The nine fields that orphan or corrupt on export Not all data loss is equal. Some fields vanish silently; others export as unusable text. Here's what actually happens: 1. Linked records (deal, company, contact relations) Notion's linked records are its strength inside the tool. Export them, and you get a comma-separated list of names—no IDs, no URLs, no relationship metadata. If your Notion contact "Sarah" is linked to three deals and two companies, the export shows: "Sarah Chen, Acme Corp, Acme Q3 Expansion, Acme Integration, Beta Networks" That's useless in a real CRM. You now have a text blob that Pipedrive or HubSpot cannot parse. You must manually re-link or run a merge/lookup script. 2. Rollup fields (sum, count, max, concatenate) Rollups export as static snapshots—the value at export time, locked forever. If you had a rollup summing "deal value across linked deals," it becomes a plain number. It will never update again. In a real CRM, that rollup would recalculate as deals move or close. 3. Formula fields (conditional text, date math, lookups) Formulas export as their final calculated values, not as formulas. A field showing "Days since last contact" becomes a frozen integer. Next month, it's wrong. 4. Status fields (if multi-select only) Single-select status fields export cleanly. Multi-select fields export as comma-separated text, which most CRMs read as a single tag. That's usually okay, but if your CRM expects one status per record, you'll see parsing errors. 5. Email and phone (if they live in related tables) If you store email/phone in a separate Contacts Details table and link it back to your main contact, the export shows the contact name but not the actual email or phone in the primary contact row. You must export the Details table separately and join it manually. 6. Timestamps (created date, last modified) Notion exports these in UTC ISO format. Most CRMs accept it, but timezone display can drift depending on the target system's settings. Not lost—just misaligned if the import doesn't map the timezone correctly. 7. Rich text and mention fields Rich text exports as plain text; inline @ mentions collapse to names without links. A note saying "Follow up with @Sarah on Q3 timeline" becomes "Follow up with Sarah on Q3 timeline." The context link is gone. 8. Attachments (file links) Notion export includes file URLs, but they're fragile. If Notion changes its storage structure or access rules, those links break. Many CRMs don't auto-sync Notion file storage anyway, so you end up with broken links or missing documents. 9. Person properties (assignee, team member references) If you assigned contacts to team members via Notion's Person property, the export shows the person's name. Without a pre-built mapping of Notion user IDs to CRM user IDs, you can't auto-assign in the target system. You'll re-assign manually or lose the ownership entirely. Which fields survive export intact The good news: core contact fields export cleanly to any CRM. You won't lose: Text, email, phone, URL — Clean, direct, no surprises. Single-select fields (status, category, source) — Most CRMs read these as tags or picklists. Usually maps directly. Date fields (birth date, contract date, deal close date) — Export as ISO dates; most CRMs understand them. Checkbox fields — Export as TRUE/FALSE; CRMs interpret as boolean or yes/no fields. Number fields (revenue, ARR, employee count) — Export as integers; no rounding loss unless the CRM has column width limits. Long text (description, notes) — Export fully; no character limit truncation unless the CRM's field is smaller than Notion's. The 14-day pre-export validation checklist Before you press "export," run this validation: Days 1–2: Audit your Notion schema List every field in your contact table. Mark each as "core," "relation," or "computed." For each relation field, count how many records it links to. (Example: "Sarah Chen links to 3 deals, 2 companies, 1 account manager.") Note these numbers. For each formula or rollup, document what it calculates and why. You'll rebuild this manually if needed. Export a test table (10 rows) as CSV and open in Excel. Veri