Agent skill

Granola Migration Deep Dive

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking.

MITAuto-check passedKnowledge Management

Install Granola Migration Deep Dive

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-migration-deep-dive -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace granola-migration-deep-dive --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/granola-migration-deep-dive .claude/skills/granola-migration-deep-dive && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
granola-migration-deep-dive
GitHub stars
2.8k
Token cost
~2.4k tokens
SKILL.md length
761 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking.

  • Works in 7 steps: Assess Migration Scope → Source-Specific Export → Choose Migration Strategy → …
  • Tasks that involve Note-taking
  • SKILL.md covers Overview, Prerequisites, Instructions and Key Differences from Bot-Based…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Granola Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking. Covers data export from source tools, parallel-run strategy, team transition, and historical data preservation. Trigger: "migrate to granola", "switch to granola", "granola from otter", "granola from fireflies", "replace meeting tool with granola".

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Knowledge Management, covering Note-taking. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Tasks that involve Note-taking

Example prompts

  • “migrate to granola”
  • “switch to granola”
  • “granola from otter”
  • “/granola-migration-deep-dive”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(python3:*)

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Assess Migration Scope
  2. Source-Specific Export
  3. Choose Migration Strategy
  4. Archive Historical Data
  5. Parallel Run (2 Weeks)
  6. Cutover Execution
  7. Post-Migration Optimization

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(python3:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • granola.ai
    • docs.granola.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Granola Migration Deep Dive loads about 2.4k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 761 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 761 words, ~2,409 tokens.

Download SKILL.mdSave it as .claude/skills/granola-migration-deep-dive/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
granola-migration-deep-dive
description
Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking. Covers data export from source tools, parallel-run strategy, team transition, and historical data preservation. Trigger: "migrate to granola", "switch to granola", "granola from otter", "granola from fireflies", "replace meeting tool with granola".
allowed-tools
Read, Write, Edit, Bash(python3:*)
compatibility
Designed for Claude Code
version
1.13.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, granola, migration

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 may not export
  • Key data: Transcripts, AI summaries, custom topics
From Fathom
  • Export format: Markdown, CSV, video clips
  • Bulk export: Settings > Data > Export All
  • Limitations: Video clips don't transfer
  • Key data: Meeting summaries, action items, highlights
From tl;dv
  • Export format: TXT, video recordings
  • Bulk export: Settings > Data Export
  • Limitations: AI highlights may not transfer
  • Key data: Transcripts, timestamps, meeting recordings
From Manual Notes (Google Docs, Notion, Confluence)
  • Already in accessible format
  • No export needed — archive in place
  • Focus on establishing the Granola workflow going forward
Step 3 — Choose Migration Strategy
StrategyWhen to UseData HandlingEffort
Fresh Start<100 historical meetings, or meetings have low reference valueArchive source data externally, start fresh in GranolaLow
Selective Migration100-1000 meetings, some have ongoing reference valueExport key meetings (client calls, decisions, contracts)Medium
Full ArchiveEnterprise with compliance requirements, everything must be searchableExport all data, archive in Notion/Drive/cloud storageHigh

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).

Step 4 — Archive Historical Data

For important historical meetings, archive before cutting over:

python
#!/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.

Step 5 — Parallel Run (2 Weeks)

Run both tools simultaneously to build confidence:

Week 1: Dual recording

  • Keep source tool active (bot still joins or captures)
  • Enable Granola on all meetings (system audio capture)
  • Compare output quality daily:
MetricSource ToolGranolaWinner
Transcription accuracy___%___%
Action item detection___/total___/total
Summary quality___/5___/5
Processing time___ min___ min
User experience (no bot)N/AYesGranola

Week 2: Granola primary

  • Keep source tool as backup only (disable auto-record if possible)
  • All sharing and distribution via Granola integrations
  • Team members report any quality issues
Show full SKILL.md (333 more words)Show less
Step 6 — Cutover Execution

Cutover day checklist:

  • Final export from source tool (last day of data)
  • Verify archive is complete and accessible
  • Disable source tool recording/bot
  • Remove source tool bot from calendar (if applicable)
  • Cancel source tool subscription (save on unused billing)
  • Announce to team via email/Slack:
markdown
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!
  • Monitor for 3 days:
    • Capture rate (% of meetings recorded)
    • Support ticket volume
    • User feedback
    • Integration sync health
Step 7 — Post-Migration Optimization

After 1 week on Granola exclusively:

  • Configure templates for each meeting type (see granola-core-workflow-a)
  • Set up Zapier automation for recurring workflows
  • Create custom recipes for team-specific post-meeting tasks
  • Establish folder structure matching team workflow
  • Delete source tool accounts and data (if no longer needed)

Key Differences from Bot-Based Tools

FeatureBot-Based (Otter, Fireflies, tl;dv)Granola
Meeting joinBot joins as participantNo bot — system audio capture
Participant awareness"Bot is recording" bannerNo banner (still announce recording for consent)
Platform supportPlatform-specific integrationsAny platform (captures system audio)
Typed notesSeparate appBuilt-in notepad merges with transcript
EnhancementAuto-generatedUser-controlled (click Enhance)
TemplatesLimited29 built-in + custom
ChatLimited or noneFull Granola Chat with Recipes
Built-in CRMNoPeople & Companies

Output

  • Source data exported and archived
  • Parallel run completed with quality validation
  • Team migrated and recording in Granola
  • Source tool deactivated and subscription cancelled
  • Historical data accessible in archive

Error Handling

ErrorCauseFix
Source export incompleteFree plan limits bulk exportUpgrade source plan temporarily for export, then cancel
Team resistance to changeComfort with existing toolShare quality comparison data from parallel run
Missing historical contextNo import feature in GranolaPoint team to archived data (Notion/Drive)
Audio quality different than botSystem audio vs. platform APIOptimize audio setup (see granola-performance-tuning)
Low adoption post-migrationSetup issuesRun drop-in support sessions, share quick-start guide

Examples

cohort=synthetic-meetings-01; baseline=420; migrated=420; consent=pass; destination=approved; retention=none; cutover=held; rollback=old-client-r8 documents a safe rehearsal.

Resources

Next Steps

After migration, explore granola-performance-tuning to optimize output quality.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/granola-migration-deep-dive of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Granola Migration Deep Dive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Granola Migration Deep Dive compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Granola Migration Deep Dive this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.4kAutomated safety check: PassMIT
CLI Hub Matrix Knowledge ResearchHKUDS/CLI-Anything52k—~2.8kAutomated safety check: PassApache-2.0
Obsidian Knowledge BuilderMichael-OvO/obsidian-knowledge-agent205—~917Automated safety check: PassMIT
Bulletmindsickn33/agentic-awesome-skills47k1 repos~916Automated safety check: PassMIT
Granolaglebis/claude-skills391—~874Automated safety check: NotesMIT
Qmdalsk1992/CloddsBot3k3 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Capability-based multi-tool matrix for research, note-taking, document authoring, and publishing.

    52k GitHub stars~2.8k tokensUpdated 19 days ago
    Knowledge ManagementAuto-check passed
  • Obsidian Knowledge Builder

    Michael-OvO/obsidian-knowledge-agent

    Turns PDFs, slides, syllabi, papers and transcripts into structured, teaching-quality Obsidian notes, matching how much structure is built to how much the material needs.

    205 GitHub stars~917 tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed
  • Bulletmind

    sickn33/agentic-awesome-skills

    Convert input into clean, structured, hierarchical bullet points for summarization, note-taking, and structured thinking.

    47k GitHub starsUsed in 1 repo~916 tokens
    Knowledge ManagementAuto-check passed
  • Granola

    glebis/claude-skills

    This skill should be used when importing, listing, or exporting Granola meeting recordings and transcripts.

    391 GitHub stars~874 tokensUpdated 3 days ago
    Knowledge ManagementAuto-check: notes
  • Qmd

    alsk1992/CloddsBot

    Local hybrid search for markdown notes and docs. An agent skill from alsk1992/CloddsBot.

    3k GitHub starsUsed in 3 repos~1.2k tokens
    Knowledge ManagementAuto-check passed
  • Obsidian Canvas Boards

    AgriciDaniel/claude-obsidian

    Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.

    15k GitHub stars~1.4k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Granola Migration Deep Dive

What does Granola Migration Deep Dive do?

Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking. Granola Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace.ai, Fireflies, Fathom, tl;dv, or manual note-taking.

When should I use Granola Migration Deep Dive?

Granola Migration Deep Dive fits situations like: tasks that involve Note-taking.

How do I install Granola Migration Deep Dive in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-migration-deep-dive -a claude-code`. Or copy the skill folder (skills/.curated/granola-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/granola-migration-deep-dive in your project. Claude Code loads it when a task matches its description.

How do I install Granola Migration Deep Dive in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-migration-deep-dive -a codex`. Or copy the skill folder (skills/.curated/granola-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/granola-migration-deep-dive in your project. Codex loads it when a task matches its description.

Can I use Granola Migration Deep Dive in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-migration-deep-dive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/granola-migration-deep-dive, .gemini/skills/granola-migration-deep-dive, .github/skills/granola-migration-deep-dive and .opencode/skills/granola-migration-deep-dive in your project.

What does Granola Migration Deep Dive need to run?

SKILL.md names no scripts, command-line tools or credentials: Granola Migration Deep Dive is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(python3:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Granola Migration Deep Dive access the network?

SKILL.md names 2 domains. As links in the text: granola.ai and docs.granola.ai. This is read from the text; nothing was executed.

Is Granola Migration Deep Dive safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Granola Migration Deep Dive use?

Granola Migration Deep Dive is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Granola Migration Deep Dive use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Granola Migration Deep Dive?

Skills that share tags, products or a category with Granola Migration Deep Dive: CLI Hub Matrix Knowledge Research (HKUDS/CLI-Anything, 52k stars), Obsidian Knowledge Builder (Michael-OvO/obsidian-knowledge-agent, 205 stars), Bulletmind (sickn33/agentic-awesome-skills, 47k stars) and Granola (glebis/claude-skills, 391 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Granola Migration Deep Dive?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.