fireflies-migration-deep-dive
Migrate to Fireflies.ai from other meeting transcription platforms or legacy recording systems. Use when switching from Otter.ai, Rev, or custom transcription to Fireflies, or importing historical meeting data into the Fireflies ecosystem. Trigger with phrases like "migrate to fireflies", "switch from otter", "fireflies migration", "import meetings to fireflies", "fireflies replatform".
Best use case
fireflies-migration-deep-dive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Migrate to Fireflies.ai from other meeting transcription platforms or legacy recording systems. Use when switching from Otter.ai, Rev, or custom transcription to Fireflies, or importing historical meeting data into the Fireflies ecosystem. Trigger with phrases like "migrate to fireflies", "switch from otter", "fireflies migration", "import meetings to fireflies", "fireflies replatform".
Teams using fireflies-migration-deep-dive should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/fireflies-migration-deep-dive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fireflies-migration-deep-dive Compares
| Feature / Agent | fireflies-migration-deep-dive | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Migrate to Fireflies.ai from other meeting transcription platforms or legacy recording systems. Use when switching from Otter.ai, Rev, or custom transcription to Fireflies, or importing historical meeting data into the Fireflies ecosystem. Trigger with phrases like "migrate to fireflies", "switch from otter", "fireflies migration", "import meetings to fireflies", "fireflies replatform".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Fireflies.ai Migration Deep Dive
## Current State
!`npm list graphql graphql-request 2>/dev/null || echo 'No graphql packages'`
## Overview
Migrate to Fireflies.ai from other transcription platforms or custom recording systems. Covers historical recording import via `uploadAudio`, adapter pattern for gradual cutover, and data validation post-migration.
## Migration Types
| Scenario | Approach | Timeline |
|----------|----------|----------|
| Fresh start (no history) | Configure Fireflies bot, done | 1 day |
| Import recordings | Batch `uploadAudio` | 1-2 weeks |
| Switch from competitor | Parallel run + gradual cutover | 2-4 weeks |
| Enterprise rollout | Phased department-by-department | 1-2 months |
## Instructions
### Step 1: Pre-Migration Assessment
```typescript
// Inventory your current meeting data
interface MigrationInventory {
totalRecordings: number;
totalHours: number;
formats: string[]; // mp3, mp4, wav, m4a, ogg
averageDuration: number; // minutes
dateRange: { oldest: string; newest: string };
platforms: string[]; // Zoom, Teams, etc.
}
// Fireflies supports: mp3, mp4, wav, m4a, ogg
// Size limits: 200MB audio, 100MB video (free), 1.5GB video (paid)
// Minimum: 50KB (can bypass with bypass_size_check: true)
```
### Step 2: Batch Upload Historical Recordings
```typescript
const FIREFLIES_API = "https://api.fireflies.ai/graphql";
interface UploadJob {
url: string; // Must be publicly accessible HTTPS URL
title: string;
attendees?: { displayName: string; email: string }[];
referenceId: string; // Your internal ID for tracking
}
async function batchUpload(jobs: UploadJob[]) {
const results: { id: string; status: string; error?: string }[] = [];
for (const job of jobs) {
try {
const res = await fetch(FIREFLIES_API, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${process.env.FIREFLIES_API_KEY}`,
},
body: JSON.stringify({
query: `
mutation($input: AudioUploadInput) {
uploadAudio(input: $input) {
success title message
}
}
`,
variables: {
input: {
url: job.url,
title: job.title,
attendees: job.attendees,
client_reference_id: job.referenceId,
webhook: process.env.WEBHOOK_URL,
},
},
}),
});
const json = await res.json();
if (json.errors) {
results.push({ id: job.referenceId, status: "error", error: json.errors[0].message });
} else {
results.push({ id: job.referenceId, status: "uploaded" });
}
} catch (err) {
results.push({ id: job.referenceId, status: "error", error: (err as Error).message });
}
// Rate limit: wait between uploads
await new Promise(r => setTimeout(r, 2000));
}
return results;
}
```
### Step 3: Upload with Authenticated URLs
If your recordings are behind auth (S3, GCS):
```typescript
// Bearer token auth (e.g., pre-signed URLs with auth headers)
const upload = {
url: "https://storage.example.com/recordings/meeting-123.mp3",
title: "Q1 Planning",
download_auth: {
type: "bearer_token",
bearer: { token: "your-storage-access-token" },
},
client_reference_id: "meeting-123",
};
// Basic auth
const uploadBasicAuth = {
url: "https://recordings.example.com/files/meeting-456.mp3",
title: "Sprint Review",
download_auth: {
type: "basic_auth",
basic: { username: "api-user", password: "api-pass" },
},
client_reference_id: "meeting-456",
};
```
### Step 4: Direct File Upload (No Public URL)
For files that can't be made publicly accessible:
```typescript
// Step 1: Get a pre-signed upload URL from Fireflies
const { createUploadUrl } = await firefliesQuery(`
mutation($input: CreateUploadUrlInput!) {
createUploadUrl(input: $input) {
url
meeting_id
}
}
`, { input: { /* file metadata */ } });
// Step 2: Upload file directly to the pre-signed URL
await fetch(createUploadUrl.url, {
method: "PUT",
body: fileBuffer,
});
// Step 3: Confirm the upload
await firefliesQuery(`
mutation($input: ConfirmUploadInput!) {
confirmUpload(input: $input) {
success
}
}
`, { input: { meeting_id: createUploadUrl.meeting_id } });
```
### Step 5: Track Migration Progress via Webhooks
```typescript
// Webhook handler tracks which uploads have completed
const migrationTracker = new Map<string, { status: string; meetingId?: string }>();
async function handleMigrationWebhook(event: any) {
if (event.eventType === "Transcription completed" && event.clientReferenceId) {
migrationTracker.set(event.clientReferenceId, {
status: "completed",
meetingId: event.meetingId,
});
// Check progress
const completed = [...migrationTracker.values()].filter(v => v.status === "completed").length;
const total = migrationTracker.size;
console.log(`Migration progress: ${completed}/${total} (${Math.round(completed/total*100)}%)`);
}
}
```
### Step 6: Validate Migration
```typescript
async function validateMigration(expectedIds: string[]) {
const results = {
found: 0,
missing: [] as string[],
hasSummary: 0,
hasSentences: 0,
};
for (const refId of expectedIds) {
const tracker = migrationTracker.get(refId);
if (!tracker?.meetingId) {
results.missing.push(refId);
continue;
}
results.found++;
// Verify transcript quality
const { transcript } = await firefliesQuery(`
query($id: String!) {
transcript(id: $id) {
id title
sentences { text }
summary { overview action_items }
}
}
`, { id: tracker.meetingId });
if (transcript.summary?.overview) results.hasSummary++;
if (transcript.sentences?.length > 0) results.hasSentences++;
await new Promise(r => setTimeout(r, 1100)); // Rate limit
}
console.log(`Validation: ${results.found}/${expectedIds.length} found`);
console.log(`With summary: ${results.hasSummary}`);
console.log(`With sentences: ${results.hasSentences}`);
console.log(`Missing: ${results.missing.length}`);
return results;
}
```
### Step 7: Adapter Pattern for Gradual Cutover
```typescript
interface TranscriptionService {
getTranscript(id: string): Promise<any>;
searchTranscripts(query: string): Promise<any[]>;
}
class FirefliesService implements TranscriptionService {
async getTranscript(id: string) {
return firefliesQuery(`
query($id: String!) {
transcript(id: $id) {
id title date duration
sentences { speaker_name text start_time end_time }
summary { overview action_items }
}
}
`, { id });
}
async searchTranscripts(query: string) {
const data = await firefliesQuery(`
query($keyword: String) {
transcripts(keyword: $keyword, limit: 20) {
id title date duration
}
}
`, { keyword: query });
return data.transcripts;
}
}
// Gradual cutover with feature flag
function getTranscriptionService(): TranscriptionService {
if (process.env.USE_FIREFLIES === "true") {
return new FirefliesService();
}
return new LegacyTranscriptionService();
}
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| `payload_too_small` | File < 50KB | Set `bypass_size_check: true` |
| Upload rejected | Free plan | Uploads require Pro+ plan |
| Auth download fails | Token expired | Refresh storage credentials |
| Missing transcription | Audio quality poor | Check file format and audio clarity |
| Duplicate uploads | Re-running batch | Use `client_reference_id` for dedup |
## Output
- Pre-migration inventory assessed
- Historical recordings uploaded via `uploadAudio` mutation
- Migration progress tracked via webhooks and `clientReferenceId`
- Post-migration validation confirming transcript quality
- Adapter layer enabling gradual platform cutover
## Resources
- [Upload Audio Mutation](https://docs.fireflies.ai/graphql-api/mutation/upload-audio)
- [Fireflies API Docs](https://docs.fireflies.ai/)
## Next Steps
For monitoring the migrated system, see `fireflies-observability`.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".