N3 — Migration System ▾
ChatGPT → Claude
Migration System
You don't migrate chats. You migrate operational knowledge. Turn scattered conversations, prompts, decisions, and workflows into a structured system for working with Claude Code.
What you'll build
CLAUDE.md Personal context and working rules with Claude README.md Description of the ecosystem, active projects, and status /prompts Folder with prompts named by task, ready to copy /workflows Documented flows with steps, tools, and success criteria /docs Documentation of decisions, architectures, and processes backlog.md A list of automations prioritized by impact/effort Diagram — How you migrate from ChatGPT to Claude Code
Scattered chats and prompts
History in ChatGPT, notes, documents
Context extraction
What you know, how you work, which projects you have
Classification of projects and workflows
Active, paused, automatable
Conversion to CLAUDE.md + README + /prompts
Structured, reusable knowledge
Automation backlog
Tasks prioritized by impact and effort
An operational system in Claude Code
Ready to work with context from day 1
Complete Level 2 to unlock
The Migration System unlocks when you complete the Advanced Operator Playbook. This level assumes you already know how to operate Claude Code with professional judgment.
Go to Level 2 — Advanced Operator Playbook →Migration isn't copying and pasting conversations. It's extracting the knowledge that exists only in your chats and turning it into something Claude Code can use as a system.
Context
Who you are, how you work, what goals you have
Style
How you prefer Claude to communicate with you
Rules
What it should never do, what it should always avoid
Projects
Current status, next steps, dependencies
Prompts
The ones that already work, not the generic ones
Decisions
The important ones and their reasoning
Workflows
Repeated processes with defined steps
Memory
What you learned and isn't written down anywhere
ERROR COMÚN
Before migrating, you need to know what you have. Check off what already exists in your case:
Conversations
Projects
Knowledge
Before migrating a project, classify it. Its status defines what to do with it:
Active
You're working on it this week
Paused
You'll come back to it, but not now
Discarded
It's not going to happen. Close it with a note.
Automatable
Claude can run it with clear instructions
Delegable
Another operator can take it on with context
Educational
What you learned building it deserves to be documented
RECUERDA
Assess your current situation to identify your migration profile. There's nothing to calculate: read each row and decide your current level.
Active projects
Useful prompts saved
Repeated workflows per week
Current documentation
Urgency to automate
Light migration
Who it's for
Few variables at low or medium level
What to migrate first
Personal CLAUDE.md + /prompts folder with 5 templates
Estimated time
2–4 hours in one afternoon
Final deliverable
A minimal working system to operate with Claude Code
Operational migration
Who it's for
Most variables at medium level
What to migrate first
CLAUDE.md + /prompts + /workflows documented
Estimated time
1–2 days spread across a week
Final deliverable
An operational system with prompts, workflows, and migrated context
Full migration
Who it's for
Several variables at high level
What to migrate first
Full inventory → classification → migration project by project
Estimated time
1–2 weeks with daily sessions of 30–60 min
Final deliverable
A complete Claude Code ecosystem with a backlog of automations
Each type of migrated knowledge goes to a specific destination:
CLAUDE.md Personal context and working rules with Claude
README.md Description of the ecosystem, active projects, and status
/prompts Folder with prompts named by task, ready to copy
/workflows Documented flows with steps, tools, and success criteria
/docs Documentation of decisions, architectures, and processes
backlog.md A list of automations prioritized by impact/effort
Act as an archivist of operational knowledge. I have conversations or a work history with ChatGPT that I want to process. From this material: [paste relevant conversations or describe the main topics] Extract and structure: 1. Active projects mentioned (name, status, next step) 2. Prompts I used that produced good results 3. Important decisions made along with their reasoning 4. Work rules or personal preferences that emerge from the history 5. Repeated tasks that could be automated 6. Tacit knowledge that exists only in the conversations Format: Markdown. Organized by category. One line per item. No filler.
Act as an architect of operational context. I have this scattered material: [paste the material: notes, conversations, project descriptions] Turn all of this into a main CLAUDE.md that serves as the entry point for working with Claude Code on any project in my ecosystem. The file should include: - Who I am and what I do (3-5 lines, dense) - Active projects with current status - Tools I use regularly - My preferred way of working with AI - What I NEVER want Claude to do - Style and tone rules if applicable 50 lines max. Something I can add at the start of any session.
Act as a consultant for migrating working systems. I have these projects and resources: [list your active projects, key documents, and tools] Create a ChatGPT → Claude Code migration plan that includes: 1. Project prioritization (which to migrate first and why) 2. For each project: what to migrate, in what format, and what to create in Claude Code 3. A list of prompts to recover and how to turn them into /prompts files 4. Which workflows to document and in what format 5. Time estimates with tasks of 30 minutes max each Expected final result: a folder structure ready to operate with Claude Code.
We can migrate your system with you.
If you have knowledge scattered across ChatGPT, Notion, emails, or documents and want to turn it into an operational system with Claude Code, we do it together.
- — Organize your scattered knowledge into an operational system
- — Build a system of custom prompts for your workflow
- — Migrate workflows from ChatGPT to Claude Code with context
- — Build an internal portal of prompts and SOPs for your team
- — Set up Claude Code to collaborate with other operators
Complete these items before marking the level:
- ✓ Knowledge inventory completed (what you have and where)
- ✓ Projects classified by status with clear judgment
- ✓ Migration profile identified (light / operational / full)
- ✓ Personal CLAUDE.md created with migrated context
- ✓ /prompts folder with at least 5 of your own operational prompts
- ✓ At least 1 workflow documented in /workflows
- ✓ backlog.md with prioritized automations
- ✓ Ecosystem README.md updated
LEVEL 3 COMPLETED
MOONKEY LAB completed