Granola Migration Deep Dive
Contents
Overview
Comprehensive guide for migrating to Granola from Otter.ai, Fireflies, Fathom, Zoom, Google Meet, or Microsoft Teams.
Prerequisites
- Access to source tool with export capability
- Granola workspace configured
- Migration timeline agreed with stakeholders
Migration Sources
| Tool |
Export Format |
Complexity |
| Otter.ai |
TXT, SRT, PDF |
Medium |
| Fireflies.ai |
TXT, JSON, PDF |
Medium |
| Fathom |
Markdown, CSV |
Low |
| Zoom/Meet/Teams |
VTT, TXT |
Low |
Instructions
Step 1: Choose Migration Strategy
- Clean Start (<100 meetings): Start fresh, archive history externally
- Selective (100-1000): Migrate key meetings only (client calls, decisions)
- Full (Enterprise): Export everything, transform, import all
Step 2: Assess and Inventory
Document total meetings, date range, storage size, content types, and integration dependencies.
Step 3: Export from Source
Follow source-specific export procedures (bulk export for Pro/Enterprise plans).
Step 4: Convert and Import
Run conversion scripts to transform source formats to Granola-compatible Markdown. Archive in Notion/Drive.
Step 5: Parallel Run (2 weeks)
Record in Granola as primary while keeping source as backup. Compare quality daily.
Step 6: Cutover
Final export from source, disable source recording, cancel subscription, monitor closely for 3 days.
See detailed implementation for source-specific export procedures, conversion scripts, execution timeline, communication templates, and rollback plan.
Output
- Source data exported and backed up
- Historical meetings converted and archived
- Granola configured with integrations
- Team migrated and recording in Granola
Error Handling
| Error |
Cause |
Solution |
| Missing transcripts |
Export format limitation |
Re-export in different format |
| Failed conversion |
Unexpected source format |
Update conversion script |
| Low adoption |
Insufficient training |
Add training sessions, share quick wins |
| Data gaps |
Incomplete export |
Run secondary export, verify counts |
Examples
Quick Migration Assessment
- Total meetings to migrate: ___
- Date range: ___ to ___
- Strategy: Clean Start / Selective / Full
- Target cutover date: ___
- Parallel running: ___ weeks
Resources
Next Steps
Proceed to granola-performance-tuning for optimization.
1---2name: granola-migration-deep-dive3description: Deep dive migration guide from other meeting note tools to Granola. Use when migrating from Otter.ai, Fireflies, Fathom, or other tools, planning data migration, or executing transition strategies. Trigger with phrases like "migrate to granola", "switch to granola", "granola from otter", "granola from fireflies", "granola migration".4license: MIT5---6# Granola Migration Deep Dive78## Contents9- [Overview](#overview)10- [Prerequisites](#prerequisites)11- [Instructions](#instructions)12- [Output](#output)13- [Error Handling](#error-handling)14- [Examples](#examples)15- [Resources](#resources)1617## Overview18Comprehensive guide for migrating to Granola from Otter.ai, Fireflies, Fathom, Zoom, Google Meet, or Microsoft Teams.1920## Prerequisites21- Access to source tool with export capability22- Granola workspace configured23- Migration timeline agreed with stakeholders2425## Migration Sources2627| Tool | Export Format | Complexity |28|------|-------------|------------|29| Otter.ai | TXT, SRT, PDF | Medium |30| Fireflies.ai | TXT, JSON, PDF | Medium |31| Fathom | Markdown, CSV | Low |32| Zoom/Meet/Teams | VTT, TXT | Low |3334## Instructions3536### Step 1: Choose Migration Strategy37- **Clean Start** (<100 meetings): Start fresh, archive history externally38- **Selective** (100-1000): Migrate key meetings only (client calls, decisions)39- **Full** (Enterprise): Export everything, transform, import all4041### Step 2: Assess and Inventory42Document total meetings, date range, storage size, content types, and integration dependencies.4344### Step 3: Export from Source45Follow source-specific export procedures (bulk export for Pro/Enterprise plans).4647### Step 4: Convert and Import48Run conversion scripts to transform source formats to Granola-compatible Markdown. Archive in Notion/Drive.4950### Step 5: Parallel Run (2 weeks)51Record in Granola as primary while keeping source as backup. Compare quality daily.5253### Step 6: Cutover54Final export from source, disable source recording, cancel subscription, monitor closely for 3 days.5556See [detailed implementation](${CLAUDE_SKILL_DIR}/references/implementation.md) for source-specific export procedures, conversion scripts, execution timeline, communication templates, and rollback plan.5758## Output59- Source data exported and backed up60- Historical meetings converted and archived61- Granola configured with integrations62- Team migrated and recording in Granola6364## Error Handling65| Error | Cause | Solution |66|-------|-------|----------|67| Missing transcripts | Export format limitation | Re-export in different format |68| Failed conversion | Unexpected source format | Update conversion script |69| Low adoption | Insufficient training | Add training sessions, share quick wins |70| Data gaps | Incomplete export | Run secondary export, verify counts |7172## Examples7374### Quick Migration Assessment75```markdown76- Total meetings to migrate: ___77- Date range: ___ to ___78- Strategy: Clean Start / Selective / Full79- Target cutover date: ___80- Parallel running: ___ weeks81```8283## Resources84- [Granola Migration Guide](https://granola.ai/help/migration)85- [Import Support](https://granola.ai/support)86- [Enterprise Migration Services](https://granola.ai/enterprise)8788## Next Steps89Proceed to `granola-performance-tuning` for optimization.
micsapp