Migration
Moving from Retell to Audact.
Founding price · €1,497 once, then €499 a month · scoped before it is scheduled
The mechanical part is smaller than you would expect. Webhook events use the Retell lifecycle names (call started, call ended, call analysed); the mapping is confirmed per event during the migration (In development). Prompts and conversation design convert, and a migration engineer runs the conversion rather than handing you a format guide. Numbers are the one thing we look at first, because porting depends on where each one is registered and who holds the account.
What the migration actually involves
- Webhook events use the Retell lifecycle names (call started, call ended, call analysed); the mapping is confirmed per event during the migration (In development).
- In development
- Prompt and conversation design convert; a migration engineer runs the conversion rather than handing you a format guide.
- Part of the migration
- Call logs, recordings and analytics export from your current platform before anything is switched off, so the cutover is reversible until you say it is not.
- Part of the migration
- A parallel run: a share of traffic on the new setup while the old one keeps taking the rest, until the numbers say switch.
- Part of the migration
- Number porting depends on where each number is registered and who holds the account. We check that first, before anyone commits to a date.
- Checked in scoping
Migration
What is different on the other side.
- The AI disclosure moves out of your prompt and into the policy: it is spoken at the position the country policy requires, in the caller's language, and its position is recorded. Country layer status — Germany active · Netherlands in progress · Belgium, Austria queued (In controlled testing).
- For governed interactions a receipt is visible in the product. Three of its fields recompute without a key, for anyone holding it; the fourth, inclusion in the Merkle root, is checked against the published root with the inclusion proof from the call's Article 50 report. The export you would hand an auditor was retested on 26 August 2026 after the deploy, measured on browser calls rather than over a telephone line: five calls, thirty validated turns, thirty receipts.
- Telephony, speech-to-text, text-to-speech and the model are inside one rate; there is nothing left to procure or reconcile separately.
- White-label the caller hears (In controlled testing), isolated sub-accounts (in controlled testing), Stripe Connect re-billing: planned, not in the current production offer. All inside the monthly rate.
- Primary application hosting is Frankfurt. The full subprocessor list, with location and safeguards per entry, is in the Trust Center.
Timing
Migration is scoped individually; timing depends on telephony and number portability.
Migration is scoped individually; timing depends on telephony and number portability. A migration engineer looks at your current setup before anyone names a date, because a date given before that is a guess with a calendar entry attached.
What it costs after
One rate, one invoice.
€1,497 implementation, then €499 a month with 5,000 minutes included and €0.11 a minute above that. Annual prepayment is 15% off. There is no annual minimum. Founding price for the first three external agencies. €2,995 and €749 from the fourth customer.
Questions
- Do I have to rewrite my webhook consumer?
- Webhook events use the Retell lifecycle names (call started, call ended, call analysed); the mapping is confirmed per event during the migration (In development). This is the part of the migration that usually eats the budget elsewhere, and here it does not.
- Can I keep my numbers?
- That depends on where each number is registered and whose account it sits in, which is why it is the first thing we check rather than the last. We will tell you what is portable and what is not before you commit to a date, and where porting is not possible we set up new numbers in parallel so nothing goes dark.
- Can I run both for a while?
- Yes, and we recommend it. A share of traffic on the new setup while the old one keeps taking the rest means the cutover is a decision you make from data rather than a leap you take on a date.
Apply for a founding seat
Twenty minutes against your current setup: what converts, what needs a decision, and what the first governed call needs. No date until we have looked.