Import history from claude.ai changedthird-party/claude-desktop/import
Nearest release: v2.1.305, published 3 hours after 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 20 Oct 2026 16:09 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 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+31added
Lines−5removed
From line
2
where the diff opens
First seen
18 Aug 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 2, old and new numbered
/
from line 2
22
33> Bring conversations, projects, and local Cowork and Code sessions into Claude Desktop on 3P from a claude.ai workspace or an earlier install
44
5Import brings a copy of your claude.ai conversations and projects into Claude Desktop on third-party (3P), along with any Cowork and Claude Code sessions already on this machine from an earlier install. Everything lands in the local session store described in [User identity and local data](/docs/third-party/claude-desktop/data-storage), so you can pick up work you started on claude.ai and continue it against your organization's own inference provider.
5Import brings a copy of your claude.ai conversations and projects into Claude Desktop on third-party (3P), along with any Cowork and Claude Code sessions already on this machine from an earlier install. Everything lands in the local session store described in [User identity and local data](/docs/third-party/claude-desktop/data-storage.md), so you can pick up work you started on claude.ai and continue it against your organization's own inference provider.
66
77Each import is a one-time copy. New activity on claude.ai after you import does not appear in Claude Desktop unless you import again, and re-running the import does not create duplicates.
88
99## Automatic import of earlier third-party sessions
1010
11Claude Desktop can automatically copy into your history the Cowork, Chat, and Code sessions it stored on this computer under an earlier third-party configuration. In an organization managed from the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console), this automatic copy is on unless it's turned off in your organization's settings. In any other deployment it runs only if your administrator turns it on.
11Claude Desktop can automatically copy into your history the Cowork, Chat, and Code sessions it stored on this computer under an earlier third-party configuration. In an organization managed from the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console.md), this automatic copy is on unless it's turned off in your organization's settings. In any other deployment it runs only if your administrator turns it on.
1212
1313Along with the sessions, the automatic copy brings over other things you had under the earlier configuration:
1414
from line 28
2828
2929* Your administrator has turned import on by setting [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport) with `enabled` set to `true` in the managed configuration. The import wizard is off by default; until then, **Settings → Import & export** has no **Import…** button and reports that import isn't enabled for this deployment. The [automatic import of earlier third-party sessions](#automatic-import-of-earlier-third-party-sessions) doesn't depend on this setting.
3030* If your administrator lists the claude.ai organizations you may import from, with `allowedOrganizationUuids` under [`claudeAiImport`](/docs/third-party/claude-desktop/configuration#claudeaiimport), you can import only by signing in to claude.ai, and only from a listed organization. A sign-in to any other organization or to a personal account is refused, and the wizard's options to import from a file or from earlier sessions on this computer are turned off. The [automatic import of earlier third-party sessions](#automatic-import-of-earlier-third-party-sessions) isn't affected by this list.
31* Claude Desktop is installed and running in third-party mode. See [Installation and setup](/docs/third-party/claude-desktop/installation).
31* Claude Desktop is installed and running in third-party mode. See [Installation and setup](/docs/third-party/claude-desktop/installation.md).
3232* To bring history over from a claude.ai Team or Enterprise workspace, an owner of that workspace has enabled member data export (next section). Personal claude.ai accounts can always export.
3333
3434## Enable member data export (admins)
from line 37
3737
3838
3939
40The member data export toggle in claude.ai organization settings. Only workspace owners see this control.
41
4042Members of the workspace can then export their own conversations. The toggle does not expose one member's data to another; each member can download only their own history.
4143
4244## Open the import wizard
from line 47
4547
4648
4749
50Step 1 of the import wizard, before a source is chosen.
51
4852The wizard has three steps: **Chats** (your claude.ai export), **Cowork & Code** (local sessions on this machine), and **Review**. Skip any step you don't need. A fourth step, **Duplicates**, appears after the import only when an imported project has the same name as one you already have. See [If a project already exists](#if-a-project-already-exists).
4953
5054## Step 1: claude.ai chats and projects
from line 61
5761
5862
5963
64The organization selector, shown if your claude.ai account belongs to more than one workspace.
65
6066
6167
68The authorization prompt. The only permission granted is a one-time export of your own data.
69
6270Back in Claude Desktop, click **Fetch export**. The wizard requests an export from claude.ai, downloads it, and shows what it found.
6371
6472
6573
74The wizard after the export finishes downloading.
75
6676**Choose a downloaded file**
6777
6878On claude.ai, go to **Settings → Privacy → Export data** and click **Export**. If you don't see **Export data**, ask a workspace owner to [enable member data export](#enable-member-data-export-admins).
from line 79
6979
7080
7181
82The Export data page in claude.ai personal settings.
83
7284claude.ai emails you a download link when the export is ready. The link expires after 24 hours.
7385
7486
7587
88The export-ready email.
89
7690Download the `.zip`, then in the import wizard click **Choose file…** and select it.
7791
7892
7993
94Step 1 with a downloaded export selected.
95
8096Click **Continue**, or **Skip this step** if you only want to bring in local sessions.
8197
8298## Step 2: local Cowork and Code sessions
from line 101
85101
86102
87103
104Local sessions found on this machine.
105
88106Sessions are copied, not moved. Your original history stays where it is.
89107
90108## Step 3: review and import
from line 111
93111
94112
95113
114The review summary before import.
115
96116
97117
118Import complete. Imported chats appear in the sidebar and imported projects appear on the Projects page.
119
98120## If a project already exists
99121
100122When an imported project has the same name as a project already in Claude Desktop, the wizard adds a **Duplicates** step after the import finishes. This happens, for example, when you set up **Northwind** on this machine and then bring over history from another machine that also has a Northwind project. The step lists each match with two choices.
from line 123
101123
102124
103125
126The Duplicates step, listing imported projects that match ones you already have.
127
104128* **Merge into existing** moves the imported chats and sessions into your existing project and removes the duplicate. Folders you attached to the duplicate move with them. If your existing project has no instructions of its own, the imported project's instructions are shown there for you to review and accept. Later imports from the same source land in the existing project as well.
105129* **Keep separate** leaves both projects in place. The imported one keeps a numbered name, such as **Northwind (1)**, and Claude Desktop stops offering to merge it.
106130
from line 139
115139
116140
117141
142The trust prompt shown the first time you resume a conversation imported from claude.ai.
143
118144## Make an imported project folder readable in Chat
119145
120146When an import brings over a project, it puts a folder on the project. In Chat, Claude can't read that folder until you add it to the project again. Add the folder once for each imported project.
from line 163
137163
138164Importing the project again doesn't make its folder readable. If you remove the import under **Import history** in **Settings > Import & export**, or archive the project, and then import from claude.ai again, the new project uses the same folder. Add the folder to the new project again.
139165
140Your administrator can also limit which folders Claude reads. See [Project folders in Chat](/docs/third-party/claude-desktop/chat#project-folders-in-chat).
166Your administrator can also limit which folders Claude reads. See [Project folders in Chat](/docs/third-party/claude-desktop/chat.md#project-folders-in-chat).
141167
142168## Export sessions to move them to another device
143169
144170When your administrator also sets `exportEnabled` to `true` under `claudeAiImport`, **Settings → Import & export** offers **Export…**, which writes this computer's chats, Cowork tasks, and Code sessions (not terminal Claude Code sessions) to a zip file. On the other device, open the import wizard and select that zip with **Choose file…**; the wizard lists its sessions in the [Cowork & Code step](#step-2-local-cowork-and-code-sessions). The export is a one-time snapshot, not a sync, and the zip contains full conversation content, so handle it as sensitive data.
145171
146The zip includes sessions, project names, and each session's output files when they total 100 MB or less. It leaves out project instructions, memory, scheduled tasks, skills, plugins, and attached files. To move those, your administrator can [copy your data to the new device](/docs/third-party/claude-desktop/data-storage#move-a-user-to-a-new-device). Sign-ins and connector connections don't move either way.
172The zip includes sessions, project names, and each session's output files when they total 100 MB or less. It leaves out project instructions, memory, scheduled tasks, skills, plugins, and attached files. To move those, your administrator can [copy your data to the new device](/docs/third-party/claude-desktop/data-storage.md#move-a-user-to-a-new-device). Sign-ins and connector connections don't move either way.
147173
148174## What is and isn't included
149175
No line in this hunk matches that.