Migrate Claude Desktop from a cloud provider to Claude Enterprise changedthird-party/claude-desktop/move-to-claude-enterprise
Nearest release: v2.1.302, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 16 Oct 2026 18:39 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+28added
Lines−32removed
From line
4
where the diff opens
First seen
15 Oct 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55Move 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 on the same computer.
66
7<img className="block dark:hidden" src="https://mintcdn.com/claude-ai/ijOo7DTs1r-Xf3X5/images/third-party/diagrams/move-to-claude-enterprise-flow.svg?fit=max&auto=format&n=ijOo7DTs1r-Xf3X5&q=85&s=ed9723f563092b8ab40c50ee46afd172" alt="Flow diagram: IT updates Claude Desktop, turns on two skills settings, and changes the configuration. Cloud provider controls stop applying. 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 checks their skills." width="1000" height="548" data-path="images/third-party/diagrams/move-to-claude-enterprise-flow.svg" />
7
88
9<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/ijOo7DTs1r-Xf3X5/images/third-party/diagrams/move-to-claude-enterprise-flow-dark.svg?fit=max&auto=format&n=ijOo7DTs1r-Xf3X5&q=85&s=a85b1f96e055e395d3ce901f425e06ec" alt="Flow diagram: IT updates Claude Desktop, turns on two skills settings, and changes the configuration. Cloud provider controls stop applying. 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 checks their skills." width="1000" height="548" data-path="images/third-party/diagrams/move-to-claude-enterprise-flow-dark.svg" />
10
119## What is migrated
1210
1311The migration never changes or deletes the Claude (third-party) data.
from line 60
6260
6361Remove the old keys and set the new one in one change to the policy or profile that carries your Claude settings: an `HKEY_LOCAL_MACHINE` policy on Windows (not `HKEY_CURRENT_USER`), or a [configuration profile](/docs/third-party/claude-desktop/mdm) on macOS.
6462
65<Steps>
66 <Step title="Remove the cloud provider keys">
67 Remove every key that puts the app in third-party mode, such as those that start with `inference` or `bootstrap`. Also remove [`disableDeploymentModeChooser`](/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser) and [`deploymentOrganizationUuid`](/docs/third-party/claude-desktop/configuration#deploymentorganizationuuid). Leave other keys in place. If your settings come from a [bootstrap server](/docs/third-party/claude-desktop/bootstrap), copy the keys you want to keep into the policy or profile itself.
63**1. Remove the cloud provider keys**
6864
69 The desktop extensions feature is on after the change unless [`isDesktopExtensionEnabled`](/docs/third-party/claude-desktop/configuration#isdesktopextensionenabled) is set to `false`.
70 </Step>
65Remove every key that puts the app in third-party mode, such as those that start with `inference` or `bootstrap`. Also remove [`disableDeploymentModeChooser`](/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser) and [`deploymentOrganizationUuid`](/docs/third-party/claude-desktop/configuration#deploymentorganizationuuid). Leave other keys in place. If your settings come from a [bootstrap server](/docs/third-party/claude-desktop/bootstrap), copy the keys you want to keep into the policy or profile itself.
7166
72 <Step title="Set your organization ID">
73 Copy the **Organization ID** from [**Organization settings > Organization and access**](https://claude.ai/admin-settings/organization). Set `importThirdPartyHistoryIntoOrgUUID` to this ID, without braces or 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 accounts that aren't in that organization.
67The desktop extensions feature is on after the change unless [`isDesktopExtensionEnabled`](/docs/third-party/claude-desktop/configuration#isdesktopextensionenabled) is set to `false`.
7468
75 On Windows, in an elevated PowerShell window:
69**2. Set your organization ID**
7670
77 ```powershell theme={null}
78 reg add "HKLM\SOFTWARE\Policies\Claude" /v importThirdPartyHistoryIntoOrgUUID /t REG_SZ /d "YOUR-ORGANIZATION-UUID" /f
79 # Optional: keeps these computers on this organization
80 reg add "HKLM\SOFTWARE\Policies\Claude" /v forceLoginOrgUUID /t REG_SZ /d "YOUR-ORGANIZATION-UUID" /f
81 ```
71Copy the **Organization ID** from [**Organization settings > Organization and access**](https://claude.ai/admin-settings/organization). Set `importThirdPartyHistoryIntoOrgUUID` to this ID, without braces or 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 accounts that aren't in that organization.
8272
83 On macOS, in a custom settings payload for the preference domain `com.anthropic.claudefordesktop`:
73On Windows, in an elevated PowerShell window:
8474
85 ```xml theme={null}
86 <key>importThirdPartyHistoryIntoOrgUUID</key>
87 <string>YOUR-ORGANIZATION-UUID</string>
88 <!-- Optional: keeps these computers on this organization -->
89 <key>forceLoginOrgUUID</key>
90 <string>YOUR-ORGANIZATION-UUID</string>
91 ```
92 </Step>
75```powershell theme={null}
76reg add "HKLM\SOFTWARE\Policies\Claude" /v importThirdPartyHistoryIntoOrgUUID /t REG_SZ /d "YOUR-ORGANIZATION-UUID" /f
77# Optional: keeps these computers on this organization
78reg add "HKLM\SOFTWARE\Policies\Claude" /v forceLoginOrgUUID /t REG_SZ /d "YOUR-ORGANIZATION-UUID" /f
79```
9380
94 <Step title="Roll out in stages">
95 Deploy to a few computers on each operating system, then to the rest. Send users the [steps for each user](#steps-for-each-user).
96 </Step>
97</Steps>
81On macOS, in a custom settings payload for the preference domain `com.anthropic.claudefordesktop`:
9882
83```xml theme={null}
84<key>importThirdPartyHistoryIntoOrgUUID</key>
85<string>YOUR-ORGANIZATION-UUID</string>
86<!-- Optional: keeps these computers on this organization -->
87<key>forceLoginOrgUUID</key>
88<string>YOUR-ORGANIZATION-UUID</string>
89```
90
91**3. Roll out in stages**
92
93Deploy to a few computers on each operating system, then to the rest. Send users the [steps for each user](#steps-for-each-user).
94
9995Afterward, keep `importThirdPartyHistoryIntoOrgUUID` deployed and keep the Claude (third-party) data. **Settings > Import** needs both. To roll back, restore your earlier configuration. Work done after the migration stays in Claude Enterprise and doesn't appear in Claude (third-party).
10096
10197If nothing migrates, Claude shows no error on screen. Check that the key arrived as a device policy, that no third-party key remains, and that the user signed in to this organization. The app's `main.log` usually gives the reason.
from line 104
108104* In **Settings > Import**, click **Add instructions** for each set of instructions listed, and **Import…** if a skill is missing from **Customize > Skills**.
109105* Set up remote connectors again, and add any keys or sign-ins your plugins and extensions need.
110106
111<Warning>
112 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.
113</Warning>
107> [!WARNING]
108>
109> 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.
114110
No line in this hunk matches that.