granola-migration-deep-dive

# Granola Migration Deep Dive ## Overview Comprehensive guide for migrating to Granola from competing meeting note tools. Covers source-specific export procedures, historical data preservation, parallel-run strategy, team transition, and cutover execution. Granola's key differentiator — no bot joins meetings — means the migration also changes the user experience fundamentally. ## Prerequisites - Access to source tool with export capability - Granola workspace configured (see `granola-install-auth`) - Migration timeline agreed with stakeholders - Budget approved for Granola licenses ## Instructions ### Step 1 — Assess Migration Scope ```markdown ## Migration Assessment Source tool: [Otter.ai / Fireflies / Fathom / tl;dv / Manual / Other] Total meetings in source: [____] Date range: [____] to [____] Active users to migrate: [____] Integrations to recreate: [Slack, Notion, CRM, etc.] Historical data priority: [Archive all / Selective / Fresh start] Target cutover date: [____] Parallel run duration: [1 week / 2 weeks] ``` ### Step 2 — Source-Specific Export #### From Otter.ai - **Export format:** TXT, SRT (subtitles), PDF - **Bulk export:** Otter Pro/Business: Settings > Export > Download All - **Limitations:** Free plan only exports individual notes - **Key data:** Transcripts with timestamps, speaker labels, action items #### From Fireflies.ai - **Export format:** TXT, JSON, PDF, SRT - **Bulk export:** Admin > Data Management > Export - **Limitations:** Custom fields m...