Can I import my ChatGPT history into Gemini or Claude?

Not as conversations. Neither imports another assistant's chats. Claude can import memory (facts about you and your preferences) from another assistant through its official memory import, and any assistant can read an exported conversation you attach as a file.

Can Gemini continue a chat I started in ChatGPT?

Only as context. Gemini's Continue this chat works on Gemini share links, copying a Gemini conversation into your account; it doesn't accept ChatGPT or Claude links. Export the ChatGPT chat and attach or paste it instead.

What format should I move a chat in?

Markdown when the assistant accepts text files or you'll paste; it keeps headings, tables and code without noise. PDF when you want the assistant to see the conversation as a document with images. Avoid screenshots; they cost tokens and lose text.

Does the new assistant remember the moved chat?

Yes, within that new conversation, as long as the file or pasted text fits its context window. Across future chats, only if you save it to the assistant's memory or project knowledge yourself.

How to Move a Conversation Between AI Assistants

To move a conversation between AI assistants you carry the content, because none of the three imports another's chats: export the chat as Markdown or PDF, give it to the new assistant as a file or pasted context, and continue from there. Claude adds an official memory import; Gemini lets a shared chat be continued, but only within Gemini. This guide covers every pair.

Quick answer: You can't import a conversation from ChatGPT into Claude or Gemini, or in any other direction; none of the three has a chat import. To continue elsewhere, export the conversation as Markdown or PDF, attach or paste it into a new chat in the other assistant with a one-line brief, and carry on.

Claude can additionally import memory from another assistant, and a Gemini share link can be continued by another Gemini user, but neither moves a ChatGPT or Claude chat into Gemini.

What moves and what doesn't

	ChatGPT → Claude	Claude → ChatGPT	ChatGPT → Gemini	Gemini → ChatGPT	Claude → Gemini	Gemini → Claude
Conversation import	No	No	No	No	No	No
Memory / preferences	Claude's official memory import	No	No	No	No	Claude's memory import
Continue a shared link	No	No	No	No	No	No
Exported file as context	Yes	Yes	Yes	Yes	Yes	Yes
Full-history export usable	JSON files can be attached	JSON can be attached	ZIP contents can be attached	Takeout HTML can be attached	JSON can be attached	Takeout HTML can be attached

The only pair with an official bridge is into Claude, and it moves memory rather than conversations (Anthropic's import and export your memory article); moving between ChatGPT and Claude covers that flow and Claude's import article in detail.

Gemini's Continue this chat copies a Gemini conversation into another Gemini account from a share link; it's a Gemini-to-Gemini feature, not an import.

Everything else is the file route.

The file route, step by step

Export the conversation from where it is.
- Claude: the Claude extension's Markdown button for the whole chat (Claude to Markdown), or PDF if images matter.
- ChatGPT: the ChatGPT extension's Word or PDF export (ChatGPT to Word); for one answer, the copy button gives Markdown.
- Gemini: the Gemini extension's Markdown or PDF button (Gemini to Markdown). If the chat is long, consider exporting only the assistant's replies (a setting in the Claude and Gemini extensions) or selected messages (Claude and ChatGPT extensions); the new assistant doesn't need every false start.
Start a new chat in the destination and attach the file, or paste the text if it's short. All three accept PDF and text uploads in their web apps; Word files are accepted as well.
Write a brief above it. Two or three sentences: what the project is, what the previous assistant concluded, what you want next. Assistants do far better with a stated goal than with a bare transcript.
Ask for a read-back. "Summarise what you've understood from this conversation in five bullets before we continue." Correct the summary. This is where misreadings of tables or truncated context show up.
Decide what to persist. If the destination has memory or project knowledge, save the summary there rather than the whole transcript, so future chats start informed.

Which format for which situation

Markdown when the content is text, tables and code. It's compact, the structure survives, and the assistant reads it as text rather than as an image of text.
PDF when the conversation contains images, charts or diagrams the next assistant needs to see, or when you want a fixed record attached alongside the live chat.
Word when the destination is a workflow rather than an assistant, or when the ChatGPT extension is your only exporter and you'd rather not convert.
The full-history export when you're moving everything at once. ChatGPT's conversations.json and Claude's JSON can be attached and queried ("list the conversations about X"), but they're large; extract what you need rather than attaching the whole archive to every chat.

Moving in bulk

Switching assistants for good is a different job from moving one conversation:

Request the full-history export from the old assistant (ChatGPT, Claude, Gemini) and keep it as the archive.
Export the ten or twenty conversations you actually reuse as Markdown or PDF documents.
In the new assistant, create a project or folder per topic and attach the relevant documents as knowledge, with a summary note.
If the destination is Claude, run the memory import so preferences carry over.
Keep the old account open until the new one has what you need; links and exports die with the account.

What never transfers

These never transfer:

Custom instructions.
Saved memories (except into Claude).
Gems and custom GPTs.
Connectors and integrations.
The assistant's internal state about a conversation.

Write down the instructions you relied on before you move; they're a paragraph, and they're the part people forget.

The sharing and export comparison shows what each assistant's exports include so you can plan what to capture by hand.