Granola Migration Deep Dive

Contents

• Overview
• Prerequisites
• Instructions
• Output
• Error Handling
• Examples
• Resources

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

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

Examples

Quick Migration Assessment

- Total meetings to migrate: ___
- Date range: ___ to ___
- Strategy: Clean Start / Selective / Full
- Target cutover date: ___
- Parallel running: ___ weeks

Resources

• Granola Migration Guide
• Import Support
• Enterprise Migration Services

Next Steps

Proceed to granola-performance-tuning for optimization.