The review matters when an old assistant knows both your current work and a project you finished months ago. Importing everything can bring yesterday's instructions into tomorrow's task.
Choose the context that still belongs to your work
Consider this fictional move. A freelance editor wants Claude to know that client proposals need plain language and that unfamiliar abbreviations should be spelled out. Their old context also mentions an expired September deadline and a former client's confidential launch plan.
The writing preferences can be useful across tasks. The deadline has expired. The launch plan needs to remain in its approved location. Review the exported text yourself; a request to exclude confidential information is an instruction to inspect, not proof that the output is safe to transfer.
You can ask the previous service for a narrower starting list:
Prepare context I can review before moving to another AI service.
List my reusable work preferences and current tools separately
from project-specific facts. Include a date when one is known.
Exclude client identities, private contact details, confidential
source material, credentials and expired deadlines. Do not infer
new facts about me. Mark anything whose current accuracy is uncertain.
Do not send this information anywhere or claim it is a complete
account export. I will inspect and select the entries myself.
This is an authored request, not a native export command or a guarantee that another service can retrieve every stored detail. Keep only entries you recognize and still want used.
Use the import route your account displays
The current flow is available on the web and Claude Desktop across plans. In the new experience, use Settings > Memory. Some Team and Enterprise organizations retain the legacy Settings > Capabilities memory interface. Follow the section for the interface you actually see. Current and legacy import flows
Paste your reviewed text and import it. Then inspect the resulting memory entries. Anthropic describes import as experimental, so success should be judged from what appeared in memory and the next task, rather than an acknowledgment alone.
For the editor, check that “spell out unfamiliar abbreviations” survived and that the old deadline did not. If a preferred tool is missing, add the accurate preference directly rather than importing the entire old history again.
Test the imported context with a small new task
Start a new conversation and ask for a short proposal paragraph using fictional facts. Include an abbreviation you can recognize. Read whether the answer explains it and whether the wording fits the preference you imported.
If Claude mentions the former client or old deadline, inspect the imported entries and correct the specific material. Do not treat a good paragraph as proof that every entry is accurate; the test covers the context it actually used.
For ongoing project sources and analysis rules, Claude Projects provides a separate place to organize that work. Reusable memory should not become the only copy of a source document.
Keep the original records separately
Save your reviewed transfer text with a date so you know what you supplied. Preserve any old conversations you need through the original service's actual export process. Exporting Claude conversations is a different task from moving selected memory.
Finish the move when the entries are accurate and a new task uses the intended context. You do not need to carry over an obsolete project to retain a useful writing preference.