Detailed Analysis
A Reddit user on r/ClaudeAI reports a frustrating experience with Anthropic's official memory import tool, describing how the feature successfully transferred broad preferences and general context from ChatGPT but failed to carry over the granular, project-specific details accumulated through extensive PM-style brainstorming sessions. The user's workflow relies heavily on ChatGPT Projects to develop passion projects, storing specific feature design decisions, architectural scoping choices, and other technical deliberations. Upon using Claude's memory import — accessible via Settings > Capabilities > Memory > Start import — the user found that those specifics were effectively lost in translation, leaving only a shallow representation of their working context.
This outcome is consistent with how the import tool is designed to function, though not always clearly communicated to users. Claude's memory system prioritizes work-relevant, structured information when processing imports, and actively filters out details it deems peripheral or insufficiently actionable. The import mechanism works by prompting the source AI to generate a structured export, which Claude then parses into individual memory edits over a period of up to 24 hours. Because the system is still in an experimental phase — having expanded from paid-only access in October 2025 to free, Pro, and Max plans around March 2026 — incomplete or selective retention is a documented limitation rather than a bug. Granular conversational specifics, such as the iterative reasoning behind a design choice, are particularly vulnerable to being filtered out, as they lack the discrete, preference-like structure Claude's memory extraction is optimized to recognize.
The user's predicament highlights a structural mismatch between how AI memory import tools are marketed and what they technically deliver. Users engaged in iterative, multi-session creative or technical work tend to accumulate a layered institutional memory within their AI environment — one that is deeply contextual and difficult to dehydrate into transferable facts. Claude's import feature is well-suited to capturing personality preferences, working style, and high-level project summaries, but struggles with the embedded reasoning and decision history that defines deep project work. The best-practice recommendation from Anthropic and third-party guides — maintaining a portable "AI profile" document and manually summarizing key preferences — implicitly acknowledges this gap, essentially asking users to perform the curation work that automated import cannot reliably do.
Broader trends in AI development make this problem particularly relevant. As users increasingly develop sophisticated, long-running workflows inside proprietary AI ecosystems, the switching costs between platforms have grown substantially. Anthropic's memory import tool represents one of the first serious industry attempts to reduce those costs and encourage platform fluidity, a meaningful competitive and philosophical stance in a landscape where ChatGPT, Gemini, and Claude are all vying for habitual daily use. However, the gap between the tool's promise and its current capability reflects the deeper unsolved challenge of AI memory portability: conversation history is not merely data, but accumulated context with relational structure that resists simple serialization. Until memory systems can export and import not just facts but the inferential web around them, users doing serious, iterative knowledge work will continue to face meaningful friction when switching between AI platforms.
Read original article →