Skip to main content
Switching from Claude does not mean starting from a blank page. OpenWork imports your past conversations into a workspace, where they look and behave like any other chat: you can read them, search them, and pick up where you left off with any model. What you can bring depends on where the conversation happened in Claude.

Claude Code

Imports directly. Sessions are saved on your computer, so OpenWork finds them for you.

Claude chats

Imports from Claude’s data export. Request it in Claude, then choose the file in OpenWork.

Cowork tasks

Not available. Claude’s export does not include Cowork tasks.
All imports happen in Settings → Import, in the workspace you want the conversations to live in.
The Import page in OpenWork settings, listing two Claude Code sessions ready to import, a drop area for a Claude export, and Cowork tasks marked as not available.

Settings → Import finds the Claude Code sessions saved for this folder. Chats come from your Claude export.

Import is rolling out. If you don’t see Import under your workspace in Settings, update OpenWork, or ask your OpenWork admin to turn on Desktop: import Claude conversations.

​
Claude Code sessions

Claude Code saves every session in a folder on your computer. OpenWork reads the sessions that belong to the folder your workspace uses.
1

Open the same folder in OpenWork

Create or select the workspace for the project folder you used with Claude Code. Sessions are matched by folder, so a session started in ~/code/website appears in the workspace for ~/code/website.
2

Open Settings → Import

Claude Code sessions in this folder lists every session it found, newest first, with how many messages it has.
3

Choose and import

Sessions you haven’t imported yet are already ticked. Untick any you want to leave behind and select Import. Each one appears in your workspace’s chat list straight away. Select Open to jump to it.
An imported Claude Code session in OpenWork: the original question, a finished Read step, and Claude's answer.

An imported Claude Code session reads like any other chat, including the tools Claude ran.

Working across several folders? Switch workspace in the Settings sidebar and import each folder’s sessions in turn.

​
Claude chats

Conversations from claude.ai and the Claude desktop app come from Claude’s data export. Claude prepares the export and emails you a link; OpenWork reads the file it gives you.

​
1. Request your export from Claude

  1. In Claude, open Settings → Privacy.
  2. Select Export data and confirm.
If you don’t see Export data, your organization has turned off personal exports. Ask a Claude organization owner to switch on Allow members to export their own data under Organization settings → Data and privacy, or to export for you.

​
2. Download the conversations file

Claude emails you when the export is ready. In our tests that took under a minute, but Claude says it can take up to 12 hours.
1

Open the link in the email

Use a browser where you are signed in to Claude. The link downloads a small list of downloads (a file named manifest-….json), not your conversations.
2

Open the conversations link inside that list

Open the manifest and visit the link next to "category": "conversations". That downloads a file named like conversations-000.zip. Large exports have more than one: download each conversations-… file.
3

Download it straight away

Links expire after 24 hours and can stop working once used. If a link no longer works, request a new export.
You can ignore the other files in the list, such as light_metadata-000.zip. They hold account details, not conversations. If you choose the manifest itself, OpenWork tells you which file to pick instead.

​
3. Import into OpenWork

1

Open Settings → Import

Under Claude chats, drop your conversations-… file onto the page, or select Choose Claude export and pick it.
2

Pick the conversations

OpenWork lists every conversation in the file, newest first, with conversations not yet imported already ticked. Untick anything you don’t want.
3

Import

Select Import. Each conversation appears in your workspace’s chat list.

​
Cowork tasks

Claude’s data export does not include Cowork tasks, and Claude offers no other way to download them. We confirmed this on October 23, 2026: a Cowork task created alongside a regular chat was missing from the export, while the chat was included. Cowork tasks now run in Anthropic’s cloud by default, which is why there is no local copy to read either. Until Claude makes them exportable, bring the useful parts across yourself:

Save the files

Open each task you rely on and download the files it produced (More ways to open → Download). Put them in your OpenWork workspace folder.

Keep the know-how

Turn instructions you repeat into a skill. Skills you wrote for Cowork move with the migration prompt.

​
What comes across

​
Good to know

Yes. An imported conversation is a regular OpenWork chat. Type a message and it continues with the model you have selected, which sees the imported history: ask about something said in Claude and it can answer.
Nothing is duplicated. Conversations you already imported show Imported and can’t be ticked. Each conversation is imported once per workspace.
You kept using it in Claude after importing it. OpenWork keeps the copy you already have, including anything you added in OpenWork, and does not overwrite it.
Into the workspace you have selected in Settings, on this computer. Nothing is uploaded to OpenWork’s servers. Your export file is read and then left where it is; delete it when you are done if you no longer need it.
You’ll see every conversation in an organization export. Import only the ones that are yours, or that your organization has agreed to move.
OpenWork reads files up to 256 MB. For bigger histories, request an export with a shorter date range and import each one.

​
Next steps

Move plugins and skills

One prompt moves your Claude plugins and the skills you wrote.

Keep using Claude models

Add an Anthropic API key to continue imported conversations with Claude.