> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Retell AI, VAPI, and Synthflow

> Move existing voice agents and assistants from Retell AI, VAPI, or Synthflow into Famulor.

# 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.

<Note>
  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.
</Note>

## 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.

<CardGroup cols={3}>
  <Card title="Retell AI" icon="phone-arrow-up-right" href="https://www.famulor.io/retell-migration" color="#1FD5F9">
    For Retell AI agents with prompts, voices, tools, and knowledge sources.
  </Card>

  <Card title="VAPI" icon="waveform-lines" href="https://www.famulor.io/vapi-migration" color="#1FD5F9">
    For VAPI assistants with model, voice, transcriber, and tool configuration.
  </Card>

  <Card title="Synthflow" icon="workflow" href="https://www.famulor.io/synthflow-migration" color="#1FD5F9">
    For Synthflow assistants you want to test and run in Famulor.
  </Card>
</CardGroup>

## Requirements

* A Famulor account at [app.famulor.de](https://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.

<Warning>
  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.
</Warning>

## Run the migration

<Steps>
  <Step title="Open the migration page">
    Open the matching migration page:

    * [Retell AI to Famulor](https://www.famulor.io/retell-migration)
    * [VAPI to Famulor](https://www.famulor.io/vapi-migration)
    * [Synthflow to Famulor](https://www.famulor.io/synthflow-migration)
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Authorize Famulor">
    Sign in with your Famulor account. This lets the assistant create new Famulor assistants in your
    account.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## What gets copied

| Area                 | Migrated    | Notes                                                                        |
| -------------------- | ----------- | ---------------------------------------------------------------------------- |
| Name and description | Yes         | You can adjust the name before creation.                                     |
| System prompt        | Yes         | Review variables, tool instructions, and escalation logic after migration.   |
| Initial message      | Yes         | Especially important for inbound assistants and web widgets.                 |
| Language             | Yes         | Mapped to the nearest available Famulor language.                            |
| Voice                | Best effort | If the exact voice does not exist, a close Famulor alternative is suggested. |
| Model                | Best effort | Proprietary model names are mapped to available Famulor models.              |
| Knowledge base       | Best effort | Content structure can differ between providers.                              |
| Tools / functions    | Partial     | API tools should be tested and may need to be finalized as Mid-Call Actions. |
| Phone numbers        | No          | Phone numbers, SIP routes, and forwarding are moved separately.              |
| Historical calls     | No          | Previous 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](/en/ai-assistants/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.

<Tip>
  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.
</Tip>

## 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

<AccordionGroup>
  <Accordion title="The API key is rejected">
    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.
  </Accordion>

  <Accordion title="No agents are found">
    Check that you are using the correct workspace or project in the source provider. Some providers
    separate production and test environments.
  </Accordion>

  <Accordion title="A voice or model is missing">
    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.
  </Accordion>

  <Accordion title="A tool does not work after migration">
    Check the URL, method, headers, body schema, and authentication. If needed, recreate the tool as a
    Famulor [Mid-Call Action](/en/automation-platform/mid-call-tools/custom-api-integration).
  </Accordion>

  <Accordion title="Can I roll back?">
    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.
  </Accordion>
</AccordionGroup>