How to Export ChatGPT Chats for Claude, Gemini, and Other AI

Switching AI assistants does not mean losing months of prompts, research notes, or code drafts locked inside ChatGPT. The practical move is to export your threads as portable files first, then bring the text into Claude, Google Gemini, Copilot, or a local model. You keep your context; you only change the engine.

Why export ChatGPT before moving to another AI?

Chat history on chatgpt.com stays on OpenAI's platform. Claude, Gemini, and local tools cannot read your sidebar automatically. Copy-pasting one long thread at a time breaks formatting, drops code blocks, and does not scale when you have dozens of projects. A structured export gives you searchable archives and reusable prompt libraries you control offline.

• Vendor portability: your prompts are assets, not locked UI state
• Better handoffs: paste clean Markdown instead of messy chat UI selections
• RAG and local LLMs: JSON feeds chunking scripts and vector DBs
• Compliance: keep a local record before account changes or cancellations

Which export format works best for Claude, Gemini, or local AI?

Pick the format by how you plan to reuse the text. Markdown is the default for human-readable paste into Claude Projects, Gemini chats, or Notion/Obsidian bridges. JSON is best when you script ingestion, chunk messages for RAG, or filter by role (user vs assistant). HTML is best when you want a readable archive or Print to PDF for stakeholders who never touch another chat UI.

• Markdown: paste into Claude, Gemini, or a new ChatGPT thread; ideal for prompt templates and long context dumps
• JSON: structured message arrays for Python/Node pipelines and local LLM prep (see the JSON developer guide)
• HTML: readable backup; open in browser and copy sections as needed

How do you export ChatGPT chats for another AI tool?

1. Install ChatGPT Power Exporter and open chatgpt.com while signed in.
2. Open the popup, click Load list, and select conversations to migrate (or All conversations for a full library).
3. Choose Markdown for paste workflows or JSON for scripts.
4. Click Export and save the file locally. Processing stays in your browser.
5. In Claude or Gemini, start a new chat or project and paste the relevant sections, or upload the Markdown file if the product supports attachments.

For local models (Ollama, LM Studio, etc.), parse JSON exports into plain text chunks, then load them into your RAG stack. The export does not call external APIs; your data never leaves the machine during the backup step.

How much context can Claude or Gemini accept from an export?

Every model has a context window limit. Do not paste an entire 200-message thread if the target tool truncates input. Split exports by topic: one conversation per project, or trim to the last N exchanges that matter. Markdown headings from the export make it easy to copy only the "system prompt" or final assistant answer you need.

Can you bulk export before canceling ChatGPT or switching tools?

Yes. Use All conversations in the extension to snapshot your full sidebar in one run. Store the file in a dated folder (for example chatgpt-archive-2026-06). Free users can export up to 5 conversations total; Pro unlocks unlimited bulk export for EUR 19 one-time. See the bulk export guide for large libraries.

Is exporting for migration private?

ChatGPT Power Exporter processes chats in your browser. Conversation text is not uploaded to developer servers during export. Only optional Pro license verification sends a license key string. Read the privacy policy and the local export guide for details.

Related guides

• Export ChatGPT to Markdown for Obsidian, Notion & Archives
• Export ChatGPT to JSON for Developers (Scripts & Pipelines)
• How to Backup ChatGPT Conversations Before You Lose Them
• How to Export ChatGPT to Obsidian and Notion
• Private ChatGPT Export: Local Processing, No Upload