Home » Guides » Back Up a Claude Workspace: What You Can Export and What Lives Locally

Back Up a Claude Workspace: What You Can Export and What Lives Locally

Title card for a guide to export Claude data: Back Up a Claude Workspace: What You Can Export and What Lives Locally

Short answer

To back up a Claude workspace starts with the data export, then the copies the export never makes for you. At CoworkStrategy.com I sort it into what the export covers and what each computer keeps, so you can decide today what to copy yourself.

What to knowKey fact
Who runs the organization exportOnly the Primary Owner, on Team and Enterprise plans
Local session historyStored on each user’s computer
Retention for local dataOutside Anthropic’s standard retention policies; admins can’t centrally manage or delete it
Cloud sessionsSessions and files are saved to the member’s Claude account
MemoryAll memory data is included in data exports

Sources: Export your organization’s data, Local conversation storage, Chat search and memory, Export your Claude data.

Most owners treat the Export data button as the backup. It does cover conversations, users and projects. It skips the files Claude made for you, anything deleted before you ran it, and the history of every session that ran on someone’s laptop. This isn’t a sync and it isn’t a restore button. It’s a record, and you fill the gaps yourself.

What a Claude Data Export Covers, and Who Can Run It

Anthropic’s guide to exporting organization data says organization exports are only available to Team and Enterprise plan Primary Owners, from Organization settings > Data and privacy, on the web or in Claude Desktop. The export holds conversation data and user data. A download link arrives by email, you have to be signed in to open it, and it expires 24 hours after delivery.

Two gaps catch people. The Word, Excel, PowerPoint and PDF files Claude creates are not in the export; you download those from the chat while they’re still available. And messages, files or projects deleted before you run the export won’t be in it.

Flow diagram for a Claude data export: the Primary Owner runs the export, saves the file before the link expires, downloads the files Claude created, and only then deletes anything
Deleted work never reaches a later export, so the delete always comes last.

So the order matters: export first, delete second. Memory does come along, and Claude memory for teams covers what the owner turns on. For the member list CSV and who holds which role, my guide to what an owner can pull for the team lists each export.

Setting this up across a staff? Claude for teams setup on Strategized.ai decides who exports, who keeps copies and how often.

Let Members Export Their Own Claude Chats

Anthropic’s export article for individual users covers Team and Enterprise members too. They can export their own chats once an owner turns on “Allow members to export their own data.” The member then opens Settings > Privacy on the web or in Claude Desktop and clicks “Export data.” There is no export from the iOS or Android apps.

That copy covers the member’s own chats, not the contents of files they uploaded. Primary Owners never see the personal button, because they export the whole organization instead. And an export can’t be imported into another personal Claude account, so treat it as a record, not a move.

Claude Organization settings, Data and privacy, Data controls section with the organization Export data button and the Allow members to export their own data setting marked
Organization settings, Data and privacy, Data controls: the organization Export data button and the Allow members to export their own data setting. Captured 2026-10-17.

In my own setup, the Primary Owner runs the export and the member toggle stays off until someone asks for their own record. Retiring a skill follows the same keep-a-copy rule: remove a Claude skill without losing work.

Back Up a Claude Workspace on Each Computer

This part lives outside the admin settings. Anthropic’s admin page on local conversation storage says that for local sessions, conversation history is stored on users’ computers. That history sits outside Anthropic’s standard data retention policies, and admins can’t centrally manage or delete it. On Enterprise, admins can retrieve it through the Compliance API.

Sessions in the cloud work differently: sessions and files are saved to the member’s Claude account. Projects follow the same split. A project used in local sessions keeps its data on that computer, and a cloud project is saved with the account.

Decision diagram to back up a Claude workspace: a cloud session is saved to the member's Claude account, while a local session keeps its history on that user's computer
Where a session ran decides where its history lives.

Picture Marco, who runs the office at a small garden design studio. His laptop is due for replacement on Friday, and he has run local sessions on it for months. On Thursday he opens the chat where Claude drafted this month’s updates and asks, “List the files you created for me in this chat.” Claude names each Word document it made, each one still downloadable in the chat. He saves them to the studio’s shared drive, because the organization export won’t carry them. The owner runs the export that afternoon and saves the file before the link expires. The old laptop stays in a drawer until Marco has checked the new one.

Before you rebuild a project, check what fits in project knowledge. Saving a skill? Read the skill file first so you know what you’re keeping. If a client asks where their data goes, start with what an owner can check on privacy. The homepage collects more tested Claude strategies, and so do the free Claude guides on Strategized.ai.

Michael’s take

The export button feels safer than it is. For me, the export is the record and my own folders are the backup: every skill’s original file, the documents Claude made that I still use, and the project files. The real risk on a small team is a laptop. When it dies, its local history goes with it, and nothing in the admin settings reaches it. If all your work runs in the cloud and you never delete anything, a regular export may be all you need.

Your 10-Minute Claude Backup Checklist

Not sure who holds the export? Anthropic’s roles page says you can check your organization’s Primary Owner under Settings > Account.

  1. Confirm who holds the Primary Owner seat.
  2. Have the Primary Owner run Export data and save the file where only owners can open it, before the link expires.
  3. Download the Word, Excel, PowerPoint and PDF files Claude made that you still use.
  4. Save each skill’s original file and your key project documents in a shared folder.
  5. List which computers run local sessions, and copy what you need before any of them is replaced.
  6. Decide whether members may export their own chats.

Solo or a small business? Book a free call at CoworkConsultant.com and I’ll go through your backup list with you. Running a team? Claude for teams setup on Strategized.ai sets who exports, who keeps copies and how often.

Frequently Asked Questions

Can I back up a Claude workspace without the Primary Owner?

Only partly. CoworkStrategy.com notes that members can export their own chats once an owner turns on the member export setting, but the full organization export belongs to the Primary Owner.

Does a Claude backup need to cover local session history?

Yes. CoworkStrategy.com notes that local session history is stored on each user’s computer, outside Anthropic’s standard retention policies, and admins can’t centrally manage or delete it.

Are the files Claude creates part of a Claude data export?

No. CoworkStrategy.com flags that organization exports skip the Word, Excel, PowerPoint and PDF files Claude creates, so download them from the chat while they’re available.

How long is the link to export Claude data valid?

24 hours after delivery. CoworkStrategy.com notes the link arrives by email, opens only when you’re signed in, and a new export gets you a fresh link.

Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai and creator of the Claude AI Strategy Stack. Michael sets Claude up for client teams and runs his own five-site content operation on Claude, so what he writes here is tested in real work first.

 ·  Connect on LinkedIn →

Not Sure Where to Start?

Read It

Start with the free guides on this site, then the Learn Claude guides at Strategized.ai when you want the longer walkthroughs.

Learn Claude guides

Install It

The free Foundation Plugin teaches Claude the basics of your work in one download. No application, no card.

Get the free Foundation Plugin

Have It Set Up for You

For your business, Strategized.ai sets Claude up for the whole team. For yourself, CoworkConsultant.com builds your own setup or a custom plugin.

How we help businesses
Just you? See how we help

Two Ways to Get Claude Working for You

Do it yourself with the free guides and plugin, or have it set up for you. Either way you end up in the same place: a Claude workspace configured around the way you work.

Do It Yourself

The free Foundation Plugin, the guides on this site, and the Learn Claude library at Strategized.ai. No application, no card.

Get the free Foundation Plugin

Have It Set Up for You

For your business: Strategized.ai sets Claude up for the whole team, configured for every role, trained on their own work and handed over.

How we help businesses

For yourself: CoworkConsultant.com builds your own Claude setup, or a custom plugin around the job you repeat most.

How we help individuals
The Foundation Plugin: free for business owners and professionals Get it free → Instant download. No account.