A few weeks ago someone posted in r/ClaudeAI:
“I am trying to export data from my old Claude account to my new account. I will no longer have access to one of my email accounts soon so that is the reason for the change. I would like to transition things by 31 Jan 2026.”
Simple request. Hard deadline. No solution.
Anthropic gives you a data export — go to Settings, request your data, and you’ll get a ZIP file containing your entire conversation history as JSON. It exists because GDPR and CCPA require it. But there is no import. You can download your data, you just can’t bring it anywhere. The person losing their email account is left with an 87MB file they can’t do anything with.
This isn’t an AI limitation. It’s a product decision.
What you actually lose
If you use Claude as a thinking partner on ongoing work — projects that span weeks or months — your conversation history isn’t just logs. It’s context. Decisions made and explained. Documents drafted and iterated. Research done. Writing style calibrated. The AI that knew your whole project now knows nothing, and you’re starting over.
The standard response is “just use Projects” or “paste the context back in.” That works for a document. It doesn’t work for six months of accumulated context across dozens of conversations. The export exists. Anthropic has the data. They will hand you a JSON file if you ask nicely. They just won’t let you use it.
The workaround
I ran into this myself switching accounts and built a fix: a local MCP server that makes the export actually useful.
The idea is simple. Claude exports your conversations as a JSON file. You run a small indexer that loads that file into a SQLite database with full-text search. Then you run an MCP server that exposes three tools Claude can call automatically:
search_history(query)— searches your old conversations and returns ranked results with snippetsget_conversation(uuid)— pulls the full thread for a specific conversationlist_conversations()— browse by date
Once it’s running and registered in Claude Desktop, you just talk normally. “What did we decide about the GTM strategy?” and Claude searches your old account data on its own, finds the relevant conversation, reads it, and answers. No copy-pasting. No manual context loading.
Setup is about five minutes if you have Python installed:
git clone https://github.com/sneg55/old-claude-mcp
pip install -r requirements.txt
python indexer.py ~/Downloads/conversations.json --db history.dbThen add it to your Claude Desktop config and restart. The whole thing is ~300 lines of Python with no external dependencies beyond the MCP SDK and SQLite (which is built into Python).
The search is keyword-based using SQLite FTS5 — fast, works offline, no API costs. It’s not perfect. Vague queries work less well than specific ones. But for the actual use case — “I remember discussing this, let me find it” — it works well enough to be genuinely useful.
What Anthropic should build instead
The workaround works. It shouldn’t need to exist.
Anthropic has the infrastructure to build account migration natively. Import a conversation export from another account. Merge histories. Let you bring your context when you change your email address or move from a personal account to a work one. The data is already there — they’re storing it, they’re exporting it on request. An import flow is not a hard engineering problem.
The harder problem is that right now the export feature exists to satisfy regulators, not users. The person losing their email account by January 31st is not the design consideration. That should change.
Until it does: the repo is here. It works with any Claude conversation export and takes about five minutes to set up. If you’re switching accounts or just want your old context available in new conversations, it’s the best option currently available.
Built this while switching Claude accounts mid-project. If you run into issues or want to add support for ChatGPT exports, PRs are open.
