Guide · Updated August 2026
Switch from Claude to ChatGPT without starting over
Whether you're switching back or running both, the awkward truth is that ChatGPT has no import feature at all — nothing pulls your Claude history in for you. The working path has three steps: export your data from Claude (Settings → Privacy → Export data; the download link arrives by email, usually within minutes), distill that history into one compact document, and hand it to ChatGPT somewhere it will actually persist — Custom Instructions for the essentials, a dedicated project or memory for the rest. What transfers is the substance of your work: projects, preferences, decisions, and how you like answers written. What doesn't is Claude-specific plumbing like published artifacts and original project files, which stay behind. This guide walks each step, maps where every Claude concept lives on the ChatGPT side, and ends with a practical suggestion: run both assistants for two weeks before you commit.
Step 1 — Export your Claude data
- In Claude, open Settings → Privacy.
- Click Export data and confirm.
- Anthropic emails you a download link — download the ZIP promptly.
Need a single chat, a PDF, or your Claude Code sessions? Every Claude export option →
| File | What it is |
|---|---|
conversations.json | Every Claude conversation with full message history |
projects.json | Your Projects: names, instructions, docs |
users.json | Your account details |
Step 2 — What transfers, what doesn't
- Transfers as context: who you are, your projects and their state, preferences, standing instructions, people and companies, decisions, writing style.
- Needs manual rebuild: Project structure and knowledge files (re-upload into ChatGPT Projects), and any Artifacts you want to keep (download them from Claude first).
- Doesn't transfer: the conversations themselves — ChatGPT can't ingest a chat archive.
Step 3 — Get your context into ChatGPT
A. Paste into memory Free · quick
Open a new ChatGPT chat and paste your context document with “Please remember this about me.” With memory enabled, ChatGPT stores the key facts and applies them to future conversations.
B. Custom Instructions & Projects Free · durable
Put the “about me” and “how to respond” essentials into Settings → Personalization → Custom Instructions (mind the character limits), and paste project-specific context into each ChatGPT Project's instructions.
C. Build the document from your full history Complete
Upload your Claude export ZIP as-is. Every conversation is analyzed and distilled into one ChatGPT-ready context document — the input that makes options A and B actually good.
Where each Claude thing lives in ChatGPT
| In Claude | ChatGPT equivalent |
|---|---|
| Profile preferences / “how to respond” | Settings → Personalization → Custom Instructions |
| A Project with instructions + knowledge | A ChatGPT Project — paste the instructions, re-upload the files |
| Memory (stored facts) | Memory — paste your facts with “please remember this” |
| Artifacts | No direct equivalent — download them from Claude and re-upload where needed |
| Claude Code sessions | Separate world — they never leave your machine via the claude.ai export |
Fitting your context into Custom Instructions
Custom Instructions fields are short — think a couple of paragraphs each, not a document — so don't try to paste your whole context there. The split that works: the durable essentials (who you are, what you do, how you want answers formatted) go into Custom Instructions, so every future chat starts right; project-specific context goes into each ChatGPT Project's instructions; and the full document lives in a Project's files or gets pasted into memory, where length doesn't matter. If you have to cut, keep instructions over facts — style preferences pay off in every single reply.
Run both for two weeks before you commit
Keep your Claude account alive during the transition, and check off before you cancel anything:
- Your export ZIP is downloaded and stored — the full export walkthrough covers every option.
- Artifacts you care about are downloaded — they are not fully recoverable once the account is gone.
- ChatGPT has answered a real “what do you know about me?” test with your actual projects and preferences.
- A week of real work has gone through ChatGPT without you reaching back for Claude — the only test that matters.
Frequently asked questions
Does ChatGPT have an import feature for Claude data?+
No. Unlike Claude (which imports memory from other AIs), ChatGPT has no built-in import at all. Your context comes in the way everything does: pasted into a chat, into Custom Instructions, or into a Project's instructions.
Where is the export button in Claude?+
Settings → Privacy → Export data. Anthropic emails you a download link with a ZIP containing conversations.json and your projects.
Can I upload my Claude export straight into a ChatGPT conversation?+
You can attach files to a chat, but a full conversations.json usually exceeds attachment limits and raw logs make poor context. A distilled context document pasted with "Please remember this about me" works far better and feeds ChatGPT's memory.
Do my Claude Projects transfer to ChatGPT?+
Project structure doesn't transfer automatically. Re-create each important project as a ChatGPT Project, paste its instructions, and re-upload its knowledge files. A context document covers the accumulated understanding that lived in the conversations themselves.
Will switching back to Claude later mean starting over again?+
No. The transfer works identically in both directions — export from ChatGPT, distill, paste into Claude — and Claude additionally imports ChatGPT's memory natively. Once you treat your context as a portable document, no switch is permanent.
Leaving over the usage caps? The Claude Max 20x vs 5x math → · Going the other way? How to switch from ChatGPT to Claude →