Free tools Windows power users keep installed
One-click scans. No signup required.
You can move useful preferences and context from Gemini into Claude using Claude’s memory import, but it is not a full chat-history or Gem transfer. To keep your workflows, save each Gem’s instructions and knowledge files separately, import only the memory you want Claude to retain, then rebuild and test each workflow in Claude.
What transfers—and what you need to rebuild
Think of a Gemini setup as several different kinds of information, not one portable package. Claude’s documented import transfers selected memory and context through text you provide. It does not import a Gemini archive or automatically convert Gem definitions.
| Gemini item | What to do when moving to Claude |
|---|---|
| Preferences and useful personal or project context | Ask Gemini to assemble the context you want to keep, review it, and paste it into Claude’s memory import. |
| Saved prompts or Gem instructions | Copy the exact text and rebuild the workflow in a suitable Claude feature. |
| Knowledge files | Save and organize the original files separately, then add relevant material to the rebuilt workflow. |
| Full Gemini conversations | Claude’s documented memory import does not describe importing complete conversations. Preserve any conversations you need separately. |
Google describes Gems as repeatable instructions and allows custom Gems to include knowledge files. Copying the instruction text alone therefore may not preserve everything a Gem depends on. See Google’s instructions for using Gems.
1. Inventory your Gems and recurring prompts
Before changing tools, make a separate record for each workflow. In Gemini, open each relevant Gem and copy its title and instructions. Capture recurring prompts that are not saved as Gems, too.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Write down the task the workflow is meant to perform and its required output format.
- Save useful examples or test inputs, including an edge case.
- List every knowledge file and keep a separate copy of each source file.
- Note any Google Workspace connection, other tool dependency, or Gemini-specific behavior the workflow expects.
This inventory gives you a specification to rebuild and check. Do not assume that a prompt will behave identically in Claude or that a connected service will be available there.
2. Prepare the memory you want to import
Anthropic’s memory-import instructions recommend asking your existing AI to collect saved memories and useful context into one copyable block. You can ask Gemini to include response preferences, relevant personal details, current projects, tools, and other context you want Claude to know, preserving original wording where possible. The suggested export is a starting point, not something you must transfer wholesale.
Rank #2
Review the text before moving on. Remove details that are sensitive, outdated, or irrelevant, and correct anything Gemini has summarized inaccurately. The import text may contain personal or work information, so treat it as data you are choosing to share with Claude.
3. Import the text into Claude
- In Claude on the web or Claude Desktop, open Settings > Memory.
- Select Start import, then paste the reviewed text.
- Submit it with Add to memory.
- Review the individual memory entries Claude extracts. Edit or remove entries that are wrong, incomplete, or no longer useful.
Anthropic’s help article says memory import is available on Free, Pro, Max, and Team plans on Claude web and Desktop. The current flow appears under Settings > Memory; some Team and Enterprise organizations may still see the legacy memory experience under Settings > Capabilities. Follow the labels shown in your account. Details are in Anthropic’s memory import and export guide.
4. Rebuild each workflow in Claude
Use the inventory as a small design brief for each replacement. Put the saved instructions into the Claude feature that best fits the job, add the relevant reference files, and adapt any assumptions tied to Gemini or Google services. This is a manual rebuild; the official guidance reviewed does not describe an automatic Gem-to-Claude converter.
Keep the original instructions unchanged in your offline copy while you iterate. Test the replacement with a typical request and an edge case, then compare its output with the result you need. Check the required structure, tone, source handling, and any expected tool actions. Revise the Claude instructions where the differences matter.
5. Keep a rollback copy until the replacements work
Retain your saved prompts, Gem instructions, and reference files until you have verified the Claude versions against representative tasks. This gives you a way to recover missing details or continue using the original workflow while you refine its replacement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Do not mistake Google’s reverse import for a Gemini-to-Claude tool
Google also documents importing from other AI platforms into Gemini, including a Claude export path. That feature moves information in the opposite direction and is not evidence of a Gemini importer in Claude. Google’s help page says its Gemini import requires a personal Google account and age 18 or older, and is unavailable in the EEA, Switzerland, and the UK, as well as in certain Gemini surfaces. See Google’s guidance on importing from other AI platforms to Gemini.
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.
