Guide · Updated August 2026
Switch from Claude to Gemini without starting over
Gemini has no import feature for Claude data — nothing pulls your history in for you. The working path has three steps: export your data from Claude (Settings → Privacy → Export data; the download link arrives by email, usually within minutes), distill that history into one compact document, and hand it to Gemini somewhere it will actually persist — your personal context instructions for the essentials, a Gem for each project, Saved info for the rest. What transfers is the substance of your work: projects, preferences, decisions, people, and how you like answers written. What doesn't is Claude-specific plumbing — Projects need re-creating as Gems, published Artifacts stay behind unless you download them first, and the conversations themselves can't be ingested. This guide walks each step, maps where every Claude concept lives on the Gemini side, and ends with a practical suggestion: run both assistants for two weeks before you commit.
Step 1 — Export your Claude data
- In Claude, open Settings → Privacy.
- Click Export data and confirm.
- Anthropic emails you a download link — download the ZIP promptly.
Every export option, timing, and troubleshooting: full Claude export walkthrough →
Step 2 — What transfers, what doesn't
- Transfers as context: who you are, your projects and their state, preferences, standing instructions, people and companies, decisions, writing style.
- Needs manual rebuild: Project structure and knowledge files — re-create the important ones as Gems — and any Artifacts you want to keep (download them from Claude first).
- Doesn't transfer: the conversations themselves — Gemini can't ingest a chat archive.
Step 3 — Get your context into Gemini
A. Saved info & personal context Free · quick
Open Gemini's settings and look for Personal context — turn on "Your instructions for Gemini" and paste the essentials: who you are, what you work on, how you want answers written. You can also simply tell Gemini "remember this about me" in a chat; it lands in Saved info and applies across conversations.
B. Gems Free · durable
For each project that matters, create a Gem — Gemini's equivalent of a Project. Paste the project's context into the Gem's instructions and re-upload its files as knowledge. Every chat with that Gem then starts fully briefed.
C. Build the document from your full history Complete
Upload your Claude export ZIP as-is. Every conversation is analyzed and distilled into one Gemini-ready context document — the input that makes options A and B actually good.
Where each Claude thing lives in Gemini
| In Claude | Gemini equivalent |
|---|---|
| Profile preferences / “how to respond” | Personal context — "Your instructions for Gemini" in settings |
| A Project with instructions + knowledge | A Gem — paste the instructions, re-upload the files as knowledge |
| Memory (stored facts) | Saved info — ask Gemini to remember them |
| Artifacts | No direct equivalent — download them from Claude and re-upload where needed |
| Claude Code sessions | Separate world — they never leave your machine via the claude.ai export |
Run both for two weeks before you commit
Keep your Claude account alive during the transition. Before you cancel anything: your export ZIP is downloaded and stored, artifacts you care about are downloaded (they are not fully recoverable once the account is gone), and a week of real work has gone through Gemini without you reaching back for Claude — the only test that matters.
Frequently asked questions
Does Gemini have an import feature for Claude data?+
No. Nothing in Gemini ingests a Claude export directly. Your context comes in the way everything does: pasted into a chat, into your personal context instructions, or into a Gem's instructions.
Where exactly do I paste the document in Gemini?+
Three places: the "Your instructions for Gemini" field under Personal context in settings (the essentials), a Gem's instructions (per-project context), or the first message of a new conversation. Google renames these sections regularly, but personalization always lives in Gemini's settings.
Do my Claude Projects transfer to Gemini?+
Not automatically. Re-create the important ones as Gems: paste the instructions, re-upload the knowledge files. The accumulated understanding that lived in the conversations themselves is what the context document covers.
Is there a size limit on what Gemini can hold about me?+
The instructions field is meant for a couple of paragraphs, not a full document. Put the durable essentials there, give each Gem its own project context, and paste the complete document into a conversation when a session needs the full picture. If you have to cut, keep instructions over facts.
Can I switch back later without starting over again?+
Yes. The document is plain Markdown and assistant-agnostic — the same transfer works toward Claude, ChatGPT, or back to Claude. Once you treat your context as a portable document, no switch is permanent.
Coming from ChatGPT instead? · Claude → Grok · Claude → ChatGPT