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

> Preview and import supported assistants, tools, knowledge, campaigns, automations, and BYO telephony

Open **Settings → Workspace → Data migration** to move supported resources from a Famulor 1.0 account into the current workspace. Only copies are created — nothing is deleted from the old account, and it keeps working while you set things up here.

Moving from Retell AI, Vapi, or Synthflow instead? The same panel handles those — see [Migrate from Retell AI, Vapi, or Synthflow](/settings/provider-migrations).

## Recommended workflow

<Steps>
  <Step title="Connect the source account">
    Choose **Connect with my Famulor 1.0 account**, or paste a Famulor 1.0 API key into the field below it. Either way the credential is used only for this run and is never saved. Do not paste credentials into the Milian conversation.
  </Step>

  <Step title="Preview">
    Load a preview to see the available resources, compatibility notes, and items that need manual follow-up.
  </Step>

  <Step title="Select resources">
    Choose the assistants, reusable tools, knowledge-base structure, campaigns, automations, and supported BYO telephony connections you want to import.
  </Step>

  <Step title="Import and review">
    Start the import, then open each imported resource and complete the review checklist before using it with customers.
  </Step>
</Steps>

## What to expect

* **Assistants** keep supported prompts, greetings, voice settings, variables, flows, and compatible tool links.
* **Reusable tools** are imported without exposing saved credentials. Re-enter any secret required by the destination connection.
* **Knowledge bases** arrive as empty containers with their names and assistant links. Document **content cannot be transferred** — Famulor 1.0 never hands out the files themselves, so every document is listed as skipped in the import report and has to be uploaded again by hand. Website and cloud-drive sources need reconnecting too.
* **Campaigns** are created as drafts. Review the audience, sender, schedule, retries, and calling window before starting them.
* **Automations** are created as disabled drafts. Review every trigger, action, and app connection before enabling them.
* **BYO telephony** can be recreated when the source provides enough customer-owned connection information. Follow the setup shown in the destination workspace before routing live traffic.

The preview highlights unsupported or incomplete items rather than silently enabling them.

## Items that often need manual work

* marketplace or rented phone numbers tied to the old account;
* knowledge documents that must be uploaded or connected again;
* campaign audiences and channel-specific senders;
* external calendar, email, CRM, and automation app authorizations;
* older flow steps or tool types that do not have a direct equivalent;
* how assistants are organized — Famulor 1.0's folders and labels have no counterpart here, so the import skips them. Assistants live in one list and are grouped with **tags** instead.

Imported campaigns and automations stay inactive until you explicitly approve them. This prevents an import from contacting customers or running external actions unexpectedly.

<Warning>
  Enter the Famulor 1.0 API key only in the migration dialog itself. Never paste an API key or other secret into a Milian conversation.
</Warning>

## REST API and MCP

Use `POST /api/v1/migrations/famulor` with `action: "preview"` before sending `action: "import"` with the selected source IDs. The credential needs read permission for the preview and the matching write scopes for the resources you import.

The same workflow is available through the MCP tools `preview_famulor_1_migration` and `import_famulor_1_data`.