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

A Management Framework for Leading AI Agents Effectively
A former backend lead identifies a plateau in AI agent productivity and proposes a framework based on three disciplines: cybernetics, information theory, and management. The framework details two operational modes: the Captain and the Architect.

Mastering Backup: Safeguarding Your OpenClaw Agent
In an era dominated by automation and AI, ensuring the safety of your OpenClaw agent through robust backup strategies is paramount. Learn the essential steps to secure your digital assistant.

OpenClaw setup tips from a user's experience: Gmail MCP, profile flags, and networking issues
A user running OpenClaw on a Mac via UTM with Ubuntu VM shares specific configuration issues encountered: the Gmail MCP server requires html_body instead of body parameter, the --profile prod flag is needed to avoid a hardcoded dev identity, and API keys must be placed in auth-profiles.json via paste-token command.

OpenClaw Pre-Launch Checklist for Security and Reliability
A Reddit user shares a practical six-point checklist for OpenClaw setup before going live, covering access control, safety rules, memory management, automation testing, delivery validation, and failure handling.