The short version
Save Claude Project instructions, source files, decisions, and examples before an account change makes them difficult to recover.
Making Claude Projects Portable — Part 2 of 5. Begin with Part One: Migrating Claude Projects from One Account to Another.
You have a Claude Project that works exactly the way you want. The instructions are tuned. The right files are sitting in the knowledge base. A dozen conversations contain decisions you made weeks ago and promptly stopped thinking about.
Then something changes.
Maybe you switch accounts. Maybe your organization gives you a different Claude account. Maybe you simply decide the project has become important enough that losing it would hurt.
I learned this lesson while moving my own Claude Projects between accounts. The migration worked, but it also made something painfully obvious: I had treated Claude as the place where the project lived instead of one place where I used the project.
That distinction matters.
Claude’s Data Export Is a Backup, Not a Restore Button
Claude lets individual users export their account data, including conversation data. But Anthropic currently says that export cannot be imported into another personal Claude account to recreate the account you left behind.
That means clicking “Export data” is worth doing, but it should not be your entire backup plan.
Think about what actually makes one of your Claude Projects useful:
| What matters | Why you need it |
|---|---|
| Project instructions | Tell Claude how to work |
| Knowledge files | Supply the source material |
| Key decisions | Preserve what you already figured out |
| Work in progress | Keep unfinished work from disappearing |
| Examples | Show what “good” looks like |
| Starting context | Help a new project get up to speed |
The account contains all of that in different places. Your backup should bring the important pieces together.
Ask Claude to Inventory the Project
Before leaving an account, open each important Project and ask Claude to document it.
I used a migration prompt for this in my original post. You can take the same idea one step further and create a project inventory.
Copy and Customize
Review this entire project and prepare it for backup.
Create a structured project inventory containing:
- Project purpose and intended audience
- Current project instructions
- Important terminology and preferences
- Key decisions already made
- Work still in progress
- A list of knowledge files and what each contributes
- Important examples or finished outputs worth preserving
- Five representative prompts that show how this project is normally used
- Missing information I should save separately
- A recommended first prompt for rebuilding this project elsewhere
Separate facts you can verify from anything you are uncertain about. Do not invent missing information.
Save the result as a plain Markdown or text file.
Plain text is boring. Boring is good when you need something to still open five years from now.
Keep Your Own Copies of the Knowledge Files
Your knowledge base may contain PDFs, Markdown files, spreadsheets, images, reference documents, or code.
Keep the originals outside Claude.
For my own work, that usually means files live in a local project folder, GitHub repository, or cloud storage first. Claude gets a copy. Claude is not the archive.
This also makes updating a project easier. When a reference changes, you know which copy is authoritative.
Make a Small Backup Kit
You do not need an elaborate archival system. A useful backup can be surprisingly small:
my-project/
README.md
project-instructions.md
migration-summary.md
knowledge/
examples/The README explains the project.
The instructions tell the Gen AI system how to behave.
The migration summary preserves decisions and unfinished work.
The knowledge folder contains your source files.
The examples folder contains two or three outputs that show the quality, format, and voice you expect.
That is enough to rebuild a surprising amount of context.
One Exception: Organization Migration
There is now an important exception to the manual process. Anthropic supports moving some personal Claude accounts into Team or Enterprise organizations. That process can transfer chats, Projects, project instructions, files, memory, and other material. Some things, including custom skills and connected-service authorizations, do not move automatically.
That is very different from moving between two ordinary personal accounts.
Know which situation you are in before you start copying files.
Quick Backup Check
Before you consider a Claude Project backed up, make sure you can answer yes to these:
- I have a copy of the project instructions
- I have the original knowledge files
- I have a summary of important decisions
- I know what work remains unfinished
- I saved examples of important outputs
- I have a starting prompt for rebuilding the project
- I requested an account data export if I may lose access
You do not need to wait until you are changing accounts to do this.
If a Claude Project has become useful enough that you would be irritated to lose it, it is useful enough to back up.
Next in the series: Part Three: Build a Portable Claude Project Kit, scheduled for October 10, 2026, at 4:45 AM Central. Turn those scattered backup files into a portable Project Kit you can actually maintain.
Series visuals
Use the Claude Project Portability Roadmap as your checklist. The collection also includes the migration-summary guide, Claude Toolbox, Train the Assistant for Your Work, and Cross-Platform Prompting Tips.