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

Claude API Rate Limits: Timezone Windows, Context Management, and MCP Overhead
Analysis of Claude API rate limits reveals tighter restrictions during peak hours (5am-11am PT / 8am-2pm ET weekdays), with context management and MCP server usage significantly impacting token consumption. Practical strategies include working outside peak windows, starting fresh conversations for new tasks, and auditing MCP integrations.

V100 SXM2 NVLink Homelab Guide: Building 64GB Unified VRAM for ~$1,100
A comprehensive guide details how to build a V100 SXM2 homelab with 64GB of NVLink-unified VRAM for approximately $1,100 using reverse-engineered Chinese hardware, covering hardware sourcing, performance estimates, and software compatibility.

Fix for sub-agents not showing up in OpenClaw v2026.3.13
A workaround for OpenClaw v2026.3.13 where custom sub-agents don't appear in the agent list: simplify the openclaw.json agent list to only include IDs and manually register agents in runs.json with status set to 'idle'.

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.