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: |4 Deep dive migration guide from other meeting note tools to Granola.5 Use when migrating from Otter.ai, Fireflies, Fathom, or other tools,6 planning data migration, or executing transition strategies.7 Trigger with phrases like "migrate to granola", "switch to granola",8 "granola from otter", "granola from fireflies", "granola migration".9allowed-tools: Read, Write, Edit10version: 1.0.011license: MIT12author: Jeremy Longshore <jeremy@intentsolutions.io>13compatible-with: claude-code, codex, openclaw14metadata:15 source: https://skillmd.com/skills/micsapp/granola-migration-deep-dive16---1718# Granola Migration Deep Dive1920## Contents21- [Overview](#overview)22- [Prerequisites](#prerequisites)23- [Instructions](#instructions)24- [Output](#output)25- [Error Handling](#error-handling)26- [Examples](#examples)27- [Resources](#resources)2829## Overview30Comprehensive guide for migrating to Granola from Otter.ai, Fireflies, Fathom, Zoom, Google Meet, or Microsoft Teams.3132## Prerequisites33- Access to source tool with export capability34- Granola workspace configured35- Migration timeline agreed with stakeholders3637## Migration Sources3839| Tool | Export Format | Complexity |40|------|-------------|------------|41| Otter.ai | TXT, SRT, PDF | Medium |42| Fireflies.ai | TXT, JSON, PDF | Medium |43| Fathom | Markdown, CSV | Low |44| Zoom/Meet/Teams | VTT, TXT | Low |4546## Instructions4748### Step 1: Choose Migration Strategy49- **Clean Start** (<100 meetings): Start fresh, archive history externally50- **Selective** (100-1000): Migrate key meetings only (client calls, decisions)51- **Full** (Enterprise): Export everything, transform, import all5253### Step 2: Assess and Inventory54Document total meetings, date range, storage size, content types, and integration dependencies.5556### Step 3: Export from Source57Follow source-specific export procedures (bulk export for Pro/Enterprise plans).5859### Step 4: Convert and Import60Run conversion scripts to transform source formats to Granola-compatible Markdown. Archive in Notion/Drive.6162### Step 5: Parallel Run (2 weeks)63Record in Granola as primary while keeping source as backup. Compare quality daily.6465### Step 6: Cutover66Final export from source, disable source recording, cancel subscription, monitor closely for 3 days.6768See [detailed implementation](${CLAUDE_SKILL_DIR}/references/implementation.md) for source-specific export procedures, conversion scripts, execution timeline, communication templates, and rollback plan.6970## Output71- Source data exported and backed up72- Historical meetings converted and archived73- Granola configured with integrations74- Team migrated and recording in Granola7576## Error Handling77| Error | Cause | Solution |78|-------|-------|----------|79| Missing transcripts | Export format limitation | Re-export in different format |80| Failed conversion | Unexpected source format | Update conversion script |81| Low adoption | Insufficient training | Add training sessions, share quick wins |82| Data gaps | Incomplete export | Run secondary export, verify counts |8384## Examples8586### Quick Migration Assessment87```markdown88- Total meetings to migrate: ___89- Date range: ___ to ___90- Strategy: Clean Start / Selective / Full91- Target cutover date: ___92- Parallel running: ___ weeks93```9495## Resources96- [Granola Migration Guide](https://granola.ai/help/migration)97- [Import Support](https://granola.ai/support)98- [Enterprise Migration Services](https://granola.ai/enterprise)99100## Next Steps101Proceed to `granola-performance-tuning` for optimization.