Standard AI Conversation Portability Does Not Exist Yet: Here Is Why That Should Bother You

Source: Dev.to

The Current State of AI Data Exports

ChatGPT exports your data as a conversations.json file. It is a nested JSON structure containing every conversation as a tree of message nodes. Each node carries an ID, parent ID, author role metadata, content parts array, status flags, weight values, timestamps, and various internal properties.

A two‑year conversation history can produce a file north of 500 MB. The nesting depth makes it expensive to parse. The metadata‑to‑content ratio is heavily skewed toward overhead, and the structure is entirely ChatGPT‑specific. No other AI platform understands this format because no standard defines what an AI conversation export should look like.

Claude’s export is also JSON, but with a different structure, different metadata, and the same fundamental problem: a platform‑specific format with no interoperability.

There is no equivalent of IMAP for AI conversations—no common schema, interchange format, or RFC.

This Is an Engineering Problem Worth Caring About

We accept data portability as a baseline requirement in every other category of software:

• Databases have SQL dumps and standard import formats.
• Email has IMAP and MBOX.
• Cloud storage has standardized file systems.
• Social media platforms, under regulatory pressure, now export data in formats that third‑party tools can process.

AI assistants have escaped this expectation so far because the industry is young and the data involved is harder to categorize. A conversation history is not a table, a file, or a simple message thread; it is an evolving context that shapes how the system responds over time. Porting raw text is not enough—you need to port the structure, the relationships between topics, and enough organizational context for a new system to actually use it.

A Working Implementation

Phoenix Grove Systems shipped a tool called Memory Forge that converts raw export files from ChatGPT or Claude into a structured “memory chip” file.

• Architecture: All processing happens client‑side in the browser. No server calls, no data transmission. Users can verify this by monitoring the Network tab in dev tools during the process.
• Output: A single file cleaned of platform‑specific metadata, indexed by conversation topic, and formatted with system instructions that any AI can parse on ingestion.
• Usage: Load the memory chip into any AI platform that accepts file uploads (Claude, Gemini, Grok, etc.) and the new system gains access to the user’s full conversation context—projects, preferences, working patterns, and accumulated understanding all transfer.
• Cost: $3.95 per month. Processing a large export takes minutes, not hours.

Whether evaluated as a product or a proof of concept, the takeaway is the same: the AI conversation portability problem is solvable with current technology. The reason it has not been solved by the platforms themselves is not technical; it is strategic. Lock‑in drives retention, and portability threatens it.

What a Standard Could Look Like

A portable AI conversation format would likely need:

1. Flat or shallow‑nested structure that any system can parse without platform‑specific knowledge.
2. Clear separation between user messages, AI responses, and system/metadata content.
3. Topic or thread boundaries that allow selective loading rather than all‑or‑nothing ingestion.
4. Header block containing context instructions (similar to what Memory Forge generates) so the receiving AI knows how to use the data.

Think of it as a “.mbox for AI”—not sexy, but functional.

Phoenix Grove Systems has effectively built a proprietary version of this with their memory chip format. Whether the industry converges on a standard or tools like Memory Forge become the de‑facto bridge remains an open question. The longer platforms wait to address portability, the more third‑party solutions will fill the gap.

The Bigger Pattern

Every major technology category has gone through this cycle:

• Proprietary lock‑in → User frustration → Third‑party bridges → Eventual standardization

Email took about fifteen years, mobile numbers about ten, and cloud data portability is still in progress.

AI conversation history is at the very beginning of this curve. Platforms have little incentive to move; users are just starting to realize the lock‑in exists. The first tools to break it open are now shipping.

If you work in AI, build tools for AI, or heavily use an AI assistant such that your conversation history has real value, this is worth paying attention to. The portability question is coming; it’s just a matter of whether the industry leads or gets dragged.

Memory Forge is available at if you want to give it a try.