Import Retell, Vapi or Synthflow assistants into Famulor

Yes. Under Settings → Workspace → Data migration you first get a preview, then inactive copies. The source account stays. Review the shell on screen first — name, prompt, greeting, language. A test conversation comes only after you activate.

Can I import Retell, Vapi or Synthflow assistants into Famulor?

Yes. As Owner or Admin you open Settings → Workspace → Data migration. There is no plan gate. You preview Retell, Vapi or Synthflow assistants, choose which ones to copy, and Famulor creates inactive copies. The source account stays unchanged. Dependencies are flagged for review.

The UI manual for this panel is Migrate from Retell AI, Vapi, or Synthflow. The public pages for Retell, Vapi and Synthflow open the same signed-in app; the CTAs append &migration=retell, &migration=vapi or &migration=synthflow to the workspace URL. An AI phone assistant created here is an inactive copy you can compare, not an instant stand-in for the production line.

Where do I find Data migration?

Open Settings → Workspace → Data migration. In the app the block lives at app.famulor.io/settings?panel=workspace. Only Owner and Admin see it. There is no plan gate. The block title is Datenmigration, the subtitle “Assistants von einer anderen Plattform importieren”.

The visible text: preview Retell AI, Vapi or Synthflow assistants and import inactive copies into this workspace. Source accounts stay unchanged; dependencies are flagged for review.

The dialog is the same for all three providers: key, then preview, then inactive copies. The review list differs — Vapi flags transcription, squads and workflows; Synthflow flags actions and widgets. There is no 1:1 import of the flow graph.

Enter the provider key only in the password field of the signed-in dialog. It applies to the current request only, goes server-side to the vendor, is not stored, not logged, not returned, and is not sent to Milian. After import the dialog is cleared. Never paste the key into Milian or any other chat.

What is imported — and what stays for review?

You get a shell, not a finished production twin. What copies is the name, the system prompt, the greeting only if it is transferable text, the primary language, and compatible settings. Voice and model come as workspace defaults, not from the source. Source tools are not copied.

The greeting copies only when it is transferable text — not a user-start greeting, not an audio URL, and not a non-static Synthflow greeting.

Compatible settings: temperature on Retell and Vapi, voice speed and max call duration. On Synthflow also recording and timezone.

What is copied:

• Assistant name
• System prompt
• Greeting only as transferable text
• Primary language
• Compatible settings (temperature on Retell and Vapi, voice speed, max call duration; on Synthflow also recording and timezone)

Flagged only, not imported:

• Tools and actions
• Knowledge
• Flow graph (Retell flows as prompt text only, no 1:1 in the builder)
• Squads
• Widgets
• Voices
• Models
• Numbers
• Routing
• Webhooks
• Variables
• Credentials

Flows you review or rebuild later in the Flow Builder — the importer does not create them. The binding list is in the provider-migration docs.

Does my Retell, Vapi or Synthflow account stay intact?

Yes. Import does not change the source account. Retell, Vapi or Synthflow stay live and can keep taking calls while you review the inactive copy in Famulor. Cutover — number, SIP, routing — is a separate step and is not part of the import.

Parallel run is the normal path. If you are still placing vendors, use Alternatives, Retell, Vapi and Synthflow. Those pages replace neither the preview nor the later test after you activate.

How do I test the difference after import?

First review the shell on screen: name, prompt, greeting, language. Then pick a voice. Then activate the assistant. A test conversation comes only after you activate.

Inactive means the assistant exists, stays switched off, and has no number. Until you activate, Outbound, Inbound, Web-Call, Simulation, WhatsApp Voice and Mail-Reply stay blocked. The UI after import: pick a voice, then activate, then test.

While the copy is inactive there is no test call and no simulation. The source account stays live. Do not switch the old assistant off for this.

When is the assistant actually live?

Not at import time. The copy exists, but it is inactive and has no number. It is ready for a comparison only after you have picked a voice and activated the assistant. A test conversation comes only after you activate. Production traffic starts only when you move number, SIP and routing yourself — that is cutover, not import.

Import is not cutover. You attach a number separately; the path is Voice AI migration without downtime: cutover plan for SIP, numbers and integrations.

How is this different from the large migration playbook?

This tutorial is the product how-to: where the block lives, that preview comes first, that you get inactive copies, and that you review the shell on screen before you activate. The docs are the UI manual. The enterprise playbook is the operating project after that.

If you treat the switch as operations, read Migrate Retell AI, Vapi and Synthflow: the enterprise playbook. If you are moving numbers and routing, stay with the cutover plan. This page is only the importer in Settings → Workspace → Data migration.

FAQ

Can I import Retell, Vapi or Synthflow assistants into Famulor?

Yes. In the preview you select assistants before Famulor creates anything. Inactive copies land in the workspace. The source account stays. Owner or Admin only, with no plan gate. The steps are in the provider-migration docs.

Where do I find Data migration?

Under Settings → Workspace → Data migration, in the app at app.famulor.io/settings?panel=workspace. The block is titled Datenmigration, subtitle “Assistants von einer anderen Plattform importieren”. There you choose Retell AI, Vapi or Synthflow. Same dialog: key, preview, inactive copies.

What is imported — and what stays for review?

Name, system prompt, greeting only as transferable text, primary language and compatible settings. Voice and model are workspace defaults, not the source. Tools, knowledge, flow graph, squads, widgets, voices, models, numbers, routing, webhooks, variables and credentials are flagged only, not imported. Retell flows come as prompt text only, not 1:1 into the builder.

Does my Retell, Vapi or Synthflow account stay intact?

Yes. Import does not change the source account. The key applies to the current request only, goes server-side to the vendor, is not stored, not logged, not returned, and is not sent to Milian. After import the dialog is cleared. Calls stay on the source until you move them yourself.

How do I test the difference after import?

Review the shell on screen first: name, prompt, greeting, language. Pick a voice. Activate the assistant. A test conversation comes only after you activate. While inactive, Outbound, Inbound, Web-Call, Simulation, WhatsApp Voice and Mail-Reply stay blocked.

When is the assistant actually live?

Only after you have picked a voice and activated the assistant. A test conversation comes only after you activate. Import alone is not cutover. Number, SIP and routing stay a separate step; that is the cutover article.

How is this different from the large migration playbook?

This article explains the in-app importer. The playbook is the enterprise operating project. The cutover plan is the number and SIP move. The docs are the UI manual for preview and import. The three texts do not replace each other.

Open workspace settings, import one inactive copy, review the shell on screen, pick a voice, activate, then decide. If you want to see the flow once, book a demo. DPA and Trust Center stay their own pages: DPA, Trust Center.