AI conversation portability
Your chat history should outlive the model that made it.
Exporting AI conversations is easy. Keeping years of work readable, searchable, private, and movable is harder. This guide explains what ChatGPT and Claude give you, what their archives leave behind, and how to make an export useful again.
Format and policy sources last checked 16 August 2026
The useful definition
An export is not automatically portable.
A data export is a copy. Portability means you can understand that copy, keep the important parts, and move them into a different workflow without quietly losing context.
A useful conversation archive should answer five questions:
- Are the conversation titles, messages, and dates present?
- Are uploaded or generated files actually included?
- What happens to branches, projects, memories, tools, and citations?
- Can the archive be inspected without uploading private history?
- Can each conversation become readable and searchable again?
Start with the source
Export your conversations.
Request the complete account export, not a screenshot or one-chat copy.
ChatGPT
Export through Data controls
ChatGPT sends a ZIP containing chat history and account data. Current large
exports may split conversations across numbered JSON files. Uploaded assets
can be stored as generic .dat files, with their original
names recorded in a separate JSON map.
Claude
Export through Privacy settings
Claude sends a ZIP containing conversation and account data. Conversation records are stored in JSON, while some referenced files may not be present as reusable binary files.
Follow the Claude export guideCurrent format map
ChatGPT and Claude exports are not interchangeable.
This is what Vinaa’s import implementation currently sees in personal account exports.
| Archive concern | ChatGPT | Claude |
|---|---|---|
| Conversation source | Numbered conversation JSON files, or a legacy conversations.json | conversations.json |
| Conversation structure | A graph with a current visible path and possible alternate branches | Messages with parent relationships and possible branches |
| Uploaded and generated files | Uploaded binaries can be present as .dat files. Generated images were absent from the fresh August export we inspected | Extracted text and file references can be present, but binary files are often absent |
| Projects | Older exports may identify project chats with opaque IDs but omit project names. The fresh August export contained no project fields | Named project definitions are exported, but neither those files nor the conversations provide membership links |
| Memory and account data | Separate sidecars may contain sensitive account or settings data | Memory and user data can appear as separate sidecars |
| Provider-to-provider migration | Another service needs a purpose-built importer to recreate chats | Claude does not import this export into another personal Claude account |
ChatGPT details reflect one fresh personal export requested on 9 August 2026, so another account may differ. Export formats can change without notice. Keep the original ZIP and check the date on any tool or guide before relying on it for a migration.
What neither archive can reliably rebuild
Projects. An older ChatGPT archive may let an importer group chats by an opaque identifier, but without the original names those groups would need placeholders such as Project 1 and Project 2. The fresh August ChatGPT export did not include even those project fields. Claude has the opposite half of the puzzle: it exports named project definitions, but no link from a conversation to its project.
Before you upload anything
Your full chat history is unusually sensitive.
An AI archive may contain client material, source code, health questions, financial details, private files, and years of personal context. Treat it like a password manager export or a private mailbox backup.
- Prefer tools that process the archive locally.
- Check whether a viewer uploads, stores, logs, or trains on the data.
- Do not extract the archive into a public or synced folder by accident.
- Keep the untouched ZIP until the new archive has been verified.
- Delete temporary extracted copies when the migration is complete.
After export
Choose what “usable” means for you.
Keep a backup
Store the original ZIP somewhere private and backed up. This protects against account loss, but it does not make the conversations easy to use.
Convert selected chats
Turn a small number of important conversations into Markdown or PDF when you need readable, portable documents rather than a complete workspace.
Import the full history
Use a purpose-built local importer when you want every chat searchable, organized, and available to continue with another model.
A destination for the archive
Keep the work, even when you change models.
Vinaa imports complete ChatGPT and Claude exports on your Mac. It turns them back into conversations you can browse, search, organize into projects and folders, and continue with cloud or local models. Chats are stored locally. Optional sync uses your private iCloud account.
Sources and update policy
Provider account steps and migration limits were checked against OpenAI’s export documentation, Anthropic’s data export documentation, and Anthropic’s memory documentation. Format details come from the current export formats supported by Vinaa’s local ChatGPT and Claude importers. This page is rechecked when either provider changes its export format or policy.