Skip to main content

​
Migrate from Retell AI, VAPI, and Synthflow

The Famulor migration assistant helps you move existing voice agents from Retell AI, VAPI, and Synthflow into Famulor. It reads your existing configuration, maps the most important fields to Famulor settings, and creates new Famulor assistants from them.
Migration creates a copy. Your Retell, VAPI, or Synthflow account is not changed. You can test both systems in parallel and only move phone numbers or SIP routing to Famulor after testing.

​
When to use this guide

Use this guide if you already have production assistants on another voice-AI platform and do not want to rebuild them from scratch.

Retell AI

For Retell AI agents with prompts, voices, tools, and knowledge sources.

VAPI

For VAPI assistants with model, voice, transcriber, and tool configuration.

Synthflow

For Synthflow assistants you want to test and run in Famulor.

​
Requirements

  • A Famulor account at app.famulor.de.
  • Access to the source-provider account you want to migrate from.
  • A source-provider API key with read access for assistants, agents, tools, and knowledge bases.
  • At least one assistant or agent in the source system.
Only paste API keys needed for the migration. The key is forwarded server-to-server to the selected provider to read your agents. It is not stored in Famulor and is not kept for future syncs.

​
Run the migration

1

Open the migration page

Open the matching migration page:
2

Paste the source-provider API key

Copy the API key from Retell AI, VAPI, or Synthflow and paste it into the first step of the migration assistant. Famulor uses the key only to read existing agents and their configuration.
3

Choose agents or assistants

Select the agents you want to copy into Famulor. You can migrate individual agents or select all agents returned by the source provider.
4

Review field mapping

Check the suggested mapping for model, language, voice, initial message, system prompt, knowledge base, and tools. Adjust the mapping if Famulor cannot find an exact match for a voice or model.
5

Authorize Famulor

Sign in with your Famulor account. This lets the assistant create new Famulor assistants in your account.
6

Start migration

Run the migration and wait until all selected agents have been created. When it finishes, the new assistants are available in your Famulor dashboard.

​
What gets copied

AreaMigratedNotes
Name and descriptionYesYou can adjust the name before creation.
System promptYesReview variables, tool instructions, and escalation logic after migration.
Initial messageYesEspecially important for inbound assistants and web widgets.
LanguageYesMapped to the nearest available Famulor language.
VoiceBest effortIf the exact voice does not exist, a close Famulor alternative is suggested.
ModelBest effortProprietary model names are mapped to available Famulor models.
Knowledge baseBest effortContent structure can differ between providers.
Tools / functionsPartialAPI tools should be tested and may need to be finalized as Mid-Call Actions.
Phone numbersNoPhone numbers, SIP routes, and forwarding are moved separately.
Historical callsNoPrevious call logs remain in the source system.

​
Test after migration

  1. Open the migrated assistant in Famulor.
  2. Review the system prompt, voice, language, and model.
  3. Test the assistant with Test Chat and a real test call.
  4. Review knowledge bases and sources if the agent uses RAG.
  5. Test every Mid-Call Action individually, especially CRM, calendar, and webhook calls.
  6. Connect a phone number or SIP trunk only after those checks pass.
Start by migrating one agent, test it end to end, then move the rest. This catches mapping issues early before you import many assistants at once.

​
Go-live checklist

  • The assistant handles the most important test cases correctly.
  • All tools or Mid-Call Actions return real responses, not test data.
  • Calendar, CRM, and webhook destinations point to production systems.
  • Phone number, SIP trunk, or forwarding points to Famulor.
  • Campaign or inbound routing rules have been recreated in Famulor.
  • Your team knows that new call logs will be created in Famulor after go-live.

​
Troubleshooting

Create a new API key in the source provider and check that it can read agents, assistants, tools, and knowledge bases. Copy it without leading or trailing spaces.
Check that you are using the correct workspace or project in the source provider. Some providers separate production and test environments.
Not every provider exposes identical voices or model names. Choose the closest Famulor voice or an available model in the field mapping step, then test conversation quality.
Check the URL, method, headers, body schema, and authentication. If needed, recreate the tool as a Famulor Mid-Call Action.
Yes. Migration does not delete or change anything in the source system. As long as phone numbers or SIP routes have not been moved, the old agent keeps running.