One read of Claude Documentationclaude-docs-20261102T193711Z
2 pages moved out of 281 read.
Pages moved
2
significant first
Pages read
281
in this capture
Captured
19:37 UTC
Corpus hash
d88b7418e240
corpus-hash
What this read moved
1-2 of 2third-party/claude-desktop/data-storage Changed · +12 / -5 lines
from line 168
168168
169169## Move a user to a new device
170170
171On devices that get their managed configuration from MDM, you can move a user to a new device by copying their data. The copy moves:
171On devices that get their configuration from MDM or from the [Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md), you can move a user to a new device by copying their data. The copy moves:
172172
173173* Chats, Cowork tasks, and Code sessions
174174* Projects, project instructions, and memory
from line 193
193193
194194* The same platform (macOS, Windows, or Linux) and CPU architecture as the old device
195195* The same OS user name and home-directory path. Otherwise, Code sessions, scheduled tasks, plugins, and project folders stop working.
196* The managed configuration, with the same [`deploymentOrganizationUuid`](https://claude.com/docs/third-party/claude-desktop/configuration#deploymentorganizationuuid), in place before Claude Desktop launches
196* The same organization as the old device:
197 * **MDM**: the managed configuration, with the same [`deploymentOrganizationUuid`](https://claude.com/docs/third-party/claude-desktop/configuration#deploymentorganizationuuid), in place before Claude Desktop launches
198 * **Enterprise Admin Console**: no managed configuration to deploy. When the app asks the user to sign in to Claude, they use the same account and organization as on the old device.
199* Anything on the device that your configuration relies on for credentials, set up as on the old device. For example, a [credential helper](https://claude.com/docs/third-party/claude-desktop/credential-helper.md) or other helper script, an [AWS named profile](https://claude.com/docs/third-party/claude-desktop/bedrock.md#named-profile), or a [Google Cloud credentials file](https://claude.com/docs/third-party/claude-desktop/vertex.md#credentials-file).
197200* The same Claude Desktop version, or a newer one
198201
199202### Copy the data to the new device
from line 205
202205>
203206> The copy holds full conversations. Encrypt any intermediate copy, restrict access to it, and delete it when you're done.
204207
2051. Quit Claude Desktop on both devices. Closing its window isn't enough.
2081. Quit Claude Desktop on both devices, without signing out. Closing its window isn't enough.
2062092. If the new device has an application-data directory (see [Where data lives](#where-data-lives)), delete it. This removes anything the user created in it.
2072103. Copy these to the same paths. On Windows, use a copy tool that supports paths longer than 260 characters.
208211 * The application-data directory, except these files in it, which the app creates again when it needs them:
from line 221
218221 * `~/.claude/` and `~/.claude.json`
219222 * The folders and repositories that the user's projects, scheduled tasks, and Code sessions use
2202234. Make the user the owner of the copied files, with read and write access. Give no other user account access to the application-data directory, `~/Claude/` or `~/Documents/Claude/`, `~/.claude/`, or `~/.claude.json`.
2215. Have the user launch Claude Desktop, sign in if the app asks, and confirm that their chats, Cowork tasks, Code sessions, and projects appear. If they don't, check that the managed configuration has the old device's `deploymentOrganizationUuid` and that the user owns the copied files. Soon after launch, a scheduled task runs once if it recently missed a run.
2245. Have the user launch Claude Desktop, sign in if the app asks, and confirm that their chats, Cowork tasks, Code sessions, and projects appear. If any are missing, check that:
225 * The user owns the copied files
226 * The [`ant-did`](#identity) file in the application-data directory has the same contents as on the old device. If it doesn't, start again from step 1.
227 * With MDM, the managed configuration has the old device's `deploymentOrganizationUuid`
228 * With the Enterprise Admin Console, the account menu at the bottom of the sidebar shows the same organization as on the old device. If it shows another name, look for a managed profile that [keeps the device off the admin console](https://claude.com/docs/third-party/claude-desktop/admin-console.md#keep-a-device-on-its-managed-profile). If you find one, remove it, then have the user relaunch Claude Desktop and sign in. Otherwise, have the user choose your organization from the account menu and sign in.
2222296. Have the user [set up what the copy doesn't move](#what-the-user-sets-up-again).
2237. If the old device stays in use, its enabled scheduled tasks run on both devices. Retire the old device, or turn off its scheduled tasks in Claude Desktop there. To remove the user's data from it, see [Removing data](#removing-data).
2307. Soon after launch on the new device, a scheduled task runs once if it recently missed a run. If the old device stays in use, its enabled scheduled tasks run on both devices. Retire the old device, or turn off its scheduled tasks in Claude Desktop there. To remove the user's data from it, see [Removing data](#removing-data).
224231
225232## Removing data
226233
third-party/claude-desktop/admin-console Changed · +1 / -1 lines
from line 31
3131| Data | Does Anthropic store it? |
3232| - | - |
3333| Prompts, model responses, and tool inputs and outputs | **No.** They go to your inference provider, and tool calls go to the connectors you configure. Data handling at the provider depends on the provider, as described under [Data handling by provider](https://claude.com/docs/third-party/claude-desktop/overview.md#data-handling-by-provider). |
34| Conversation history, projects, memory, and uploaded files | **No.** They stay on the device. |
34| Conversation history, projects, memory, and uploaded files | **No.** They stay on the device. To take them to another device, see [Move a user to a new device](https://claude.com/docs/third-party/claude-desktop/data-storage.md#move-a-user-to-a-new-device). |
3535| Provider credentials, API keys, bearer tokens, and MCP secrets | **No**, except the client secret of a Google Desktop-app OAuth client, which Google doesn't treat as confidential. You can enter one for [Google sign-in to your provider](#choose-how-users-authenticate-to-your-provider) or for a [managed MCP server that signs in with Google](https://claude.com/docs/third-party/claude-desktop/mcp-sign-in.md#where-the-client-secret-goes). Everything else stays on the device, and the console refuses to save it. |
3636| Plugin and skill content | **No.** It stays in your own repositories or on devices. The console stores marketplace locations and installation settings, not content. |
3737| OpenTelemetry export, if you configure a collector | **No.** It goes to your collector only. |