How to Import Your ChatGPT History Into Claude Using Projects

If you're moving from ChatGPT to Claude and dreading the cold-start problem — no access to past context, project history, or your customized interaction style — there is a workable solution. One Reddit user posted a pragmatic two-step workflow that uses Claude's native Projects feature to carry over context from ChatGPT conversations.
Step 1: Export ChatGPT History as Markdown
Use a browser extension to select all your ChatGPT chats and export them as individual Markdown files (one .md per chat). Raw JSON dumps won't work for the next step; Markdown keeps files clean and readable. You'll end up with a folder of portable, local history.
Step 2: Load Key Chats Into a Claude Project
Claude Projects allow you to upload files as knowledge that the model reads before answering. Do not dump all 800 chats — be selective. Pick the conversations that carry active context: ongoing projects, reference material, chats where you defined how you like things done. Drop those .md files into a Project. Now Claude reads your ChatGPT history and continues from it instead of starting from zero.
Step 3: Archive the Rest Locally
Keep the entire exported folder in a notes app, Obsidian, or a regular folder. It stays searchable and backed up after you stop using ChatGPT.
Optional: Create a Context Brief
For long, messy threads, paste the conversation into Claude and ask it to compress it into a short brief: key decisions, current state, open questions. A 3,000-message thread becomes a half-page Claude can use instantly.
Caveats
- Claude Projects have file and size limits — be selective.
- This brings over context for Claude to read, not a literal recreation of your chat list.
- For resuming work, giving Claude your history to read is what matters.
📖 Read the full source: r/ClaudeAI
👀 See Also

Vibe Coding Rules: Build Side Projects from Your Phone Using Claude Code Without Reading Code
A senior engineer shares their rules for building side projects entirely from a phone using Claude Code without reading code: start in plan mode, commit to git, write tests, use subagents for reviews, and auto-mode.

Using AI to Write Better Code More Slowly: A Bug-Finding Workflow
Nolan Lawson describes a workflow using multiple AI agents (Claude, Codex, Cursor Bugbot) to find and prioritize bugs in PRs, improving code quality over raw velocity.

NemoClaw Windows Setup Issues and Fixes
NemoClaw installations on Windows fail with three specific errors: unsupported environment on Git Bash, port 18789 already in use, and Docker build failing on OpenClaw install. The root cause is that NemoClaw wasn't built with Windows in mind, requiring WSL2 Ubuntu for successful setup.

iOS Developer Shares Claude Code Best Practices After Shipping Multiple Apps
An iOS developer with cybersecurity background outlines specific practices for using Claude Code effectively, including environment separation, observability setup, and avoiding technical debt accumulation.