Claude Projects Export: How to Preserve Your Work

For a Claude Projects export, start with Claude’s account data export, then save the project instructions, original files, and current work summary separately. Treat the result as an archive plus a handoff; an exported account is not proof that another app can recreate your project.

That distinction matters when months of useful work sit beside old drafts and rejected ideas. Tools like fenbs keep reviewed decisions and unfinished tasks outside the chat app, so the next assistant can start with the current record. For the workspace basics, see the separate guide to Claude Projects.

How do you get the available account export?

1. Sign in to the Claude account that contains the work. On the web or Claude Desktop, open Settings, then Privacy, and choose Export data.
2. Wait for the export email, then download the archive while signed in. Use Claude’s current help instructions if the link has expired or the control is missing.
3. Keep an untouched copy in your approved storage location. Open a working copy for inspection and note which account and export date it represents.
4. Pick one active project to check first. Write a list of the conversations, instructions, source materials, and outputs you expect to preserve.

Claude’s export documentation↗ (opens in a new tab) describes account user data and conversation history. Organization members may need an owner to enable exports; the member export does not include uploaded file contents. The documentation also distinguishes exporting from migrating an account, so do not assume the archive is an importable project package.

Do the inspection before you delete, archive, or leave anything behind. A successful download tells you that a file arrived. It does not tell you whether the particular brief, final answer, or approved spreadsheet you need is inside it.

Which project materials should you collect separately?

Use a checklist based on the work, rather than guessing from the archive’s filenames. Claude’s project guide↗ (opens in a new tab) describes project knowledge and project instructions as distinct parts of a workspace. Preserve the original source for each important item wherever you can.

Keep filenames meaningful. “Client brief, approved revision” helps more than a pile of identically named downloads. If a document was replaced, label the older copy as superseded so another assistant does not choose it simply because it appears first.

How do you turn the project into a usable handoff?

Write a short current-state document alongside the archive. Its job is to answer what the next person should do, not to retell every conversation. A source transcript can show how an idea developed; the handoff must say which idea survived.

• Goal: the outcome the project is trying to produce and who will review it.
• Agreed decisions: what a person chose, why, and where the approval can be checked.
• Rules: instructions that still apply, with the project or task they cover.
• Progress: finished work, checks actually run, and anything still uncertain.
• Next step: one concrete action, its required files, and any question waiting for a person.

Say you are preparing a proposal. “Draft three is the approved structure; the staffing section still needs review” gives the next assistant a clear boundary. “We worked on a proposal” does not. Include a reference back to the relevant conversation or saved output when that evidence will matter.

The guide to organizing Claude Projects covers upkeep inside Claude; for a move between apps, fenbs keeps this reviewed record available through its supported AI connections.

How can you check that the handoff is complete?

Test the smallest meaningful continuation before you depend on the new setup. Give the receiving assistant the handoff and the relevant source files. Ask it to explain the goal, the latest decision, the unresolved question, and the first action it would take.

Compare that answer with the actual work. Does it cite the right file version? Does it recognize that a proposed change was rejected? Does it distinguish an unchecked output from a completed task? Correct the handoff before asking for a large rewrite.

Use Claude project memory as a separate topic: a useful remembered summary and a complete archive serve different purposes. Keep the archive for reference even after the shorter handoff passes your check.

What should you review before sharing the export?

An account archive can contain material unrelated to the project you are moving. Review the destination and the intended audience before uploading it anywhere. A selective handoff may be more appropriate when you only need one client project or one unfinished assignment.

Remove secrets and unnecessary personal information from the working copy you intend to share. Keep access to the original archive limited. Confirm that you are allowed to move employer or client documents, and preserve any restrictions in the handoff instead of expecting the next app to infer them.

How to do this with fenbs

1. Create a free account, then add the project whose work you want to keep portable.
2. Add the unfinished tasks with their plans and current status. Put reusable project facts in AI context notes and record people’s agreed choices in Decisions and rules.
3. Connect a supported assistant using the integration guide and browser sign-in. Ask it to read the project context before continuing.
4. Save Where we left off with what changed, what was checked, and the next action. In a fresh session, ask the assistant to explain that starting point before it works.

fenbs is free for one person, with no credit card. It is useful when the work continues across sessions or supported AI apps. It is not the right fit if your only goal is a complete transcript archive or an exact visual copy of a Claude workspace.

How do you keep the record useful after the move?

Choose one current home for decisions and progress. Keep the exported history as a dated reference, and update the active record when the work changes. Otherwise, a clean handoff gradually becomes another stale snapshot that somebody must explain.

At the end of each session, capture the next thing a colleague would have to ask. The switching models hub covers other moves, while fenbs’s work context workflow keeps the same read, work, and save routine after the export is finished.