Migrate from Recall.ai

What it does

Point the tool at your existing Recall.ai project and it works in four passes:

1. Scan: recursively finds Recall base URLs, endpoint calls, field names, webhook handlers, SDK imports, and RECALL_API_KEY usage.
2. Map: prints endpoint, field, and webhook mapping tables so you can see every change before it happens.
3. Transform: rewrites base URLs, endpoint paths, field names, webhook event handling, env vars, and imports.
4. Report: summarizes what changed, warns on anything that needs manual review, and prints a post-migration checklist.

Run it in scan or --dry-run mode as many times as you like. Nothing is written until you confirm.

Install & run

# Scan only (no changes)
npx @meetstream/migrate scan /path/to/your-recall-project
# Dry run: see the full diff
npx @meetstream/migrate --dry-run /path/to/your-recall-project
# Migrate (asks for confirmation first)
npx @meetstream/migrate /path/to/your-recall-project
# Verify against the live API after migrating
npx @meetstream/migrate test --api-key YOUR_MEETSTREAM_API_KEY
# Full lifecycle test against a real meeting
npx @meetstream/migrate test --api-key YOUR_KEY --meeting-url https://meet.google.com/xxx-xxxx-xxx

What gets rewritten

Endpoints

Fields

Webhooks

Recall’s webhook becomes either a signed workspace webhook endpoint or a per-bot callback_url, and Recall’s string events map onto MeetStream’s event model:

• Every payload carries event and bot_event. Branch on bot_event.
• A bot’s ending arrives once, as event: "bot.stopped", with the cause in bot_event: bot.stopped, bot.kicked, bot.denied, bot.notallowed or bot.failed.
• bot.done marks the end of post-call processing for every bot.

Before finalizing your handlers, read Webhooks and Events, or have your assistant call the webhook_events_guide tool on the MeetStream MCP server.

Capability comparison

Checked on September 24, 2026. MeetStream facts come from the product; Recall.ai facts come from Recall.ai’s public documentation and website, linked in the notes below. Only capabilities we could verify on both sides are listed.

Where MeetStream goes further

Available on both

Where Recall.ai goes further

Notes (all checked September 24, 2026)

1. Recall.ai, Storage and playback: docs.recall.ai/docs/storage-and-playback
2. Recall.ai pricing: recall.ai/pricing
3. Recall.ai, separate audio per participant (real-time): docs.recall.ai/docs/how-to-get-separate-audio-per-participant-realtime
4. Recall.ai, separate video per participant (real-time): docs.recall.ai/docs/how-to-get-separate-videos-per-participant-realtime
5. Recall.ai, Output Media: docs.recall.ai/docs/stream-media
6. Recall.ai, Transcription: docs.recall.ai/docs/transcription
7. Recall.ai, Calendar integration: docs.recall.ai/docs/calendar-integration
8. Recall.ai, Bot overview (supported platforms): docs.recall.ai/docs/bot-overview
9. Recall.ai, Zoom breakout rooms: docs.recall.ai/docs/zoom-breakout-rooms
10. Recall.ai, Zoom webinars and registration-required meetings: docs.recall.ai/docs/zoom-webinars
11. Recall.ai website, security section (SOC 2 Type 2 report): recall.ai

What the migrator flags for review

The migrator flags Recall.ai calls that have no one-to-one MeetStream equivalent, most notably live video output into the meeting. On MeetStream, bots can show a still or animated image with Send Image, and MIA voice agents can speak in the meeting. Everything in the endpoint and field tables migrates automatically.

After migrating

1. Swap RECALL_API_KEY for MEETSTREAM_API_KEY in your environment and secrets manager.
2. Change the auth header to Authorization: Token <your-key>.
3. Receive events through a workspace webhook endpoint (signed) or callback_url on create_bot.
4. Run test --api-key ... (optionally with --meeting-url) to confirm the live API responds as expected.
5. Review anything the report flagged for manual attention.