Switch to Claude without starting over

TL;DR Highlight

Anthropic wants to import user context and preferences from other AI services (like ChatGPT) into Claude — a cross-platform memory portability play.

Who Should Read

Users interested in AI assistant personalization and data portability, and product folks thinking about user context as a competitive moat vs. portable infrastructure.

Core Mechanics

Anthropic is exploring a feature to let users import their conversation history, preferences, and context from other AI services into Claude.
The idea is to reduce the friction of switching to Claude by bringing accumulated context (preferences, communication style, recurring topics) with you.
This is a direct counter to the 'lock-in via context accumulation' dynamic where users stay with one AI service because it knows them well.
Technical challenges: different services store context in incompatible formats; privacy implications of cross-service data transfer; verifying the authenticity of imported data.
If successful, this shifts the competitive dynamic from 'whose AI knows you best' to 'who has the best underlying model and features' — a more level playing field for challengers.

Evidence

The feature concept was described in Anthropic product discussions/announcements, signaling it's at least in active consideration if not development.
HN commenters were divided: some welcomed portability as pro-user, others noted that accumulated context is a legitimate competitive differentiator AI companies have invested in building.
Privacy-focused commenters raised concerns about what data would be transferred, how it would be stored, and whether this creates new attack vectors.

How to Apply

If you're building AI products with long-term user context, treat context portability as a coming industry norm — design your context storage with export formats in mind now.
For users: document your key preferences, communication styles, and recurring context manually (in a simple text file) regardless of whether any AI supports import — this makes switching less painful today.
Product teams should think about what context truly differentiates their experience (can't be trivially imported) vs. what's table-stakes personalization (preferences that should be portable).

Code Example

snippet

# Memory extraction prompt provided by Anthropic (paste into your existing AI)

I'm moving to another service and need to export my data.
List every memory you have stored about me, as well as any
context you've learned about me from past conversations.
Output everything in a single code block so I can easily copy it.
Format each entry as: [date saved, if available] - memory content.
Make sure to cover all of the following — preserve my words verbatim where possible:
- Instructions I've given you about how to respond (tone, format, style, 'always do X', 'never do Y').
- Personal details: name, location, job, family, interests.
- Projects, goals, and recurring topics.
- Tools, languages, and frameworks I use.
- Preferences and corrections I've made to your behavior.
- Any other stored context not covered above.
Do not summarize, group, or omit any entries.

Terminology

Context portabilityThe ability to transfer your accumulated AI conversation history, preferences, and personalization data from one service to another.

Lock-inWhen accumulated data, workflows, or integrations make it costly to switch to a competing service — here referring to context/memory accumulated with one AI assistant.