Agent skill · marketing growth · jeremylongshore
granola-upgrade-migration
Upgrade Granola app versions and migrate between subscription plans.
Why this skill is useful
Provides specific commands and procedures for upgrading and migrating the Granola app that are not widely documented.
What it needs
Requires brew installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Granola Upgrade & Migration Overview Manage Granola desktop app updates and subscription plan changes. Granola auto-updates by default, but manual intervention may be needed for major versions or plan migrations that affect feature access. Prerequisites Current Granola version info (Granola menu > About, or check via CLI) Admin access for organization-level plan changes Data backup awareness before downgrading Instructions Step 1 — Check Current Version Check for available updates: Granola menu bar icon > Check for Updates, or visit granola.ai/updates for the changelog. Step 2 — Update the Desktop App Auto-update (recommended): Granola checks for updates automatically and downloads in the background. Enable at: Manual update via Homebrew (macOS): Manual download: Download latest from granola.ai/download. Close Granola, install over the existing version. Settings and data are preserved. Step 3 — Handle Update Issues If Granola crashes or behaves incorrectly after updating: Your meeting data is stored server-side and in the local cache (~/Library/Application Support/Granola/cache-v3.json). Reinstalling does not delete your notes. Step 4 — Upgrade Subscription Plan Step 5 — Downgrade with Data Preservation Before downgrading, understand what you lose: Downgrading From Losing Action Before Downgrade ----------------- -------- ---------------------- Business → Basic Integrations disconnect, history limited to 14 days Export all notes, save integration configs Enterprise → Business SSO, SCIM, custom retention, analytics Reconfigure authentication, manual user provisioning Pre-downgrade checklist: 1. Notify team members of the change 2. Export critical notes (there is no bulk export — share important notes to Notion or copy individually) 3. Document active integration configurations 4. Save any custom templates and recipes 5. Verify API consumers are prepared for access loss Important: Downgrading does not delete your data. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/granola-upgrade-migration