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

# Migrate Claude Desktop from a cloud provider to Claude Enterprise

> Migrate Claude Desktop from a cloud provider such as Amazon Bedrock to Claude Enterprise and keep each user's local chats, sessions, projects, tasks, and skills

Move Claude Desktop from your cloud provider, where the app is named Claude (third-party), to Claude Enterprise. After one configuration change, each user's work migrates when they sign in to Claude Enterprise on the same computer. You choose one option: move everyone to Claude Enterprise, or let each user switch between your cloud provider and Claude Enterprise at sign-in.

![Flow diagram: IT updates Claude Desktop, turns on two skills settings, and changes the configuration. Cloud provider controls don't apply in Claude Enterprise. Each user signs in to Claude Enterprise. Claude Desktop migrates earlier work (chats, sessions, projects, scheduled tasks), then adds skills, plugins, extensions, and local MCP servers. The user approves tools in scheduled tasks, adds their instructions and Cowork memory, and checks their skills.](https://mintcdn.com/claude-ai/eCdSFVE2PxOkix1N/images/third-party/diagrams/move-to-claude-enterprise-flow.svg?fit=max\&auto=format\&n=eCdSFVE2PxOkix1N\&q=85\&s=f30d504bf82282211d88e1dc8492801b)

## What is migrated

The migration never changes or deletes the Claude (third-party) data. Nothing migrates until you turn the migration on, as described under [Migrate your fleet](#migrate-your-fleet).

**Migrated automatically:**

* Chats, which appear in Cowork
* Cowork sessions and projects, with their folders, except a few system or network folders and [folders that `allowedWorkspaceFolders` leaves out](#check-the-allowedworkspacefolders-list)
* Code sessions in folders Claude Code trusts
* Scheduled tasks, on or off as before, except Code tasks in untrusted folders
* Local MCP servers and most desktop extensions, as before
* App preferences

**Migrated after one step:**

* Skills, and plugins users uploaded, after the [skills settings](#before-you-begin)
* Plugin marketplaces users added over HTTPS from github.com, gitlab.com, bitbucket.org, or a GitHub Enterprise host your organization connected to Claude, after the [skills settings](#before-you-begin). Claude must be able to access the repository. Users then install the plugins they want in **Customize > Plugins**.
* Personal instructions the account doesn't have yet, after **Add instructions** in **Settings > Import**
* Cowork [memory](https://claude.com/docs/third-party/claude-desktop/data-storage.md#memory), after the [memory settings](#before-you-begin) and **Add to memory** in **Settings > Import**. Claude saves what's useful to the user's memory, in its own words.
* Code sessions in untrusted folders, after the user trusts the folder and adds them in **Settings > Import**

**Not migrated:**

* Remote connectors, other plugin marketplaces, and plugins users didn't upload. Set them up again.
* Skills with plugin components or an unreadable header, or over about 10 MB or 200 files
* Scheduled Code tasks in folders Claude Code doesn't trust
* A few system or network folders. The user can attach most of them again.
* Session and project folders that [`allowedWorkspaceFolders` leaves out](#check-the-allowedworkspacefolders-list)
* Artifacts. The **Artifacts** page in Claude Enterprise doesn't list them. Their files stay on the computer, by default in [`~/Claude/`](https://claude.com/docs/third-party/claude-desktop/data-storage#data-shared-with-standard-claude-desktop).
* [Project memory](https://claude.com/docs/third-party/claude-desktop/data-storage.md#project-memory). A migrated project starts without the memory that Claude kept for it in Claude (third-party), and **Notes from Cowork** in **Settings > Import** doesn't include it.

Migrated sessions stay on the computer and don't sync to claude.ai. Continuing one sends its content to Anthropic. Uploaded skills, added instructions, added Cowork memory, plugin marketplaces, and MCP tool on/off settings go to the user's account. Claude also sends standard usage data.

## Before you begin

1. **Update first.** Update every computer to Claude Desktop 4.16336.0 or later before the configuration change. Each user's work migrates on the version installed when they first open Claude Enterprise after the change. A computer that migrated on an earlier release writes the [status file](#check-whether-a-computer-has-finished-migrating) after it updates, if `importThirdPartyHistoryIntoOrgUUID` is still deployed. A computer that migrated before 3.1623.0 also adds plugin marketplaces after it updates, but doesn't add folders to the sessions and projects that it already migrated. If a user moved to a new computer with a [Claude Desktop export](https://claude.com/docs/third-party/claude-desktop/import.md#move-your-data-to-another-device), update the new computer to 5.11492.0 or later before the configuration change. Earlier releases don't migrate the export's scheduled tasks, its projects that have no sessions, or the project instructions that the user accepted.
2. **Turn on the skills settings.** In [**Organization settings > Plugins & skills > Policy**](https://claude.ai/admin-settings/skills?tab=policy), turn on **User-created skills** and **Skill and plugin security scanning**. For custom roles, also give them the skills permissions in [**Organization settings > Roles**](https://claude.ai/admin-settings/roles). Skills need both settings. Plugins and plugin marketplaces need only **User-created skills**.
3. **Turn on memory.** For Cowork to use each user's memory, turn on **Memory** and [**Chat and Cowork unified**](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization) in [**Organization settings > Capabilities**](https://claude.ai/admin-settings/capabilities). Users turn on memory for themselves in the [steps for each user](#steps-for-each-user).
4. **Replace the controls** listed in [What changes for your security controls](#what-changes-for-your-security-controls).
5. **Check the folder list.** If you set `allowedWorkspaceFolders`, follow [Check the `allowedWorkspaceFolders` list](#check-the-allowedworkspacefolders-list).

Special cases:

* If the policy or profile that carries your Claude settings sets [`requireCoworkFullVmSandbox`](https://claude.com/docs/third-party/claude-desktop/configuration#requirecoworkfullvmsandbox) to `true`, Claude Enterprise applies the key, although Claude (third-party) ignores it. Cowork then runs only in its VM sandbox, and the migration waits until you remove the key. Remove the key as part of the configuration change, and keep it removed afterward. If you set it again, users can't continue their migrated Cowork sessions. If your organization needs Cowork to run only in its VM sandbox in Claude Enterprise, ask your Anthropic account team before you migrate.
* If your organization needs HIPAA, make it HIPAA-ready before users first sign in. A HIPAA-ready organization migrates no skills, local MCP servers, extensions, plugins, plugin marketplaces, instructions, or Cowork memory.
* With the MSIX install on Windows versions before Windows 11 (build 22000), for example on Windows 10, update Claude in place. Uninstalling or resetting it can delete the [Claude (third-party) data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#where-data-lives).
* On Linux, where Claude Desktop is in [beta](https://code.claude.com/docs/en/desktop-linux), the same steps apply, with the keys as JSON in the root-owned file [`/etc/claude-desktop/managed-settings.json`](https://claude.com/docs/third-party/claude-desktop/configuration-format#the-linux-configuration-file). If that file doesn't meet the ownership and permission rules described there, Claude ignores every key in it. Use an unlocked desktop keyring on each computer, such as GNOME Keyring or KDE Wallet, so that Claude can protect what it saves.

### Check the `allowedWorkspaceFolders` list

Unlike most cloud provider keys, [`allowedWorkspaceFolders`](https://claude.com/docs/third-party/claude-desktop/configuration#allowedworkspacefolders) also applies in Claude Enterprise, and it limits which folders the migration brings. This holds for a list in the policy or profile itself. A list that only your bootstrap server sends doesn't reach Claude Enterprise until you copy it into the policy or profile.

Cowork sessions in Claude Enterprise open without folders that are outside the list. The migration handles those folders this way:

* **Sessions** arrive without them
* **Projects** arrive with a new, empty folder instead, in the `Projects` folder of the [Cowork files folder](https://claude.com/docs/third-party/claude-desktop/data-storage.md#data-shared-with-standard-claude-desktop)
* **Projects that are already directly inside that `Projects` folder** keep their folder, and projects that had no folder get one there
* **Scheduled tasks and Code sessions** keep their folders, but can't work in a folder that is outside the list

The files stay where they were. Changing or removing the list later doesn't bring back the folders that the migration left out, so users have to attach them again.

Before the configuration change, make the list cover the folders that hold users' work, but don't list a home folder:

* **Cowork files folder**: by default `~/Claude`, or `~/Documents/Claude` on older installs. **Settings > Cowork** shows it under **Cowork files**. If the list doesn't cover it, sessions open without the project folders inside it.
* **Environment variables**: if the only entry uses a variable, such as `%OneDriveCommercial%`, that isn't set when Claude starts, Claude allows no folder, and the migration treats every folder as outside the list.

If users' work is in folders that you won't list, or you can't tell, keep the key out of the policy or profile for now. Until you add the key, it limits no folders in Claude Enterprise and doesn't turn on the command sandbox in Code sessions. Add it to a computer after its users have [finished migrating](#check-whether-a-computer-has-finished-migrating). From then on, sessions open without folders that are outside the list, so first have users move that work into a listed folder and attach it.

A list that you set under [**Allow workspace folders**](https://support.claude.com/en/articles/12622667-enterprise-configuration-for-claude-desktop) in [**Organization settings > Capabilities**](https://claude.ai/admin-settings/capabilities) can limit the migration in the same way. If you keep the key out, don't choose **Allow only the folders on the list** or turn the setting off until all users have [finished migrating](#check-whether-a-computer-has-finished-migrating).

## What changes for your security controls

While a user works in Claude Enterprise, most of your cloud provider settings in the [configuration reference](https://claude.com/docs/third-party/claude-desktop/configuration.md) don't apply to them, including permission, plugin, and browser limits. Claude shows no warning, even if the keys stay deployed. Set up replacements first:

* Cowork's telemetry and network egress: your organization settings.
* Code sessions' telemetry, SSH host limits (any host is allowed until you set a list), and session retention (`cleanupPeriodDays`): Claude Code's managed settings.
* Remote [managed MCP servers](https://claude.com/docs/third-party/claude-desktop/configuration.md#managedmcpservers): add them as connectors. The Microsoft 365 connector keeps working.

Telemetry opt-outs, the egress list for Code sessions, Cowork's session retention, and locally run managed MCP servers have no replacement. Migrated plugins aren't scanned. Migrated skills and plugins arrive on or off as before, with their hooks and tool permissions.

The command sandbox in Code sessions stays on only where the policy or profile itself sets [`allowedWorkspaceFolders`](https://claude.com/docs/third-party/claude-desktop/configuration#allowedworkspacefolders). The same list decides which folders Cowork sessions keep, as described under [Check the `allowedWorkspaceFolders` list](#check-the-allowedworkspacefolders-list).

## Migrate your fleet

Make one change to the policy or profile that carries your Claude settings: an `HKEY_LOCAL_MACHINE` policy on Windows (not `HKEY_CURRENT_USER`), a [configuration profile](https://claude.com/docs/third-party/claude-desktop/mdm.md) on macOS, or the root-owned [`/etc/claude-desktop/managed-settings.json`](https://claude.com/docs/third-party/claude-desktop/configuration-format#the-linux-configuration-file) on Linux.

**1. Remove or keep the cloud provider keys**

Choose one option for the keys that connect Claude to your cloud provider, such as keys that start with `inference` or `bootstrap`:

* **To move everyone to Claude Enterprise**, remove those keys. Also remove [`disableDeploymentModeChooser`](https://claude.com/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser), [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/mdm#restrict-a-device-to-one-deployment-mode), and [`deploymentOrganizationUuid`](https://claude.com/docs/third-party/claude-desktop/configuration#deploymentorganizationuuid). If your settings come from a [bootstrap server](https://claude.com/docs/third-party/claude-desktop/bootstrap.md), copy the keys you want to keep into the policy or profile itself.
* **To let each user switch between your cloud provider and Claude Enterprise**, keep those keys and `deploymentOrganizationUuid`. They must be in the same `HKEY_LOCAL_MACHINE` policy or configuration profile as `importThirdPartyHistoryIntoOrgUUID`, because on Windows Claude [reads one policy location](https://claude.com/docs/third-party/claude-desktop/mdm.md#4-deploy-the-configuration). Make sure [`disableDeploymentModeChooser`](https://claude.com/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser) isn't set in the policy or profile, or by your bootstrap server, and that [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/mdm#restrict-a-device-to-one-deployment-mode) is unset or `any`. Claude's welcome screen then offers **Or sign in with Claude.ai**. Your cloud provider settings still apply while a user works with your cloud provider. With your cloud provider and with Claude Enterprise, Claude uses some of the same folders on the computer, as described under [Data shared with standard Claude Desktop](https://claude.com/docs/third-party/claude-desktop/data-storage.md#data-shared-with-standard-claude-desktop).

Remove `requireCoworkFullVmSandbox`, unless your organization needs Cowork to run only in its VM sandbox, as described under the special cases in [Before you begin](#before-you-begin). Before you keep `allowedWorkspaceFolders` or copy it from a bootstrap server, [check the list](#check-the-allowedworkspacefolders-list). Leave other keys in place. In Claude Enterprise, the desktop extensions feature is on unless [`isDesktopExtensionEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#isdesktopextensionenabled) is set to `false`.

**2. Set your organization ID**

For either option, copy the **Organization ID** from [**Organization settings > Organization and access**](https://claude.ai/admin-settings/organization). Set `importThirdPartyHistoryIntoOrgUUID` to this ID without braces, and in the registry or a profile without quotation marks. To keep Claude on these computers from using another organization or a personal account, where nothing migrates, you can also set `forceLoginOrgUUID` to the same ID. The app then blocks Claude accounts that aren't in that organization.

If you keep the cloud provider keys and users click **Sign in with Claude Console**, also add the ID of each Claude Console organization that you allow, as described under [Keep a device on its managed profile](https://claude.com/docs/third-party/claude-desktop/admin-console.md#keep-a-device-on-its-managed-profile).

On Windows, in an elevated PowerShell window:

```powershell theme={null}
reg add "HKLM\SOFTWARE\Policies\Claude" /v importThirdPartyHistoryIntoOrgUUID /t REG_SZ /d "YOUR-ORGANIZATION-UUID" /f
# Optional: keeps these computers on this organization
reg add "HKLM\SOFTWARE\Policies\Claude" /v forceLoginOrgUUID /t REG_SZ /d "YOUR-ORGANIZATION-UUID" /f
```

On macOS, in a custom settings payload for the preference domain `com.anthropic.claudefordesktop`:

```xml theme={null}
<key>importThirdPartyHistoryIntoOrgUUID</key>
<string>YOUR-ORGANIZATION-UUID</string>
<!-- Optional: keeps these computers on this organization -->
<key>forceLoginOrgUUID</key>
<string>YOUR-ORGANIZATION-UUID</string>
```

On Linux, add these keys at the top level of the existing object in `/etc/claude-desktop/managed-settings.json`, next to your other keys, with the ID in quotation marks as a JSON string. `forceLoginOrgUUID` is optional:

```json theme={null}
{
  "importThirdPartyHistoryIntoOrgUUID": "YOUR-ORGANIZATION-UUID",
  "forceLoginOrgUUID": "YOUR-ORGANIZATION-UUID"
}
```

**3. Roll out in stages**

Deploy to a few computers on each operating system, then to the rest. If the policy or profile sets `allowedWorkspaceFolders`, first open a migrated project and a session in it on those few computers, and check that their files are there. Send users the [steps for each user](#steps-for-each-user).

Afterward, keep `importThirdPartyHistoryIntoOrgUUID` deployed and keep the Claude (third-party) data. **Settings > Import** needs both. Work done in Claude Enterprise stays there and doesn't appear in Claude (third-party).

To roll everyone back, restore your earlier configuration. If users could switch, also set `disableDeploymentModeChooser` to `true` in the policy or profile. Claude then opens with your cloud provider for everyone.

### Nothing migrated

Claude shows no error on screen when nothing migrates. The app's `main.log` usually gives the reason. Check for each of these causes:

* `importThirdPartyHistoryIntoOrgUUID` didn't arrive as a device policy.
* Claude opened with your cloud provider instead of asking the user to sign in to Claude Enterprise. If you removed the cloud provider keys, one remains. If you kept them, the user didn't click **Or sign in with Claude.ai** yet.
* The user signed in to another organization.
* Cowork runs only in its VM sandbox in Claude Enterprise, so the migration waits. Claude doesn't show **Settings > Import**, and writes `Cowork is not in host-loop mode` to `main.log` each time it opens. If [`requireCoworkFullVmSandbox`](https://claude.com/docs/third-party/claude-desktop/configuration#requirecoworkfullvmsandbox) is in the policy or profile, remove it as described under the special cases in [Before you begin](#before-you-begin), then have the user quit Claude fully and open it again. If the key isn't there, ask your Anthropic account team.
* If you kept the cloud provider keys and the welcome screen doesn't show **Or sign in with Claude.ai**, `disableDeploymentModeChooser` is still set or `deploymentMode` is `3p`. Remove both keys from the policy or profile, and `disableDeploymentModeChooser` from what your bootstrap server returns.
* On Linux, Claude rejected `/etc/claude-desktop/managed-settings.json`, for example because of its ownership, its permissions, or invalid JSON, and read none of its keys. Search `main.log` in `~/.config/Claude/logs/` for `managed-settings.json`.

### Check whether a computer has finished migrating

Claude Desktop 4.16336.0 and later write a status file, `history-import-status.json`, for each user and update it during the migration. The file's `schemaVersion` is `1`. Read it with a device-management script from the user's Claude data folder. This is the `Claude` folder that Claude Enterprise uses, not the `Claude-3p` folder:

* macOS: `~/Library/Application Support/Claude/`
* Windows: `%APPDATA%\Claude\`
* Windows, with the MSIX installer from Anthropic: `%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\`, or `%LOCALAPPDATA%\Claude-Data\claude_pzs8sxrjxfjjc\` on computers where Claude moved its data out of the package
* Linux: `~/.config/Claude/`

A script that runs as SYSTEM or root must read each user's own folder.

Claude adds an entry under `imports` when a Claude account signs in to your organization in that Windows, macOS, or Linux user account. Each entry gives its `account` and `organization` IDs in lowercase. Check the entries whose `organization` is your organization ID. If there is no such entry, the user hasn't signed in to your organization yet, Anthropic has paused the migration, or one of the causes under [Nothing migrated](#nothing-migrated) applies. Each entry has:

* `state`:
  * `complete`: every migration step that applies on this computer has run. `completedAt` is the time Claude first found the entry complete.
  * `in_progress`: `pending` lists the steps that haven't run yet.
  * `nothing_to_copy`: Claude has nothing to migrate, and doesn't run the steps left in `pending`. `reason` says why.
  * `unknown`: Claude can't read its own record of the migration, and stops the migration for this user. Ask your Anthropic account team.
* `reason`, with `nothing_to_copy` or `unknown`:
  * `no_third_party_profile`: this user account has no Claude (third-party) chats or sessions folder.
  * `third_party_profile_removed`: that folder was removed after the migration began.
  * `third_party_profile_not_recognized`: Claude can't confirm that the folder belongs to Claude (third-party).
  * `no_third_party_sessions`: the folder holds no chats or sessions to migrate.
  * `import_record_unreadable`: the reason for `unknown`.
* `gaps`: the steps that found something and couldn't migrate all of it, such as a plugin that Claude couldn't install or local MCP servers left for **Settings > Import**. A `complete` entry can still list gaps. `gaps` never lists Code sessions in untrusted folders or chats that a user starts with your cloud provider after the migration. `null` means that an earlier release started the migration for this entry and didn't record gaps.
* `pending` and `gaps` use Claude's step names, such as `sessions`, `projects`, `scheduledTasks`, `skills`, `plugins`, and `extensions`.

An entry has finished when its `state` is `complete` or `nothing_to_copy`. A computer has finished when it has at least one entry for your organization and every such entry has finished. After that, keep `importThirdPartyHistoryIntoOrgUUID` deployed and keep the Claude (third-party) data, even when `gaps` is empty. **Settings > Import** needs both.

A finished entry can change later. A Claude Desktop update, or a new step that Anthropic turns on, can change a `complete` entry back to `in_progress`. An entry with `no_third_party_profile` or `no_third_party_sessions` changes if the user later creates chats or sessions with your cloud provider.

An entry can stay `in_progress`:

* Until the user opens Claude again
* While Cowork runs only in its VM sandbox, as described under [Nothing migrated](#nothing-migrated)
* While the [skills settings](#before-you-begin) are off
* While Anthropic has paused a step

If you delete the file, Claude writes it again the next time Claude opens signed in to your organization.

## Steps for each user

1. Quit Claude fully, including from the menu bar or system tray. Then open it again.
2. If Claude opens as before instead of asking you to sign in to Claude Enterprise, choose **Sign out** from the account menu. Then, on the welcome screen, click **Or sign in with Claude.ai**. Claude restarts.
3. Sign in to your company's Claude Enterprise organization on this computer, in the same Windows, macOS, or Linux user account as before. If macOS asks for access to Documents, allow it, so that scheduled tasks can migrate.

Your chats (now in Cowork), sessions, projects, and scheduled tasks appear. Your Claude (third-party) work doesn't change. Then:

* If a scheduled task asks to use a tool, choose **Allow for all scheduled runs**.
* If a session or project is missing its folder, your files are still where they were. Attach the folder again. If Claude refuses it, ask your IT team which folders are allowed, and move the files there.
* Turn on [memory](https://support.claude.com/en/articles/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context#h_c9b905eb3f) in your settings. **Notes from Cowork** shows only while it's on.
* In **Settings > Import**, click **Add instructions** for each set of instructions listed, **Add to memory** until **Notes from Cowork** disappears, and **Import…** if a skill is missing from **Customize > Skills**. Claude may leave out notes on how it should respond, so add those to your [instructions](https://support.claude.com/en/articles/10185728-understanding-claude-s-personalization-features).
* Set up remote connectors and any missing plugin marketplaces again, install the plugins you want in **Customize > Plugins**, and add any keys or sign-ins your plugins and extensions need.

If your IT team kept your cloud provider available, you can switch between it and Claude Enterprise:

* **To go back to your cloud provider**, choose **Log out** from the account menu, then quit Claude and open it again. Claude opens with your cloud provider whenever you start it while logged out of Claude Enterprise. Sign in to your cloud provider again if Claude asks. Your Claude Enterprise work is kept for when you return.
* **To return to Claude Enterprise**, choose **Sign out** from the account menu. Then click **Or sign in with Claude.ai** on the welcome screen. Claude restarts. Sign in, and your work is where you left it. Projects and scheduled tasks that you created with your cloud provider also appear. In **Settings > Import**, click **Import…** to add chats and sessions that you started with your cloud provider, and click **Add to memory** until **Notes from Cowork** disappears.

> [!WARNING]
>
> Don't click **Remove** on the home page banner or in **Settings > Import**. It deletes your migrated chats, sessions, and projects, including any work you added after the migration.
