Guide · Updated August 2026
How to export ChatGPT to Claude
There's no “send to Claude” button in ChatGPT and no “import conversations” button in Claude — the transfer is always export first, then bring the context in. The working path: request your archive from ChatGPT under Settings → Data controls → Export data, download the ZIP from the email link, then turn the conversations.json inside into something Claude can hold — because Claude can't read the raw ZIP, and a full history is far too large to paste. That last step has three routes: Claude's built-in memory import (fast, but moves only stored memory), a summary you write yourself, or a distilled context document built from your entire history. Whichever you pick, the goal is the same: one clean block of context in Claude's settings or a project, so it knows your work from the first message. Here is the whole path, including the part most guides skip: what to actually do with the ZIP once you have it.
Step 1 — Export your data from ChatGPT
- Open Settings → Data controls → Export data and confirm.
- Wait for OpenAI's email — minutes for most accounts, up to 24 hours for huge histories.
- Download the ZIP before the link expires (24 hours).
Full walkthrough with troubleshooting: How to export your ChatGPT data
Step 2 — What's inside the export
| File | What it is |
|---|---|
conversations.json | Every conversation you've ever had, with full message history — the file that matters |
chat.html | The same history, viewable in a browser |
user.json | Your account details |
message_feedback.json | Your thumbs up/down history — safe to ignore |
Step 3 — Get it into Claude
Claude can't swallow a chat archive directly, so pick the route that matches how much of your history you want to keep:
A. Upload key files to a Claude Project Free · manual
Good for a handful of important documents. Doesn't work for the history itself — conversations.json is usually far past project knowledge limits, and raw logs make noisy context.
B. Claude's memory import Free · memory only
Settings → Capabilities → Import memory. Moves the short list of facts ChatGPT stored about you — worth doing, but it never touches your conversations. See what it covers and misses →
C. Analyze the full export Complete
Upload the ZIP to ChatGPTToClaude exactly as you downloaded it. Every conversation is analyzed and distilled into one Claude-ready context document — projects, preferences, people, decisions, writing style. Paste it into Claude's profile preferences or a Project and keep working.
Which route should you pick?
The honest decision rule: it depends on how much your history is worth to you.
- You barely used ChatGPT (a few dozen casual chats): do the memory import, paste a paragraph about yourself into Claude's profile preferences, and move on. Nothing else is worth the effort.
- Your work lives in a handful of documents, not conversations: upload those files to a Claude Project directly — route A covers you.
- Months of real work happened in chat — projects discussed, preferences established, decisions made across hundreds of conversations: that substance exists nowhere except conversations.json, and distilling it (route C) is the only way it survives the move. Run the free preview first; it will show you concretely what your history contains.
The routes also stack: memory import plus a distilled document is strictly better than either alone.
After the transfer, make Claude prove it
Don't assume the context landed — test it. After pasting your document, open a fresh Claude conversation and ask: “Based on what you know about me, what am I working on and how do I like answers formatted?” A good transfer means Claude answers with your actual projects and preferences, unprompted. Then try a real task — draft an email, continue a project discussion — and check it applies your context instead of just reciting it. If something important is missing, add it as a line in the document; it's Markdown, and editing it is the point.
Common mistakes to avoid
- Uploading conversations.json straight into a chat. Even when it fits, raw logs bury the signal — the model spends its attention on noise, and old misunderstandings come along for the ride.
- Relying on memory import alone. It moves a short list of stored facts, not the months of context that never made it into memory. Treat it as a bonus, not the transfer.
- Letting the download link expire and giving up. Re-request the export; it's free and unlimited.
- Deleting your ChatGPT account the same day. Keep it for a couple of weeks until you've verified everything important made the trip — an active account is the only way to re-export.
Frequently asked questions
Can Claude read my conversations.json file?+
Partially. You can upload files to a Claude Project, but a full conversations.json is usually far too large for project knowledge limits, and raw chat logs are noisy context. Distilling the file into a structured context document works much better than uploading it raw.
Do I need ChatGPT Plus to export my data?+
No. Data export is available on every ChatGPT plan, including free accounts, from Settings → Data controls → Export data.
Which file from the export do I actually need?+
conversations.json — it contains your entire chat history. ChatGPTToClaude accepts the whole ZIP as-is, so you don't need to unzip or pick files yourself.
Is there a button in Claude to import ChatGPT conversations?+
No. Claude's built-in import (Settings → Capabilities → Import memory) transfers only ChatGPT's stored memory facts, not conversations. Moving the substance of your history requires bringing it in as distilled context.
Can I move my ChatGPT history to Claude for free?+
Partly. The memory import is free, uploading individual files to a Claude Project is free, and ChatGPTToClaude analyzes any export free — including a complete document if your history has 3 or fewer substantial conversations, or one built from your top 3 otherwise. Paying only ever buys the full-history document.
Full switching walkthrough: How to switch from ChatGPT to Claude →