Free tools Windows power users keep installed
One-click scans. No signup required.
Switching AI assistants usually moves some of your history, not the working environment you built inside the old one. A preference summary, a chat archive, or an imported memory can carry over. Project files, attachments, project-scoped memory, and the sense of picking up exactly where you left off often do not. The useful question is not “can I import my data?” but “which parts of my working setup does this particular transfer recreate?”
Why the working context feels scattered
An assistant’s working context is not stored in one place. It is spread across several layers: chat histories, saved memories, project spaces, uploaded files, and account settings. Each provider stores and scopes these layers differently, so a transfer tool can move one layer without touching the others.
As an Amazon Associate I earn from qualifying purchases.
Scope is the most common source of surprise. OpenAI describes ChatGPT project-only memory as excluding personal saved memories and chats outside the project, while chats inside the same project can reference one another. Anthropic describes separate memory spaces and summaries for Claude projects. Both designs help keep work focused inside a project, but they also mean that a project is its own layer. Moving your general profile does not move the project.
Google framed the problem from the user’s side when it announced Gemini memory and history import on March 26, 2026. The announcement described “starting over with an assistant that doesn’t know you” as daunting, and promised bringing memories and chat history “without starting over.” Those are vendor descriptions of the problem, not measurements of how many people experience it. Google’s announcement also states the principle behind the feature: “We believe that the most helpful AI assistant is one that’s personal to you, and understands your preferences and past conversations,” said Maryam Sanglaji, Group Product Manager, Gemini App.
#1 Best Overall
What each official transfer route moves
The routes below are the ones documented by the providers as of early October 2026. Rollout and limits change, so confirm them in the app before you follow a step-by-step process.
Gemini: preference summaries and ZIP chat history
Google documents two separate routes:
- Preference summary. You ask your current assistant to summarize what it knows about your preferences, then paste that summary into Gemini’s memory settings. Only what you paste arrives, so the quality of the summary sets the quality of the transfer.
- ZIP chat-history import. The ZIP file is the supported format, with a 5 GB limit. Chat text transfers, and imported histories appear as chats that you can search. Project files cannot be imported. Images and files generated in the other app are excluded. Google’s help page says the import can take up to a day to complete.
ChatGPT account-to-account: an uploaded export as reference
OpenAI documents a route in which you upload an exported conversation JSON file into a new conversation in another personal account. The file then serves as reference material for that conversation. It does not merge the two accounts and does not restore the old chats as chats. Settings, memories, GPTs, files, subscriptions, and workspace access do not transfer through this route.
ChatGPT desktop and Codex CLI: agent setup and recent work
OpenAI also documents an import route in the ChatGPT desktop app and in Codex CLI for selected setup and recent work from supported agents. Source eligibility differs by destination. The Codex CLI route imports up to 50 chats from the last 30 days. This is an import for agent setup and work, not a general method for moving consumer chatbot memory between providers.
Claude: memory import and export
Anthropic documents chat search, memory, and separate project memory and summaries. It also describes an experimental feature for importing and exporting memory between Claude and other AI services. Memory synthesis and chat summaries are included in standard conversation history exports. Anthropic’s documentation, as summarized here, does not establish that this feature recreates a full project from another provider, so do not assume it does.
How to judge any switch or import feature
When you compare a provider’s import or switch feature with another, check four things:
- What moves: a memory summary, chat text, project configuration, files, or attachments. Most routes move only one or two of these.
- How it appears afterward: a searchable imported archive, a reference attachment, or an editable recreated project. Only the last one restores a working space.
- Scope and limits: file format, size caps, rollout status, account type, and whether a source is eligible for your destination.
- Privacy and control: where the export is uploaded, whether imported chats can be deleted, and whether the feature can be turned off. Check each provider’s current settings, because the official pages reviewed here do not answer all of these questions for every route.
A handoff workflow that carries the working state
Because no single route recreates a project, the most reliable approach is to carry the working state yourself in a short document you control. This is practical workflow advice based on the transfer gaps above. It has not been tested as an interoperability standard.
- Ask your current assistant for a handoff. Request a concise summary with these headings: goal, current state, decisions already made, open questions, constraints, preferred output format, and the next action.
- Export useful chats where the service allows it. Keep the export file somewhere you control.
- Save project files and attachments separately. Archive imports may omit them, and Gemini’s ZIP route excludes project files entirely.
- Import through the destination’s documented route. Use the memory-summary route for preferences and the archive or export route for conversation text.
- Verify the destination. Ask the new assistant to restate the current state and the next step. Correct anything it has missing or wrong, and note which corrections you had to make.
- Keep the handoff document current. Store it outside any single provider so you can reuse it when you switch again.
Checks after you import
- Imported chats do not appear yet. Gemini’s import can take up to a day. Wait before repeating the import, since duplicate imports can clutter your history.
- Generated images or files are missing. This is expected on Gemini’s ZIP route, which excludes images and files generated in the other app.
- The project is absent. This is expected. No documented route recreates a project with its files, so rebuild the project from your handoff document and the files you saved separately.
- The new assistant describes your goals inaccurately. Correct it directly in the chat and, where the app allows it, in memory settings. Then update your handoff document.
- A chat from the old account is referenced, but not restored. This matches OpenAI’s account-to-account behavior. Treat the uploaded file as reference material.
What is and is not established
Official documentation and announcements establish what each provider says its transfer features do, along with several limits. They do not show how complete an imported context feels to real users, and no independent measurement of how common this frustration is has been cited here. Google’s March 26, 2026 announcement describes its rollout as starting that day, and Anthropic labels its memory import and export feature as experimental. Check current in-app availability before you rely on any route.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe most dependable statement you can make about any switch is narrow: a transfer can carry selected memories, chat text, or an archive. Recreating the working environment still requires you to rebuild the project, its files, and its current state.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
