You're about to export your Notion CRM to move platforms. You run the export. The CSV lands in your inbox. You open it in a spreadsheet and immediately realize something's wrong—the relationships your team spent months building are gone. Interaction history is a wall of text. Deal linkage is broken. Custom properties don't exist. You've just orphaned 60% of your relationship context, and you don't know which pieces survived the export and which didn't. This is not a Notion bug. It's a structural limitation in how Notion's relational database exports to flat file formats. But it's catastrophic when your relationship data is your competitive moat. We've mapped exactly which nine fields vanish on export, why they disappear, and how to recover them before they cost you ₹30K in lost relationship context and deal friction. Why Notion's Export Destroys Relationships Notion stores relationships as bidirectional links inside its database—one contact can connect to many others, each link tagged with a relationship type (partner, referral source, competitor, client advocate). When you export to CSV, Notion can't represent those links in a flat file. It collapses them into a single text field, stripping away the relationship type, the direction, and any metadata attached to that connection. The same thing happens with interaction history, deal linkage, and any field that references another table. Notion's export format is optimized for quick data dumps, not data fidelity. The nine fields we're about to map account for roughly 60% of the depth that makes a CRM actually useful—the context that turns a contact list into a relationship engine. If you're migrating soon, this matters. If you're using Notion right now and thinking about moving to a platform with better relationship management, you need to know what you're leaving behind. The Nine Fields That Orphan on Export Here's the field-by-field breakdown of what dies when you export: 1. Relationship Type (Bidirectional Links) What Notion stores: Contact A is a "Partner" to Contact B; Contact B is a "Referral Source" to Contact A. What exports: "Contact B" as plain text, with no indication of the relationship type or direction. Recovery cost: ₹5K–8K in manual re-tagging if you have 200+ contacts with cross-relationships. Impact on deals: You lose the ability to trace deal influence back to the relationship type (e.g., partner intros vs. self-identified leads). 2. Interaction History (Rollup Field) What Notion stores: A rollup of all emails, calls, and meetings linked to a contact, with date, type, and outcome. What exports: A concatenated text string: "Call 2025-01-14, Email 2025-01-20, Meeting 2025-02-01" with no structure or metadata. Recovery cost: ₹8K–12K to parse and re-link interactions if you have 500+ contacts. Impact on deals: No touchpoint timeline. You can't see velocity signals or engagement patterns. 3. Deal Linkage (Many-to-Many Relation) What Notion stores: Contact is linked to Deal A (buyer), Deal B (stakeholder), and Deal C (evaluator), each with a specific role. What exports: "Deal A, Deal B, Deal C" as comma-separated text, with no indication of the role or stage. Recovery cost: ₹6K–10K to reconstruct deal influence and stakeholder mapping. Impact on deals: You can't identify multi-threaded deals or trace decision makers back to their deals. 4. Custom Relationship Properties (Formula Fields) What Notion stores: Calculated fields like "Days Since Last Contact" or "Relationship Health Score" (1–10 scale). What exports: Nothing. Formula fields don't export at all. Recovery cost: ₹3K–5K to rebuild scoring logic in your new platform. Impact on deals: You lose prioritization data. Reps can't see who's warm vs. cold at a glance. 5. Linked Interaction Records (Relation Field) What Notion stores: Each interaction (email, call, meeting) is a separate record linked to the contact, with notes, duration, and outcome. What exports: Contact exports as a single row. Interactions don't export at all unless you manually export the Interactions table separately—and when you do, they lose their link back to the contact. Recovery cost: ₹5K–8K to re-join interaction data to contacts post-export. Impact on deals: No way to see the full conversation thread without digging through notes. 6. Account / Company Linkage (Lookup Field) What Notion stores: A link to a Company record, with inherited fields like "Company Stage" and "ACV." What exports: The company name as text, but none of the inherited fields come with it. Recovery cost: ₹4K–6K to rebuild company-to-contact associations and re-inherit company attributes. Impact on deals: You lose account context. Reps can't see company-level signals (funding, growth stage, churn risk). 7. Pipeline Stage as a Relation (Not a Select) What Notion stores: If deal stage is stored as a linked record (not a simple dropdown), it can carry metadata like stage duration, SLA, and actions. What exports: Just the stage name, with no metadata or h