Does Anthropic let me export Claude Projects?

Yes, partially. You can download your full account data — including conversations — from Settings → Privacy → Export data. The export gives you JSON of every chat. What it doesn't cleanly give you is the Project structure itself: the custom instructions, the uploaded files, and the per-project context that makes Projects useful in the first place. Those you have to capture by hand, and that's what most of this guide is about.

Why bother backing up Claude Projects?

Two reasons. One: every Anthropic model rollout (Sonnet 4 → 4.5 → Opus 5, etc.) changes how Projects behave — instructions that worked great on one model land differently on the next. Two: features get reshuffled. Anthropic has already iterated heavily on Projects since launch; assume the version you're using today won't be the version you're using next year. Your instructions and reference files are the work you put in. The Project shell is rented.

What's the fastest way to copy a Project's instructions out?

Open the Project → click the project name at the top → Edit project instructions. Select all, copy, paste into a plain text file or your notes app. Repeat for every Project. Tedious but bulletproof. Do the same for any 'project knowledge' files: download them back to your machine. The whole thing takes 2 minutes per Project.

Can I import Claude Projects into ChatGPT or Gemini?

Not natively — there's no migration tool. But the instructions are just text and the files are just files. Paste the instructions into a ChatGPT Custom Instruction or a Gemini Gem, re-upload the files where the other platform allows it, and you've reconstructed the Project's shape. The conversations don't transfer, but the working setup does.

How often should I back this up?

Whenever you change a Project's instructions meaningfully, and once a month for everything else. Pair it with your other end-of-month admin: pay invoices, do the books, back up your Projects. Five minutes.

How does Konshus help here?

Konshus has a Claude importer (export ZIP and share-link methods, both supported). The conversations land in your vault and get distilled into a portable persona you can paste into any AI. The Project instructions you've saved out become a separate stable artifact in the vault — versioned, searchable, exportable to whatever platform you move to next.

A guide · ~5 min read

How to back up your Claude Projects

Projects is the best thing Anthropic has shipped for power users — a place where Claude actually remembers what you're working on. It's also the part of Claude that gets reshuffled the most. Instructions you've spent months refining live behind a UI that could look different next quarter. Here's how to make sure the work survives the next change.

The four things to capture

Project instructions. The custom system prompt you've tuned for each Project. This is the highest-leverage thing to save — most of the value is here.
Knowledge files. Any docs, references, PDFs, or code you uploaded into the Project. Download them back to your machine.
Conversation history. Use Settings → Privacy → Export data. You'll get a JSON dump of every chat across every Project.
Working examples. If a particular conversation captures how the Project should behave (a great response, a clean workflow), copy that whole thread into your notes. It's the easiest way to rebuild the feel.

The 5-minute monthly routine

Open each Project, click the project name, hit Edit project instructions, copy the whole block, paste into a plain text file named claude-project-[name].md.
Click into the project knowledge panel and re-download any files you've uploaded. Save them in the same folder.
Once a month, go to Settings → Privacy → Export data and request the conversation export. Anthropic emails you a ZIP. Save it somewhere outside Claude.
Commit the folder to a private repo, sync it to a drive you control, or drop it in a vault. Anywhere but only-in-Claude.

What you're actually protecting against

Model rollouts. A new Sonnet or Opus changes how instructions are interpreted. The Project you tuned for the old model may need a rewrite — and you want the original to diff against.
Feature reshuffling. Projects has already changed shape multiple times. Assume the UI, the file limits, and the structure won't be identical a year from now.
Switching tools. Maybe you move to ChatGPT for a specific workflow. Maybe Gemini ships something compelling. Your Project instructions are the portable artifact — the rest is platform-specific.
Account issues. Rare, but billing failures and terms disputes happen. The export is small. Do it.

Short answer

Copy each Project's instructions into a plain text file, re-download any uploaded knowledge files, and run Anthropic's Settings → Privacy → Export data monthly for the conversation history. Store everything outside Claude. When the next model rollout or feature change lands, the work you put into Projects will still be yours.

The portable answer

Konshus has a Claude importer that handles the export ZIP and share-link methods both. Conversations land in your vault and get distilled into a portable persona you can paste into ChatGPT, Gemini, or whatever ships next. Your saved Project instructions live alongside as stable artifacts — versioned, searchable, exportable.

See also what happens when Claude Projects gets deprecated and Konshus vs Claude Projects for the longer view on why the Project shell shouldn't be where your work lives long-term.

Frequently Asked Questions

Your Projects work shouldn't live only in Claude.

Save the instructions, distill the conversations, keep a portable persona that works across every AI you'll use this decade.

Meet Konshus