How to Export ChatGPT to Claude (Chats, History & Files)

There is no official ChatGPT-to-Claude import — on either side. The working method is three steps: (1) export your ChatGPT conversations as readable files (Markdown or PDF, not the raw JSON archive), (2) bring the ones you need into Claude — as Project knowledge files or by pasting single messages, and (3) keep the full export as a local backup so nothing depends on either platform. Expect about 30 seconds per conversation with a free browser extension, or one batch run for the whole history with the desktop app.

Set expectations before you start, because "migrate" means different things for different parts of your account:

The honest summary: your content moves as files; your setup (memory, instructions, project structure) is re-created by hand. That’s true for every tool on the market — no exception exists because neither OpenAI nor Anthropic offers an import.

You have two routes, and they serve different needs:

Route A — The whole account, as an archive. ChatGPT’s Settings → Data Controls → Export Data emails you a ZIP of conversations.json. It’s complete, but it’s machine-readable JSON — you can’t attach it to a Claude Project or read it as documents. Keep it as the safety-net copy; it’s not the migration format.

Route B — Readable files, per conversation or in bulk (recommended for migrating). The free XWX AI Chat Exporter extension exports any open ChatGPT conversation as Markdown or PDF in one click — code highlighting, tables, and math survive, and each file carries YAML frontmatter with the date, model, and source URL. Markdown, TXT, and JSON exports are free and unlimited.

1. Install XWX AI Chat Exporter from the Chrome Web Store — no account or signup.

Step 2 — Open the conversation you want to move. Go to chatgpt.com and open the chat; the extension detects it automatically.

Step 3 — Click Export and choose Markdown. The file downloads immediately, formatted and self-contained. Choose PDF instead if the conversation is a deliverable you’ll share as-is.

For years of history, one conversation at a time is the wrong tool. The XWX Backup desktop app (Windows) pairs with the extension and batch-exports your entire ChatGPT library — filtered by date or selected in bulk — into a local folder: one Markdown file per conversation, already-saved chats skipped on re-runs. You can also put it on a schedule, which doubles as your ongoing backup after the migration is done.

The practical migration pattern: batch-export everything once, migrate the top conversations deliberately, and keep the local folder as the permanent archive. You get the full history in Claude-readable form without trying to hand-carry 2,000 chats into a Project.

Claude reads files, not platform histories. Depending on how you work:

• Project knowledge (best for ongoing work). Create a Claude Project for the topic — a client, a codebase, a research line — and attach the exported Markdown or PDF files as Project knowledge. Every conversation in that Project can then draw on them. This is the closest thing to "importing" your history: the knowledge is available in context, even though there’s no chat-by-chat timeline.
• Single messages (best for one-off references). Open the exported file, copy the exchange you need, paste it into a new Claude chat. Markdown pastes cleanly — tables and code blocks included.
• Custom instructions. If you had ChatGPT custom instructions, copy the text into Claude’s profile preferences or the Project’s instructions field. It’s a two-minute job people forget.

A note on scale: Claude Projects have file-attachment limits (count and size), and they change over time — check Claude’s current limits before uploading a 300-file archive. Migrate the conversations you actually reference; keep the long tail in the local archive where anything is retrievable.

ChatGPT’s memory doesn’t export, and Claude’s memory is a separate system — there is no memory transfer, whatever any tool claims. What you can do in ten minutes:

1. Skim your most important exported conversations — the ones where you corrected the model, stated preferences, or established how you work.
2. Distill them into a one-page context primer: who you are, your stack and tools, writing style, recurring projects, standing preferences.
3. Paste the primer into Claude’s profile preferences, or keep it as the first file in every Project.

Users who do this report it works better than platform memory — because you control it, it’s inspectable, and it survives the next platform switch too.

Migration is rarely a light switch — most people run both platforms for weeks. Two habits make that period safe:

• Keep the scheduled backup on. With XWX Backup’s scheduled export enabled, every new ChatGPT conversation lands in your local folder on its own — so even after you stop living in ChatGPT, the archive stays current. The same schedule covers Claude, Gemini, and ten other platforms, so both sides of your transition stay backed up in one place.
• Export from Claude too. Claude has the same structural weakness you’re leaving ChatGPT for: no per-chat export button, and an official export that’s a JSON dump. The same extension exports Claude conversations to Markdown or PDF — see how to back up Claude conversations.

The result is a local archive that belongs to you, not to either vendor — which is the actual end state of a successful migration.

The bottom row is the setup this guide builds: a complete, readable archive on your own disk, with the working subset living in Claude Projects.

• No importer exists. Neither OpenAI nor Anthropic offers history import or export between the platforms — every method above produces files you move yourself.
• The chat timeline doesn’t reappear in Claude. Exported conversations become files and Project knowledge, not scrollback in Claude’s sidebar.
• Memory and custom GPTs don’t transfer. Memory is rebuilt via the primer in Step 3; custom GPTs have no Claude equivalent — their instructions can be pasted into a Project’s instructions.
• Project attachment limits apply. Check Claude’s current file limits per Project before bulk-uploading.
• ChatGPT Plus isn’t cancelled by exporting. This guide moves your content; manage your OpenAI subscription separately.

• Developers consolidating on Claude Code — the coding workflow lives in Claude, but months of debugging context are stranded in ChatGPT. Exporting the relevant threads into Project knowledge keeps the context with the work.
• Teams standardizing on one platform — when a workspace settles on Claude, each member migrates their own history; batch export makes that an afternoon, not a week.
• Privacy-motivated movers — keeping a local, plain-file archive of everything either platform holds, independent of any vendor’s policies.
• Dual-platform users — most movers keep both accounts. A shared local archive plus Projects on each side beats loyalty to either.

If you’re leaving for backup reasons rather than platform preference, start with automatic backups — you can keep ChatGPT and stop worrying about it.