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

# Data Migration

> Migrate assistants, phone numbers, knowledgebases, tools, widgets, and automation flows between users

Transfer data between users on your platform. This tool allows you to copy or move assistants, phone numbers, knowledgebases, custom tools, widgets, and automation flows from one user to another.

## Accessing Data Migration

1. Open your Administration Panel
2. Navigate to **Data Migration** in the sidebar

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-sidebar.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=5698125e4b7f6f43dcedea26670059ca" alt="Data Migration in sidebar" width="1925" height="590" data-path="resources/white-label-data-migration-sidebar.png" />
</Frame>

## Step 1: Select Users

Choose the **Source User** (migrate FROM) and the **Destination User** (migrate TO). All users in your platform are listed by name and email.

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-users.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=f5479fe8864ec5e5b8468eae7bbfc965" alt="Source and Destination user selection" width="1603" height="207" data-path="resources/white-label-data-migration-users.png" />
</Frame>

## Step 2: Select Data to Migrate

After selecting a source user, you can pick which items to migrate. All fields are searchable multi-select dropdowns.

### Assistants

Select the assistants you want to migrate. Each assistant is shown with its avatar and name.

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-assistants.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=72c569cd741552022592f8c57030d291" alt="Assistant selection" width="1608" height="718" data-path="resources/white-label-data-migration-assistants.png" />
</Frame>

When assistants are selected, an **Assistant Migration Options** section appears with these settings:

* **Include attached Knowledgebase** (default: on) — also copy the knowledgebase linked to each selected assistant
* **Include attached Custom Tools** (default: on) — also copy the tools assigned to each selected assistant
* **Transfer Post-Call Webhook Flows** (default: on) — transfer automate flows connected as post-call webhooks
* **Transfer Inbound Webhook Flows** (default: on) — transfer automate flows connected as inbound webhooks
* **Voice Handling:**
  * *Reference existing voice* (recommended) — destination user uses the original voice reference
  * *Copy cloned voice to destination user* — creates a separate copy of the voice

### Phone Numbers, Knowledgebases, Tools, Widgets & Automate Flows

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-other.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=a90fd7edfae68310a35abe3d5e0de61f" alt="Phone numbers, knowledgebases, tools, widgets and automate flows selection" width="1583" height="708" data-path="resources/white-label-data-migration-other.png" />
</Frame>

**Phone Numbers** — behavior depends on the type:

* **Normal** (subscribed numbers) — **Grant access**: the source user keeps ownership but only the destination user can use it
* **SIP / Caller ID** — **Full transfer**: ownership moves completely to the destination user

**Knowledgebases, Custom Tools, Widgets** — select standalone items not already attached to the assistants selected above. Items attached to selected assistants are migrated automatically if the corresponding option is enabled.

**Automate Flows** — select automation flows to migrate. Each flow shows its status (enabled/disabled).

<Warning>
  OAuth connections (Google, Slack, etc.) will NOT be transferred. The destination user must reconnect all OAuth apps in their Automate workspace after migration.
</Warning>

## Step 3: Preview & Execute

Once you have selected items, a **Migration Summary** section appears showing the total count of items to be migrated.

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-summary.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=d6c1728c0f08cce34c8004c3a3b77fb8" alt="Migration summary" width="1585" height="382" data-path="resources/white-label-data-migration-summary.png" />
</Frame>

* **Preview Migration** — performs a dry run to show what would happen, including any warnings
* **Execute Migration** — runs the actual migration after a confirmation prompt

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-preview.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=94af10ab15a913431b7e4154d3a79eda" alt="Migration preview result" width="1587" height="392" data-path="resources/white-label-data-migration-preview.png" />
</Frame>

## Migration History

Below the migration form, a **Migration History** table shows all past migrations with:

| Column     | Description                                                                                          |
| ---------- | ---------------------------------------------------------------------------------------------------- |
| **Type**   | Entity type — Assistant, Knowledgebase, Tool, Phone (Grant), Phone (Transfer), Widget, Automate Flow |
| **From**   | Source user name                                                                                     |
| **To**     | Destination user name                                                                                |
| **Status** | Pending, In Progress, Completed, Failed, or Rolled Back                                              |
| **Date**   | When the migration was executed                                                                      |

<Frame>
  <img src="https://mintcdn.com/autocalls/PrqJQQ7RUSkO1ZNE/resources/white-label-data-migration-history.png?fit=max&auto=format&n=PrqJQQ7RUSkO1ZNE&q=85&s=2dd13bbcf44a6a20a7f823b04738bd5f" alt="Migration history table" width="1597" height="865" data-path="resources/white-label-data-migration-history.png" />
</Frame>

### Rollback

Completed migrations can be rolled back using the **Rollback** button on each row. This deletes the migrated entity from the destination user.

<Warning>
  Rollback cannot be undone. If a migrated assistant is currently attached to campaigns, it cannot be rolled back until removed from those campaigns.
</Warning>