Getting your data out

Two reasons to care before you need to. Portability, so a decision to move stays yours and does not belong to the switching cost. And the practical one: months of problem-solving in a chat history is work, and work you cannot retrieve is work you did for someone else's storage.

How it works

The steps are in Anthropic's export article: a settings page, a wait while it generates, and a link by email. Which surfaces and plans offer it is stated there and has moved before.

Two details from that article catch people out and belong in your head. The link expires 24 hours after delivery, and you must be signed in to use it. Miss the window and you repeat the process for a fresh one — no loss beyond the wait, but a surprise if you requested it on a Friday.

Out is not the same as in

The limit worth knowing before you plan around export: "Exported data can't be imported into another personal Claude account, and we don't support migrating data between personal accounts."

So export is portability away from the product. Portability between accounts of it is a different thing, and it is absent. Moving from a personal account you are closing to a new one, your history does not come with you.

One route does exist. Joining a Team or Enterprise organisation lets you migrate a personal account directly, without an export at all.

What to do with the file

Treat it as sensitive. It is every conversation you have had, which for most people is a more revealing document than anything else on their machine. Somewhere encrypted, and not a shared drive.

Then read some of it. An export is the only view of what you have actually put into the product over months, and it is a more honest audit than memory. People who do this generally find at least one conversation they would not have started had they thought about it — which is useful calibration for what goes in rather than a reason for regret.

Export is not deletion

Requesting a copy changes nothing about what is retained. Retention, the training toggle, and what deleting a conversation does are separate mechanisms covered in the training toggle and retention.

If your goal is to leave, both steps are needed and in that order: export first, because deletion is not reversible and support cannot reconstruct it.

Try this

Request one now, while nothing depends on it. You learn how long it takes for your account size, you confirm the email arrives at an address you still read, and you find out what the file actually contains before the day you need it.

What goes wrong

Requesting it during a deadline. There is a delay, the link lives 24 hours, and neither is under your control.

Assuming the history transfers. It does not, between personal accounts. Plans that depend on carrying conversations to a new account are built on something the documentation says is unsupported.

Leaving the file where the conversations were the sensitive part. The export concentrates everything into one artefact, so it deserves more care than any single conversation did.

Deleting first. Export, verify the file opens, then delete.

How to check it worked

Open the export and search it for a conversation you remember from months ago. If it is there with its content intact, you have a working copy and you know the process. If something you expected is missing, better to find that now than on the day you are relying on it.