ChatGPT to Claude

In ChatGPT: Settings → Data Controls → Export data. You'll get an email with a zip within 15 minutes containing:

conversations.json - every chat you've had.
chat.html - browsable version of all conversations.
model_comparisons.json - A/B testing data.
user.json - your profile and memory entries.

The export doesn't include your Custom GPTs as separate files - you'll need to copy their instructions manually from the GPT editor.

Open chat.html in a browser. Skim the list. Be honest: most people use ChatGPT for 3-5 repeatable tasks and the rest is one-off exploration.

Common patterns worth migrating:

Daily writing helper - editing, rewriting, tone shifts.
Code companion - debugging, explanation, scaffolding.
Research brief builder - summaries, comparison tables.
Meeting notes rewriter - raw transcript to clean doc.
Specific Custom GPTs - e.g. a brand voice checker, a SQL assistant.

Pick the top 3-5. Don't try to rebuild conversation history - you don't need it.

Go to claude.ai and create an account. Start on Free to kick the tires. Upgrade to Pro ($20/mo) when you're using it daily, or Max ($100/mo) if you're doing heavy Opus / 1M context work.

Install the desktop app (claude.ai/download) - it's dramatically faster than the web UI for daily work and adds global keyboard shortcut support.

For each Custom GPT worth keeping:

1. In ChatGPT: open the GPT editor, copy the Instructions verbatim.
2. In Claude: click New Project, give it a name, paste the instructions into Custom Instructions.
3. Upload any reference files (knowledge base docs) to the Project's Knowledge area.
4. Start a new chat in the Project. Test the same prompt you used in the GPT.

Projects in Claude don't have a store or public sharing by default. That's a feature for most people - you're not competing for discovery.

If you used ChatGPT's Custom Instructions ("How would you like ChatGPT to respond?"), copy them to Claude's equivalent:

Settings → Profile - there's a "Personal preferences" box that applies to all conversations. Paste your persona and style instructions here.

ChatGPT's memory feature has a rough Claude equivalent: Projects act as scoped memory. Claude doesn't auto-remember across conversations outside Projects by design.

Claude's strength as a daily driver comes from MCP (Model Context Protocol) connectors. In the desktop app:

Settings → Connectors - one-click installs for Google Drive, GitHub, Linear, Gmail, Slack, and more.

Unlike ChatGPT plugins (mostly abandoned), MCP connectors are maintained, open-source, and work well. If you use ChatGPT with GitHub or Drive, this matters a lot.

# Popular MCP connectors
- Google Drive - chat with your docs
- GitHub - read repos, create issues
- Slack - read channels, send messages
- Gmail - summarize, draft replies
- Linear - triage issues

Claude responds to structured prompts better than ChatGPT does. Translate your go-to prompts:

<!-- ChatGPT-style -->
You are an expert copywriter. Rewrite this for a B2B SaaS
audience. Make it punchier. Here's the text: ...

<!-- Claude-style -->
<role>Senior B2B SaaS copywriter</role>
<task>Rewrite the text below for a busy exec reader.
Cut filler. Keep claims concrete.</task>
<input>{your text}</input>

XML tags aren't required but Claude scores much higher on following instructions when they're present. For your top 5 repeat prompts, convert them to this style once and save them in a Claude Project.

Don't cancel ChatGPT day one. Run both for a billing cycle. Every time you reach for ChatGPT, also run the task in Claude and compare outputs.

After 7 days, you'll know which wins on your actual work. For most people: Claude wins on code, long documents, and careful reasoning. ChatGPT sometimes wins on image generation and voice.

Cancel whichever loses. Some power users keep both ($40/mo total) and route by task type - that's fine too, just don't forget this guide is on a site called Fewer Tools.