How to Move ChatGPT Conversations to Claude or Gemini
Published · Updated
Switching AI platforms raises an uncomfortable question: what happens to the history you built up? The honest answer comes first. No tool can recreate your conversations inside Claude or Gemini, because those platforms offer no way to import another platform's history. Your old threads will never appear in the new sidebar, no matter what any product page promises.
What you can do is more useful than it sounds: export your history into portable files, move the context that actually matters by hand, and keep a searchable archive for everything else. This guide walks through that realistic path with ChatVault, including the manual steps, because pretending they do not exist would waste your time.
Why no tool can truly auto-move your chat history
A conversation inside ChatGPT, Claude, or Gemini is not a file you can drag between apps. It lives in that platform's database, tied to your account there, and none of these platforms accepts imported history from a competitor. There is no import button, no supported API for recreating foreign threads, and no way to transplant the memory a platform built up about you.
ChatVault does not auto-import into another platform either, and it never will claim to. What it produces are portable files — Markdown for reading, JSON for structure — that you fully control. The last mile of any move is manual: you decide what context the new platform needs, and you paste it in yourself.
Treat any tool promising one-click migration with suspicion. Recreating history would require writing into the destination platform's database as you, which no public interface allows; what such tools actually deliver is the same export-and-paste path described in this guide, with the manual steps hidden from view. Knowing the real shape of the problem helps you judge those claims — and plan realistically for the curating only you can do, because no script knows which conversations still matter to you.
What moves and what stays behind
Setting expectations before you export saves frustration afterwards. The content of your chats travels well; the platform-specific scaffolding around them does not:
| Item | Does it move? |
|---|---|
| Prompt and reply text | Yes — exported as Markdown, TXT, HTML, or JSON files |
| Code blocks and tables | Yes — formatting and language tags preserved in Markdown |
| Platform memory and personalization | No — each platform builds its own; you re-seed it manually |
| Projects and custom instructions | No — recreate them by hand on the new platform |
| Uploaded files and attachments | No — kept as structured references in the export, not as files |
| Shared links and model settings | No — they belong to the old platform's account |
Step one: export your history to portable files
The export step is the only part of the move that is automated, and it runs locally on your device. If you are leaving ChatGPT, the walkthrough on the export ChatGPT conversation history page applies; leaving Claude, use the export Claude conversation history flow instead. The short version:
- Install ChatVault and enable the platform you are leaving, granting only that site's host permission.
- Open a signed-in tab for that platform and run a scan to enumerate your conversations.
- Select everything and export both JSON and Markdown.
- Open manifest.json in the ZIP and retry any chat flagged incomplete, so the archive you move from is proven whole.
- Unzip the archive somewhere permanent. This folder is your source of truth for the entire move.
Step two: choose the conversations worth moving
Most history does not deserve a move. Dead ends, one-off questions, and superseded drafts have no value in a new account, and dumping thousands of old messages into a fresh platform only buries the threads that matter. A move is a chance to curate, not to hoard.
The candidates worth carrying over are conversations that hold reusable context: ongoing projects, decisions and their reasoning, prompts you refined over many iterations, and reference answers you keep returning to. Search the archive to find them — the local Vault indexes everything you exported with platform and date filters — and aim for a short list you could read through in an afternoon.
Step three: seed the new platform with a context brief
This is the manual part, and it is where the move actually happens. For each conversation or project that matters:
- Open the exported Markdown of the chat and read it once, end to end.
- Write a short context brief in your own words: the goal, the constraints, the decisions already made, and the open questions.
- Start a new conversation on Claude or Gemini and paste the brief as your first message.
- Paste the most relevant excerpts from the export when the thread needs detail — a code block, a requirements list, a draft.
- Save the conversation in the new platform's project or memory features if you use them, so the seeded context persists there.
- Repeat per project. Resist pasting whole histories into a single thread; a focused brief outperforms a data dump every time.
Keep the archive as your searchable memory
Everything you did not move stays useful. When the new platform needs an old detail — a command you once settled, a decision's rationale — search the Vault or grep the JSON files, find the original chat, and paste the excerpt you need. Over a few weeks, the archive shifts from something you consult daily to something you consult rarely, and that is the sign the move worked.
If you later switch again, the same archive serves the next move. JSON stays the lossless record with a declared schema version, so the files you export today remain readable by future tooling, whichever platform you land on.
Frequently asked questions
Can I import my ChatGPT history into Claude directly?
No. Claude offers no way to import another platform's history, and neither does Gemini. The workable path is exporting your chats to portable files, then seeding the new platform with a context brief and the excerpts that matter, as described in this guide.
Will Claude or Gemini remember my old conversations after I move?
No. Each platform's memory and personalization are built from your activity on that platform and cannot be transplanted. You re-seed context manually per project, and the new platform learns from there.
Is it safe to paste exported chats into another AI platform?
The export step is fully local: ChatVault has no backend and your content never leaves your device while files are produced. The moment you paste text into another platform, that text goes to that provider under its own privacy terms. Read the target platform's data policy and redact anything sensitive before pasting.
Can ChatVault move my chats between platforms automatically?
No, and cross-platform auto-migration is not on its feature list. ChatVault exports portable Markdown, JSON, TXT, HTML, and ZIP archives with completeness checks. Choosing what to carry over, and pasting it into the new platform, remains a manual decision.
Which format should I use for moving chats: Markdown or JSON?
Export both. Markdown is what you read and paste from when seeding context, since it preserves code blocks, tables, and lists. JSON is the lossless archive for long-term storage and any tooling you build later. HTML works well when you want to share a chat with a person.
Does this work in the other direction, from Claude to ChatGPT?
Yes, the method is symmetric. Export from the platform you are leaving with ChatVault, curate the conversations worth moving, and seed the destination with context briefs. The limits are identical too: no platform imports foreign history, so the last mile is always manual.