meetstream-migrate

One-command migration from Recall.ai to MeetStream.ai. Scans your codebase, maps every API call, shows the diff, and migrates — safely, with warnings for anything that needs a human look.

v2.1.2 — near feature parity with Recall.ai (verified live against production, July 2026). MeetStream matches Recall across recording, per-participant streams, real-time audio/video/ transcript, chat + image output, Google and Outlook calendar, scheduling, signed-in bots, and retention — plus native AI summaries and MIA voice agents that Recall doesn't have. The only gaps: pause/resume recording and live video output into the call (both shipping soon). See Feature parity & gaps below.

Quick Start

pip install meetstream-migrate
meetstream-migrate scan ./your-recall-project

Commands

# Scan (read-only) — finds every Recall.ai reference, writes NOTHING
meetstream-migrate scan ./your-project

# Dry run — shows exactly what would change, still writes nothing
meetstream-migrate migrate ./your-project --dry-run

# Migrate — applies all transformations (prompts before writing)
meetstream-migrate migrate ./your-project --yes

# Verify your MeetStream credentials + API reachability
meetstream-migrate test --api-key YOUR_MEETSTREAM_API_KEY

CLI reference

meetstream-migrate <command> [path] [options]

Commands:
  scan [path]        Scan only — show what would change
  migrate [path]     Scan & migrate a project
  test                Run API tests against MeetStream.ai

Options:
  --yes, -y          Skip the confirmation prompt
  --dry-run          Show changes without writing files
  --api-key KEY      MeetStream API key (for the test command)
  --verbose, -v      Detailed output
  --help, -h         Show help

What it does

1. Scan — recursively finds:

• Recall.ai base URLs (us-east-1.recall.ai, eu-west-1.recall.ai, api.recall.ai)
• API endpoint calls (/api/v1/bot/, /api/v1/bot/{id}/audio/, etc.)
• Recall-specific field names (meeting_url, recording_mode, transcription_options, metadata, …)
• Webhook handlers (bot.status_change, joining_call, in_call_recording, call_ended, done, fatal, …)
• SDK imports (require('recall-ai'), import recall)
• Environment variables (RECALL_API_KEY, RECALL_API_URL, RECALL_WEBHOOK_SECRET)

Supported file types: .js .ts .jsx .tsx .mjs .cjs .py .go .rb .java .kt .rs .php .cs .swift .env .yaml .yml .json .toml .ini .cfg

2. Display — endpoint mapping table, field mapping table, webhook event mapping, and a compatibility check (auto-migratable vs. needs manual review).

3. Transform — base URL swap, endpoint path rewrites, field renames, webhook event renames, env var renames, import/require updates. Every change carries an inline warning when it needs a second look.

4. Report — what changed, what needs manual review, and a post-migration checklist.

Endpoint Mapping

Field Mapping

Webhook Events — live-verified against production

MeetStream's envelope key is event — the same key Recall uses. No envelope rename needed. Alongside it: bot_id, message, status_code (200 success / 500 failure), custom_attributes, and on lifecycle events, bot_status.

{ "event": "bot.inmeeting", "bot_id": "...", "bot_status": "InMeeting",
  "message": "...", "status_code": 200, "custom_attributes": {} }

Two-layer model: bot.stopped fires once; bot_status tells you why — Stopped (normal) / NotAllowed (lobby timeout) / Denied (host denied) / Error (crash). Recall's separate end-reason events collapse into this single event + status.

Streaming-only providers (deepgram_streaming, assemblyai_streaming, meeting_captions) do not fire transcription.processed/transcription.failed/bot.done — their terminal event is audio.processed. Don't wait on bot.done for a streaming bot, or your handler hangs forever.

transcript_id is never in the webhook payload. Resolve it via GET /bots/{id}/detail (bot_details.transcript_id), the create_bot response, or GET /bots/{id}/transcriptions.

Full bot_status enum: Joining, InWaitingRoom, InMeeting, Recording, Leaving, Stopped, NotAllowed, Denied, Error, Done.

Real-time events

Breaking changes to review manually

1. Transcript retrieval uses transcript_id (from the create_bot response, /detail, or /transcriptions), not bot_id.
2. recording_mode (Recall string) → video_required (MeetStream boolean).
3. Chat messages: Recall's separate POST /send_chat_message/ → MeetStream's POST /bots/{id}/send_message.
4. Webhook registration: Recall registers globally via POST /webhook/; MeetStream uses callback_url per bot at creation.
5. Webhook event values rename (see table above) — but the envelope key stays event, so most handler code needs a value rename, not a restructure.
6. Post-call processing arrives as discrete events (manifest.completed, audio.processed, transcription.processed/transcription.failed, video.processed, bot.done) instead of one bot.done-then-fetch signal.
7. Live transcription: real_time_transcription.destination_url → live_transcription_required.webhook_url on create_bot.
8. Pause/resume recording has no MeetStream equivalent yet — remove these calls, or segment via remove_bot + re-create.
9. Output audio/media into the call is REST on Recall, WebSocket-bridge on MeetStream — needs a real refactor, not a rename (flagged, not auto-migrated).

Post-Migration Checklist

1. Set MEETSTREAM_API_KEY (get one at app.meetstream.ai/api-keys)
2. Review every ⚠️ warning from the migration output
3. Update webhook handlers: keep branching on event, rename the values, and check bot_status for bot.stopped's reason
4. Store transcript_id for transcript retrieval — from create_bot, /detail, or /transcriptions
5. Add handlers for manifest.completed, audio.processed, transcription.processed/failed, video.processed
6. Verify the recording_mode → video_required boolean logic
7. Remove any pause_recording/resume_recording calls (not supported yet)
8. Run meetstream-migrate test --api-key YOUR_KEY to confirm connectivity

Feature parity & gaps

Run scan first to see exactly which of these appear in your codebase before migrating.

Requirements

Python ≥ 3.8

Development

pip install -e .
python -m pytest test/    # or: python -m meetstream_migrate.cli test --api-key YOUR_KEY

License

MIT © MeetStream.ai — meetstream.ai · docs.meetstream.ai