Migrating from Vapi: a reversible voice-assistant cutover plan

Moving a voice assistant from Vapi is an application migration. Instructions are only one part of it. The number route, tool contracts, credentials, call records and billing rules also affect what a caller experiences.

This guide is a migration procedure, not a claim that developers are leaving Vapi or that Burki is universally better. Start only when you can describe the problem the move is intended to solve.

1. Capture the current contract

Document the assistant's approved business facts, greeting, interruption behavior, required information and escalation rules. Record the selected voice components and the tools the assistant may invoke. Use the Vapi documentation to inspect the current configuration rather than assuming exported fields map directly to another platform.

For each action, write down the input fields, authentication method, timeout, idempotency behavior and successful response. Preserve recordings and transcripts according to their retention permissions; do not transfer more personal information than the new workflow needs.

2. Map every dependency

A similarly named event does not guarantee identical timing. For example, “call ended” may arrive before final recording or usage data. Your downstream system should not assume every result is immediately complete.

3. Validate without duplicate side effects

Start with simulated actions or a dedicated test environment. Use fixed caller scenarios: correct a date, change an address, interrupt an answer, request a human, and trigger an unavailable dependency.

Then run a small number of authorized real calls through the replacement carrier route. Verify both audio directions, hangup, handoff recovery and financial settlement. A browser pass is useful but does not replace this telephone acceptance.

Do not connect the same business webhook to both systems in a way that repeats bookings or messages. Assign one owner for each live request, and preserve request identifiers so retries can be recognized.

4. Cut over with a rollback route

Choose a limited traffic window, confirm the old route still works, and name a person responsible for monitoring early calls. Roll back for lost callers, repeated actions or missing results. After a stable period, remove genuinely unused numbers and subscriptions only after checking dependencies.

In Burki, create an unpublished assistant and validate its supported voice mode and actions before publishing. Keep the migration checklist alongside the cost comparison so operational improvements and financial savings are measured independently.