Can you import a Claude data export into a new account?

No. Anthropic lets you request and download your full conversation history as a JSON ZIP, but there is no import flow, so you can't bring that data anywhere. The post frames this as a product decision rather than a technical limitation, since the export exists primarily to satisfy regulators rather than users losing access to an account.

How does the local MCP workaround for Claude exports work?

You run a small indexer that loads the export JSON into a SQLite database with FTS5 full-text search, then run a local MCP server exposing three tools: search_history, get_conversation, and list_conversations. Once registered in Claude Desktop, you talk normally and Claude searches your old account data on its own. The whole thing is about 300 lines of Python with no dependencies beyond the MCP SDK and SQLite, and setup takes about five minutes.

What are the limits of the keyword-search approach?

Search is keyword-based using SQLite FTS5, so it is fast, works offline, and has no API costs, but it is not perfect. Vague queries work less well than specific ones. For the core use case of remembering you discussed something and wanting to find it, it works well enough to be genuinely useful.

Why is my Claude data export not working?

The usual causes are starting the export from the iOS or Android app, which cannot do it, checking the wrong inbox, or using a download link that is more than 24 hours old or has already been used once. Start the export again from the web app or Claude Desktop under Settings, then Privacy, then Export data, check spam, and make sure you are signed in to the account that requested it when you click the link. On a Team or Enterprise plan the Export data button only appears once an owner turns on the setting that lets members export their own data.

What does "We could not find this link" mean on a Claude export?

It means the browser that opened the download link is not signed in to the account that requested the export, or the link is no longer valid. Anthropic says the link requires you to be signed in, expires 24 hours after it is created, and may work only once. Sign in to claude.ai with the requesting account in the same browser, then click the link again. If it still fails, run the export again to get a fresh link.

Claude lets you export your data but won't let you use it

Q: Can you move a Claude Project to another account?

Not directly. Anthropic documents no way to transfer a Project between personal accounts, and its help center says migrating data between personal accounts isn't supported. Sharing works only inside a Team or Enterprise organization. For a personal-to-personal move, copy the project instructions, re-upload the knowledge files from your originals, and carry over key chats by hand or through the local MCP server.

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.

Can you move a Claude Project to another account?

Not in one step. Anthropic’s help center says an exported file can’t be loaded into another personal Claude account, and migrating data between personal accounts isn’t supported. Project sharing exists, but only on Team and Enterprise plans, where you can give colleagues “Can view” or “Can edit” access. That page describes sharing, not transferring ownership, and I could not find anything in the docs saying a Project can be handed to a different account.

There is one documented exception. If you are joining a Team or Enterprise organization, you can bring your personal account’s data with you. Anthropic lists chats, projects with their instructions and files, uploaded files and memory as carrying over. It is one-way, and it does not help if you are moving between two personal accounts.

For the personal-to-personal case, you rebuild the Project by hand. Here is what the export gives you and what you carry yourself:

Item	In the export?	What to do
Conversations	Yes. The help center says the export includes “conversation data and the user data for your account”	Keep the ZIP. Index it if you want it searchable
Projects and project instructions	The help center article does not list them. Anthropic’s Claude Desktop import docs say an export contains your projects, and that imported projects keep their custom instructions	Copy the instructions out of the Project settings anyway. It removes the doubt
Project knowledge files	No. The same docs say a member’s own export never includes the contents of files uploaded to a project’s knowledge	Re-upload from the originals, or download them from the Project before you lose access
Chat attachments	No, same rule	Same fix
Memory	The Desktop docs say the export includes it. Memory also has its own import and export	Export it from Settings, then paste it into the new account

The practical sequence:

In the old account, open the Project and copy the instructions into a text file.
Download every knowledge file you do not already have elsewhere.
Pick the handful of chats that hold real decisions and save them. The export has them, but a summary pasted into the new Project’s knowledge is more reliable than hoping search finds the right thread.
Create the Project in the new account, paste the instructions, upload the files.
For everything else, point the local MCP server below at the export and let Claude search it on demand.

Memory is the one thing with an import path. Claude now has a memory import, available on Free, Pro, Max and Team plans on the web and Claude Desktop. The help center calls it experimental, and it takes memory entries, not conversation history. It carries what Claude knows about you, not your projects or chats.

What do you do when the Claude export is not working?

Start with the boring causes, because they are the ones the help center documents. Exports can only be started from the web app or Claude Desktop. The iOS and Android apps cannot do it. The path is your initials in the lower-left corner, then Settings, then Privacy, then Export data.

After that, the file arrives as an email link, not a download in the page. Anthropic says there may be a small delay while it is generated, the email goes to the address tied to your account, and you must be signed in to use the link. The help center also says the link “will expire 24 hours after it’s created, and it may work only once,” so download the file as soon as the email lands. If it lapses, you run the export again to get a fresh one.

“We could not find this link”

The full message asks you to make sure you are logged in with the account that requested the link. It shows up when the browser that opens the email link is signed in to a different Claude account, or to none, and when the link is past its 24 hours or has already been used. Sign in to claude.ai with the account that asked for the export, in the same browser, and click the link from the email again. If that still fails, the link is spent: request a new export.

“Your export should begin downloading automatically,” and you get a tiny JSON file

A user on note.com described this in September 2026: the download page saved a single JSON file of 1 to 2KB. It was a manifest, not the data. It listed separate links for conversations, projects, memories, feedback and light metadata, with a note that each link can be used only once. Clicking each link in turn downloaded the actual ZIP files. Anthropic’s Claude Desktop import docs are consistent with this: they say an export can come as more than one .zip file. Open the manifest in a text editor, use each link once, and keep every ZIP.

The help center has no article on an export email that never shows up. The closest guidance is in the login troubleshooting article, which is about login emails: check spam and junk for mail from @mail.anthropic.com, allowlist that domain, and ask IT if you are on a business, government or .edu address that filters aggressively. I would apply the same checks here, but that article does not say it covers exports, so treat it as a reasonable guess.

Watch for these account-type traps:

Team and Enterprise. Members can export their own chats only after an Owner or Primary Owner turns on “Allow members to export their own data” under Organization settings, then Data and privacy. If you don’t see the Export data button, that setting is off. Primary Owners don’t get the personal button at all and export the whole organization instead. Messages, files and projects deleted before an export starts are left out.
Wrong inbox. If you signed in with a different address than you remember, the link went there.

If you have done all of that and nothing arrives, request the export once more and then contact Anthropic support. I have not found a documented cause beyond these.

What can you do with a Claude export?

Anthropic is explicit that the file can’t be imported into another personal Claude account. That leaves three uses.

Keep it as an archive. The conversations are JSON. They are readable in any text editor, just not pleasant to read.
Import it into Claude Desktop on your company’s own model provider. Anthropic’s import wizard “brings a copy of your claude.ai conversations and projects” into Claude Desktop running in third-party mode, against an organization’s own inference provider. It is off by default and an admin has to enable it. Chats and projects come over, but project knowledge files and conversation attachments do not. This is for companies, not for someone moving between two personal accounts.
Make it searchable from Claude. That is the workaround below.

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 snippets
get_conversation(uuid) — pulls the full thread for a specific conversation
list_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.db

Then 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.