A usable record needs the exchange you intend to keep. If that exchange depends on an uploaded spreadsheet, keep track of the spreadsheet separately too.
Choose the export route for your account
Anthropic's export instructions, checked October 24, 2026, give these paths:
| Account or role | Where to start |
|---|---|
| Individual Free, Pro or Max | Settings > Privacy > Export data on web or Desktop |
| Team or Enterprise member | Same route, after an Owner enables member exports |
| Team or Enterprise Primary Owner | Organization settings > Data and privacy, for the organization export |
| Using iOS or Android | Open the web app or Desktop to request the export |
For a missing member button, ask an Owner whether Allow members to export their own data is enabled. A Primary Owner uses the organization route instead of looking for a personal button. That route has a broader scope; follow your organization's process for handling the result.
Before making a request, confirm which account contains the conversation. Having a personal Claude account and an organization account makes this worth checking explicitly. Open the required conversation and note its actual title and one recognizable phrase.
Keep track of what the record must contain
Suppose a project coordinator needs to preserve a permitted discussion before handing the work to a colleague. In this fictional example, the conversation explains why the team excluded canceled orders from a comparison. The original order spreadsheet remains in the team's approved storage.
The coordinator needs two related records:
| Record | What to inspect |
|---|---|
| Conversation | The question, exclusion decision, and reasoning around it |
| Source spreadsheet | The actual version used, including the canceled-order flag |
Anthropic says Team and Enterprise member exports include the member's chats but exclude the contents of uploaded files. Finding the discussion therefore does not establish that the spreadsheet is in the export. Member export contents
Write down the source file's real location and version while you still have access. Do not invent a missing file from the conversation's summary. If the source belongs to another team, use the organization's normal handover route.
Request and download the data
Select Export data in the appropriate settings. Anthropic emails a download link when processing finishes. The link expires 24 hours after delivery; an expired link requires a new request. You must be signed in to download it. Download conditions
Record the account, request date, and destination for the permitted record. Keep the delivered download intact while inspecting a working copy. Use software appropriate to the formats actually supplied; do not rename an unfamiliar file extension to make it appear readable.
Find the title or distinctive phrase you noted earlier. Read the exchange around it. For the canceled-order example, check that the retained discussion explains which orders were excluded and why. A single final answer may omit the question that gave the rule its meaning.
If the conversation is absent, first recheck the account and export scope. Keep that gap visible in the handover rather than treating a successful download as proof of completeness.
Decide whether you need an archive or a reusable result
An account export preserves conversation data. For a finished generated HTML page, saving a Claude artifact is a separate task: keep the actual page file and the information needed to reuse it. The right handover may require both the final result and its relevant reasoning.
Exported data cannot be imported into another personal Claude account. Anthropic provides a separate path for moving a personal account into a Team or Enterprise organization. Export and migration boundary
Finish the coordinator's handover with a checked conversation record, the source spreadsheet's maintained location, and any missing material identified. The next person should be able to inspect the exclusion decision without guessing which file produced it.