Stats
Actions
Tags
From granola-pack
Guides migration to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual notes via exports, parallel runs, team transitions, and historical data preservation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/granola-pack:granola-migration-deep-diveThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
granola-install-auth)## 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]
| Strategy | When to Use | Data Handling | Effort |
|---|---|---|---|
| Fresh Start | <100 historical meetings, or meetings have low reference value | Archive source data externally, start fresh in Granola | Low |
| Selective Migration | 100-1000 meetings, some have ongoing reference value | Export key meetings (client calls, decisions, contracts) | Medium |
| Full Archive | Enterprise with compliance requirements, everything must be searchable | Export all data, archive in Notion/Drive/cloud storage | High |
Recommended for most teams: Fresh Start or Selective. Granola doesn't import historical data from other tools — there's no import feature. Historical data lives in your archive (Notion, Google Drive, local files).
For important historical meetings, archive before cutting over:
#!/usr/bin/env python3
"""Organize exported meeting notes for archival."""
import os
from pathlib import Path
EXPORT_DIR = Path("~/Downloads/otter-export").expanduser() # Adjust for your source
ARCHIVE_DIR = Path("~/Documents/meeting-archive").expanduser()
# Create organized archive structure
categories = {
"client": ["client", "customer", "deal", "sales", "demo"],
"engineering": ["sprint", "standup", "architecture", "review", "retro"],
"product": ["product", "prd", "design", "feedback", "roadmap"],
"leadership": ["all-hands", "board", "strategy", "planning"],
"general": [], # catch-all
}
ARCHIVE_DIR.mkdir(parents=True, exist_ok=True)
for cat in categories:
(ARCHIVE_DIR / cat).mkdir(exist_ok=True)
for file in EXPORT_DIR.glob("*.txt"):
filename_lower = file.name.lower()
placed = False
for cat, keywords in categories.items():
if any(kw in filename_lower for kw in keywords):
dest = ARCHIVE_DIR / cat / file.name
file.rename(dest)
placed = True
break
if not placed:
(ARCHIVE_DIR / "general" / file.name).rename(file)
print(f"Archived to {ARCHIVE_DIR}")
Alternatively, upload the archive to Notion or Google Drive for team-wide searchability.
Run both tools simultaneously to build confidence:
Week 1: Dual recording
| Metric | Source Tool | Granola | Winner |
|---|---|---|---|
| Transcription accuracy | ___% | ___% | |
| Action item detection | ___/total | ___/total | |
| Summary quality | ___/5 | ___/5 | |
| Processing time | ___ min | ___ min | |
| User experience (no bot) | N/A | Yes | Granola |
Week 2: Granola primary
Cutover day checklist:
Subject: Meeting Notes Migration Complete — Granola is Now Primary
Team,
As of today, we've completed our migration to Granola for meeting notes.
What's changed:
- No more [Otter/Fireflies/etc.] bot joining meetings
- Granola captures audio directly from your device (no bot visible to participants)
- Notes are auto-enhanced with AI summaries and action items
What you need to do:
1. Ensure Granola is running on your device
2. Verify your calendar is connected (Settings > Calendar)
3. Check that microphone + Screen & System Audio permissions are granted
Historical notes: Archived at [Notion link / Drive folder]
Support: Post in #granola-support
Thank you for the smooth transition!
After 1 week on Granola exclusively:
granola-core-workflow-a)| Feature | Bot-Based (Otter, Fireflies, tl;dv) | Granola |
|---|---|---|
| Meeting join | Bot joins as participant | No bot — system audio capture |
| Participant awareness | "Bot is recording" banner | No banner (still announce recording for consent) |
| Platform support | Platform-specific integrations | Any platform (captures system audio) |
| Typed notes | Separate app | Built-in notepad merges with transcript |
| Enhancement | Auto-generated | User-controlled (click Enhance) |
| Templates | Limited | 29 built-in + custom |
| Chat | Limited or none | Full Granola Chat with Recipes |
| Built-in CRM | No | People & Companies |
| Error | Cause | Fix |
|---|---|---|
| Source export incomplete | Free plan limits bulk export | Upgrade source plan temporarily for export, then cancel |
| Team resistance to change | Comfort with existing tool | Share quality comparison data from parallel run |
| Missing historical context | No import feature in Granola | Point team to archived data (Notion/Drive) |
| Audio quality different than bot | System audio vs. platform API | Optimize audio setup (see granola-performance-tuning) |
| Low adoption post-migration | Setup issues | Run drop-in support sessions, share quick-start guide |
After migration, explore granola-performance-tuning to optimize output quality.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin granola-packManages Granola meeting data exports via local cache Python script, retention policies, GDPR/CCPA compliance, archival workflows, and data rights requests.
Migrates meeting transcriptions to Fireflies.ai from Otter.ai, Rev, or legacy systems via GraphQL batch audio uploads and historical data import.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.