Move a Claude conversation to another chat or account

To export a Claude chat to ChatGPT or a fresh Claude conversation, save the useful text and prepare a handoff summary. Paste the summary into the new chat, then add the transcript and files needed for the next task. You’re carrying over the context for your work. You can’t import Claude’s account archive into another personal account.

Decide whether you need a handoff or account migration

A handoff gives the new conversation your goal, agreed decisions, and the material needed to continue. These serve as reference material without recreating the old chat in the sidebar.

Anthropic’s data-export instructions rule out importing the archive or migrating between personal accounts. Keep the account-history export as a backup.

Eligible personal accounts can move into a Team or Enterprise organization. Read the full instructions first: this one-way migration closes the personal account. Uploading a transcript doesn’t start that process.

Ask for a handoff summary before leaving

While the old chat still works, ask Claude for a compact briefing:

Prepare a handoff for a new conversation. Include:
- the goal and current state of the work
- decisions we agreed on, with reasons
- constraints and requirements that still apply
- exact filenames, relevant source links, and important values
- approaches we rejected and why
- unresolved questions and the next task
Distinguish confirmed facts from assumptions. Keep this concise.

Check the summary for outdated decisions and missing details. A confident answer can still choose the wrong version of a plan.

For example, a debugging handoff could say: parser.py handles quoted commas, blank rows still fail, and the next task is a regression test for blank rows. “We were debugging a CSV parser” leaves the new conversation to reconstruct the work.

Save the handoff with a single-reply export. Keep discarded ideas in the supporting transcript.

Save the conversation as Markdown

DocMyChat saves the open Claude conversation as a .md file in desktop Chrome.

1. Open the source conversation on claude.ai.
2. Click Export beside Share.
3. Choose Markdown.
4. Save a separate handoff copy of the downloaded file.
5. Edit that copy in a text editor to remove material the destination doesn’t need.

The file has ## You and ## Claude headings, code fences with language labels, and formulas as LaTeX. Ordinary links and the link back to the chat stay clickable. See the Markdown export guide for details. Keep the original file untouched.

The export follows the displayed branch. Check that it contains the accepted version if earlier messages were retried or edited. It saves one chat at a time.

Start the destination chat with the summary

Start the new conversation with your summary and next task:

I’m continuing work from another conversation. The summary below is
the current state. The transcript is background. First identify any
missing information, then help with the next task: fixing blank rows.

Paste the relevant Markdown text after that instruction, or try attaching the .md file. If the destination won’t accept it, paste the text or save a .txt copy in your text editor. DocMyChat has no TXT export.

Claude’s upload guide lists TXT, Word (.docx), and PDF as supported file types. Use + → Add files or photos to select a file. OpenAI’s ChatGPT upload guide lists supported documents and text files, subject to account settings and limits.

Ask the new assistant to restate the goal, current decision, and next step. Correct any misunderstanding before it changes the work.

Use a Claude Project for continuing work

For ongoing work in Claude, add your checked summary and reference files to a Project. It keeps related files and instructions together.

In the existing Projects interface, open the dropdown beside a standalone conversation’s title and choose Add to project. See Anthropic’s project-management guide for that route.

A newer Projects version is also rolling out in beta. It uses one conversation with parallel threads, so the older multi-chat instructions won’t fit every account. Use the file and instruction controls in your version.

Put current requirements in the handoff or project reference files. Don’t rely on every detail from an old exchange to carry over automatically.

Bring the files and keep the input manageable

Markdown image URLs need a signed-in Claude session. A link won’t give another assistant the image. Upload important images separately using the destination’s file controls.

Do the same for source files. For the parser example, attach the current parser.py and a small input that reproduces the bug. A long discussion containing three old versions of the code is a poor substitute for the current file.

Long transcripts can exceed the receiving system’s input or context limits. Start with the summary and the relevant sections, adding more when the task needs it. Claude’s usage and length guide distinguishes conversation capacity from account usage allowance. Starting a new chat doesn’t reset that allowance.

With code execution enabled, Claude can summarize earlier messages automatically as context fills. You may not need to move just because a conversation is long. Start a new chat when separating the next task would help.

Review what will cross into the other account

Remove passwords, access tokens, unrelated personal details, and internal discussion the next task doesn’t need. Check the transcript and summary. Sensitive material can remain in an early prompt after you’ve cleaned up the final answer.

For a different provider, review the destination account’s data settings and your organization’s rules. OpenAI’s guidance says uploaded-content use depends on the service and data settings. Don’t assume the new account has the same controls as the old one.

Keep the original conversation and saved files until the new chat has the right context. Follow the backup routine for work you’ll need beyond this handoff.

Questions