How to move a Claude project to another account
Moving a Claude project to another account means carrying over the material you want to keep and setting up a new project around it. AI Chat Archive has no automatic project importer, account-transfer button or conversation-restoration feature. Its project ZIP is the starting material for a manual rebuild.
Anthropic’s data-export help page says exported data cannot be imported into another personal Claude account. It separately describes a direct personal-account migration when joining a Team or Enterprise organization. That official migration is a different workflow; this guide covers rebuilding a selected project from files.
What you can carry across
- Instructions: copy the saved prompt text into the new project’s instructions.
- Knowledge files: upload available files from the ZIP’s
files/directory, within the destination account’s current limits. - Past decisions: upload selected transcripts as reference files or write a handoff note that points to them.
- Available outputs: review exported attachments and task files, then add the ones the new project needs.
The ZIP does not restore the original sidebar, live chats, thread relationships, automatic project Memory, task execution state or connector configuration. Project access and sharing also need to be set up separately. A new chat can read an uploaded transcript and discuss it, but it starts as a new conversation.
1. Export while you can still open the source project
Install AI Chat Archive for Chrome, Edge, Firefox or Safari on macOS, then activate AI Chat Archive Pro. Whole-project ZIP export requires Pro. Single-chat export is free and unlimited in PDF, Markdown, HTML, JSON and TXT if you only need individual conversations.
- Sign in to the source Claude account and open the project. Classic projects use
claude.ai/project/…; Beta Projects useclaude.ai/code/project/…. - Click Export project on the page, or choose Export this project (ZIP) in the extension popup.
- Choose Markdown, HTML, JSON or TXT for the conversation transcripts. Markdown is convenient for reviewing and reusing text. PDF transcripts are available only through individual-chat export.
- Enable Include attachments in the ZIP if you want available chat attachments and task outputs as well. Project knowledge and Library files are attempted regardless of that setting.
- Keep the project tab open until export finishes and save every ZIP part if the archive is large.
The Claude project download page has the setup and demo, and the project-export FAQ explains the controls.
2. Unzip and check the copy
Open README.md, the root _INDEX.md and files/_INDEX.md. Read any _INCOMPLETE.md or _SKIPPED.md reports. If the export arrived in parts, follow How to combine the parts.txt from part 1 and extract every part into the same destination before judging what is missing.
Open important knowledge files and a few transcripts, including the most recent work. Classic files may be previews, thumbnails or extracted text rather than original documents. Use original copies from your computer where you have them. Resolve reported omissions while you still have access to the old account. See what’s inside the project ZIP for the exact folders and fallback behavior.
3. Create a project in the destination account
Sign in to the other Claude account and create a new project from its Projects area. Give it a name you will recognize. Use the destination account’s current project controls; their labels and upload limits can differ by plan and project version. Keep the unzipped archive open beside the new project.
You do not upload the ZIP as a project-restoration package. AI Chat Archive does not run the following setup steps for you.
4. Paste the project instructions
Open instructions.md. Copy the original text inside the fenced block into the new project’s instructions field. Leave out the # Instructions heading and fence markers added by the exporter. If the file says no instructions were set, there is no saved prompt to paste.
Read the prompt before saving it. Update references to old filenames, project names or account-specific tools if those will change. Automatic project Memory is separate from this saved instructions text and is not included in the ZIP.
5. Upload knowledge files manually
Add the useful files from files/ to the new project’s knowledge area or Library. Skip generated navigation reports such as _INDEX.md and _SKIPPED.md. For Beta Library exports, inspect nested folders too and recreate the organization where the destination supports it.
Wait for each upload to finish and confirm that the document appears in the destination. A transcript-format choice does not turn every knowledge document into that format: a downloadable PDF can remain a PDF, while a text-knowledge entry contains the text Claude exposed. Check the actual content before re-uploading a file whose name suggests an original document.
If the destination rejects a file or the project fills up, consult its current upload limits. Start with the source documents the project still uses. Keep the complete archive on your computer and add less-used material later rather than treating the entire ZIP as required project context.
6. Bring old chats in as reference material
Choose the conversations that contain decisions, requirements or unfinished work. Their transcripts are under conversations/<date>_<title>/. Add readable transcripts as project reference files where supported, or attach them to a new chat. Keep the rest locally for future lookup.
Uploading a transcript does not import it into Claude’s chat history. Messages do not reappear as live user and assistant turns. You cannot resume the original thread, preserve its identity or recreate its tool execution state by uploading Markdown, JSON or the ZIP.
For ongoing work, add a short handoff note: the goal, decisions already made, current draft or files, constraints, open questions and the next step. Check the note against the saved chats. Start a new conversation with a request such as:
Read the project instructions, source files and the attached handoff note. Summarize the current goal, the decisions already made and the open questions. Point out anything missing before we continue.
A continued Beta thread’s export can contain both its old context and its new replies. Check the transcript before uploading duplicate versions. Available chat files may be in attachments/ or outputs/; a thread’s outputs/_PROJECT_FILES.md can point to a shared file already saved under the project’s files/.
7. Check the rebuilt project
Confirm the instructions text and important filenames in the new account. Open the uploaded documents to check their contents. Then ask one question grounded in a specific source file and one that depends on the instructions. Review the responses against the sources and fix any gaps. Keep the original export as a separate archive while you work in the new project.
Troubleshooting the move
My old conversations are missing from the sidebar
That is expected for this workflow. The transcripts are files for the new project to read. Start a new conversation and point it to the relevant transcript or handoff note.
A knowledge file is missing or looks different
Check files/_SKIPPED.md and the root incomplete report. Retry the export while the source session still works. A preview, thumbnail or extracted-text copy does not recover the original binary; upload your original document if you have it.
The new project does not know something the old one remembered
Automatic project Memory is not exported. Put the specific facts or working rules you need into reviewed instructions or a reference document. Connectors, task schedules and other workspace settings also need separate setup.
Can the extension do the import for me?
No. As of 5 November 2026, AI Chat Archive exports project material and does not automatically import it into another Claude account. The workflow here is manual: create the project, paste instructions, upload files and start new chats.
The source export uses your own signed-in session and runs in your browser. Chat content is not uploaded to our servers; Pro license checks send Polar only your key. When you manually upload selected files to the destination Claude account, you are sending those files to Claude for the new project.