fireflies-migration-deep-dive
Provides strategies and step-by-step guides for migrating to Fireflies.ai from legacy transcription platforms.
Install
mkdir -p .claude/skills/fireflies-migration-deep-dive && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5386" && unzip -o skill.zip -d .claude/skills/fireflies-migration-deep-dive && rm skill.zipInstalls to .claude/skills/fireflies-migration-deep-dive
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Migrate to Fireflies.ai from other meeting transcription platforms orKey capabilities
- →Assess existing meeting data inventory
- →Batch upload historical recordings via GraphQL
- →Handle authenticated storage URLs for imports
- →Track migration progress using webhooks
- →Implement adapter patterns for gradual cutover
How it works
The migration process involves inventorying existing data, batching uploads via the uploadAudio mutation, and using an adapter pattern to switch between legacy and Fireflies services during a phased rollout.
Inputs & outputs
When to use fireflies-migration-deep-dive
- →Importing historical meeting data into Fireflies.ai
- →Switching from competitor transcription platforms
- →Executing gradual platform cutover using the adapter pattern
- →Performing pre-migration data inventory assessment
About this skill
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
// 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
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):
// 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:
// 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
// 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
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
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
uploadAudiomutation - Migration progress tracked via webhooks and
clientReferenceId - Post-migration validation confirming transcript quality
- Adapter layer enabling gradual platform cutover
Resources
Next Steps
For monitoring the migrated system, see fireflies-observability.
When not to use it
- →Systems requiring immediate, non-gradual platform replacement
- →Environments without access to public HTTPS recording URLs
Prerequisites
Limitations
- →Uploads require a Pro+ plan
- →Files under 50KB require bypass_size_check: true
How it compares
This workflow uses a strangler fig pattern for gradual cutover rather than a high-risk, all-at-once platform migration.
Compared to similar skills
fireflies-migration-deep-dive side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fireflies-migration-deep-dive (this skill) | 1 | 27d | Caution | Advanced |
| opencode-cli | 14 | 7mo | Review | Advanced |
| claude-automation-recommender | 47 | 2mo | Review | Beginner |
| mcp-integration | 21 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
hook-development
anthropics
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
pdf-processing-pro
davila7
Production-ready PDF processing with forms, tables, OCR, validation, and batch operations. Use when working with complex PDF workflows in production environments, processing large volumes of PDFs, or requiring robust error handling and validation.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns