
Move ChatGPT context to Claude honestly: export, memory and Projects, plus Krater conversation import formats, limits and preservation boundaries.
Short answer: You cannot import your ChatGPT conversation history as native Claude chats. Claude does support importing memory, and Projects can hold selected documents as reference material. Those are different from restoring a chat archive. If your business needs a searchable conversation workspace across model families, export ChatGPT and use Krater's conversation import panel under Settings, then Data. Keep the original archive until you have checked the imported conversations.

For an SMB, migration is usually about continuity: client instructions, decisions, useful drafts and the reasoning behind them. A memory summary can carry working preferences, but it will not recreate every discussion. A project knowledge file can preserve a brief, but it will not become the original conversation with its branches and timestamps.
Compare the destination in our Claude alternatives guide. If you want to keep several model families available, explore the all-in-one AI workspace and check Krater's plans and credits before choosing a migration route.
| Route | What it moves | What it does not promise |
|---|---|---|
| ChatGPT export | A downloadable copy of eligible account data | A Claude-compatible restore operation |
| Claude memory import | Selected remembered facts, preferences and working context | Your original conversation list or complete transcripts |
| Claude Projects | Reference documents and project instructions | Conversion of uploaded transcripts into native historical chats |
| Krater conversation import | Supported conversations from a provider export | Perfect reproduction of every attachment, branch or provider feature |
Open ChatGPT, select your profile, then Settings, Data controls and Export data. Confirm the request and download the ZIP when the notification arrives. OpenAI says exports can take up to seven days and download links expire after 24 hours. Check the account and workspace before requesting it: the self-service export is not available for ChatGPT Business, Enterprise or Healthcare workspaces. An administrator may need to help with organization-managed data access.
Keep a copy somewhere your business has approved for sensitive information. An export can contain more than the two conversations you wanted to move. Check it before sending it to another service, and avoid sharing download links in team channels. Exporting also does not cancel a subscription, delete an account or restore conversations that were already deleted.
For the broader handover, read switching from ChatGPT. It is worth separating the archive task from the decision about which subscription to keep.
Anthropic's help center says importing conversation history from another AI provider is not currently possible. Its memory import instead asks the previous service to produce remembered information. You review that text, then paste it into Claude's import flow. The current instructions point to Settings, Your Claude, then Start import; an older settings layout uses Settings, Memory. After import, review what Claude actually learned.
Remove private client details and obsolete preferences before submitting the text. A generated memory export is not a certified inventory of every past conversation. Anthropic also describes memory imports as experimental and says they may not always incorporate imported memories successfully. Ask Claude to explain the resulting context, then correct omissions directly rather than assuming the operation was complete.
For a live business project, a concise handover often matters more than a giant transcript. Create a Claude Project, add approved documents to its knowledge and set project instructions for the intended output. Anthropic's Projects guide describes uploaded documents, text files and code snippets as context for chats in that project.
A useful handover includes the current objective, accepted decisions, source documents, unresolved questions and examples of the required output. Label any copied AI draft as a draft. Uploading this material gives Claude a reference; it does not preserve your ChatGPT thread as an editable native conversation. See switching from Claude if you also want to retain an export from the destination later.
The panel accepts ChatGPT ZIP and Claude ZIP exports. For Gemini it accepts ZIP, JSON or HTML. The maximum applies to the uploaded file; a valid extension alone does not establish that the archive contains a supported export. Do not rename a random file to ZIP or combine unrelated documents and expect the importer to understand them.
The ChatGPT parser reads supported conversation export files, including legacy and sharded layouts. It follows the active conversation branch and imports supported user and assistant content. It can use source titles and timestamps, with model information where present. This is not a promise that every source field, historical model setting, alternate branch, image or attachment survives. Check a short thread and a long thread with files before calling the migration complete.
Krater brings 500+ AI models and 1,400+ app connections into one workspace. That does not transfer a ChatGPT or Claude subscription entitlement. For the Google route, compare transferring ChatGPT history to Gemini and switching from Gemini.
No. Anthropic does not document a native conversation-history import from another provider. You can supply selected material as context, but that is not a restored sidebar or a faithful historical thread.
No. It transfers the text you provide for Claude to incorporate as memory. Review the output and remove sensitive details. It is not a complete backup, and Anthropic warns the feature is experimental.
Not until you have verified the conversations you need and followed your business retention policy. Retain a secure original if you need source material that the importer does not preserve.
Checked November 2026: OpenAI export guidance; Claude's history-import limitation; Claude memory import; Claude Projects. Krater instructions were checked against its conversation import panel and provider importers.