Skip to main content
Open Settings → Workspace → Data migration and choose Famulor 1.0, Retell AI, Vapi, Synthflow, or ElevenAgents. Famulor 1.0 copies supported assistants, tools, knowledge, campaigns, automations, and BYO telephony into this workspace. See Migrate from Famulor 1.0. The migration first shows a preview. You choose the assistants to copy before Famulor creates anything. Imported assistants are inactive, so you can review and test them before they handle conversations.

​
What is copied

  • Assistant name
  • System prompt and portable text greeting
  • Primary language
  • Compatible conversation settings such as temperature, voice speed, call duration, timezone, and recording preference when the source provides them
Famulor uses workspace-approved model and voice defaults during this first stage. Choose and preview the final voice in each imported assistant.

​
What needs review

Tools, actions, knowledge content, conversation flows, squads and handoffs, phone numbers, routing, widgets, and credentials are not silently recreated. The preview lists the relevant follow-up work for every assistant.
Never paste a provider key into Milian or another chat. Enter it only in the password field inside the authenticated migration dialog. The key is used for the current preview or import request and is not saved.
Your source account stays unchanged. Route calls to Famulor only after you have reconnected dependencies, selected a voice, and completed a test conversation. For programmatic migrations, see Preview or import provider assistants.

​
ElevenAgents

Choose ElevenAgents and use an ElevenLabs Global workspace key with read access to your agents. Regional data-residency workspaces are not supported by this import. The import reads each agent’s main configuration; other branches, drafts, traffic splits and version history stay in ElevenAgents. An empty source greeting keeps User speaks first. A disabled recording preference stays disabled. Compatible temperature, speed, duration and timezone settings are copied. Tools, knowledge sources, workflows, subagents, procedures, language presets and runtime variables require review. Reconfigure privacy, retention and evaluation policies before activation.

​
API, MCP and CLI

Use POST /api/v1/migrations/providers with provider: "elevenlabs", first with action: "preview", then action: "import" and the selected agent IDs. MCP provides preview_provider_assistant_migration and import_provider_assistants.
Keep the source key in a local JSON request file using the source_api_key field. The import file also includes selected_assistant_ids from the preview. Protect and delete these local files after use; do not put keys in shell history or shared logs.