Skip to main content
SERVICE

How do I move from ChatGPT to Claude, or set up Claude for a small team?

About a week if you have an existing GPT setup. Skills replace your prompts, CLAUDE.md holds your operating context, Cowork projects replace ad-hoc chats. Workshop-first so the team ships in the first session.

Moving from ChatGPT to Claude takes about a week if you have an existing GPT setup. You migrate prompts to reusable Skills, drop your operating context into CLAUDE.md, connect Drive, and replace ad-hoc chats with Cowork projects. A small team can be productive within the first session if you do it workshop-first.

The three questions Mapi asked back-to-back

Mapi, who runs a nonprofit consulting practice with one VA in Colombia, asked me three questions back-to-back when she saw the setup. "Esto que me mostras vive en ChatGPT. Es facil despues hacer la transicion. Cuanto te tomo la transicion."

She had six custom GPTs that had stopped working well. "Llegaba a conversaciones muy largas y empiezan a inventarse cosas." Frangela, a solopreneur psychologist, made the move a month before our first call.

The pattern is universal in 2026: ChatGPT users are looking at Claude, and the migration question is the entry point.

WHAT CHANGES

What actually changes when you move

ChatGPT custom GPTs are isolated. Each one has its own instructions, its own files, and no awareness of the others.

Claude Cowork uses three primitives that solve that. Skills are reusable instruction sets that can be invoked from any conversation. CLAUDE.md is a single operating file that holds your business context, your voice, your rules, and is read by Claude every time you start a new session. Cowork projects are persistent workspaces with their own files and memory, and they can pull from shared Skills. See how the AI Operating System works for the architecture in detail.

ONE WEEK

The one-week migration

The migration takes about a week if you have an existing GPT setup.

Day one and two: I read your existing prompts and identify which ones become Skills versus which ones become entries inside CLAUDE.md. Day three and four: I install Drive sync, set up the Cowork projects, install the Skills, and write the first version of your operating file. Day five: 90-minute hands-on workshop with the team where each person ships one Skill tied to a real task.

Mapi's nonprofit migration in one week ran 2 hours 47 minutes in the workshop because we troubleshot Drive sync on her VA's Windows machine. She walked out with six Skills installed and the operating file connected. That is the workshop-first adoption method in practice.

PER-SEAT COST

Per-seat cost

Per-seat cost is the question Mapi asked next. "Si me toca lo mismo para Ivon y para Cata."

For a team of two-to-five, Claude Team at roughly $30 per user per month is the right plan. For a single power user moving from a $20-per-month ChatGPT seat, the Pro plan covers it. The bigger cost is the time to set it up well, which is why most teams hire someone to do the migration once instead of figuring it out over six months. See what a Claude Cowork training engagement costs for the engagement tiers, and the privacy posture on Team and Enterprise plans for regulated firms.

WHO THIS IS FOR

Who this is for

If you are running multiple GPTs that have stopped working as well as they used to, the migration solves that. Send me the list of GPTs you actually use weekly and I will tell you what becomes a Skill and what becomes an entry in CLAUDE.md.

Migration Questions

Frequently Asked Questions

Yes if you have an existing GPT setup. About a week. Day one and two: read your existing prompts and decide which become Skills versus entries inside CLAUDE.md. Day three and four: install Drive sync, set up Cowork projects, install the Skills, write the first version of your operating file. Day five: 90-minute hands-on workshop with the team.

About a week of focused work. Mapi's session ran 2 hours 47 minutes in the workshop because we troubleshot Drive sync on her VA's Windows machine, but she walked out with six Skills installed and the operating file connected. The migration is mostly the operating file and the Skills inventory; the workshop is what makes it stick.

No, it lives in Claude Cowork. ChatGPT custom GPTs are isolated, each with its own instructions and files, no awareness of the others. Claude Cowork uses Skills, CLAUDE.md, and Cowork projects which compose together. A Skill invoked from any conversation, an operating file Claude reads on every session, and a persistent workspace that holds your files.

Three primitives. Skills are reusable instruction sets invoked from any Claude conversation. CLAUDE.md is a single operating file holding your business context, voice, and rules, read by Claude every time you start a session. Cowork projects are persistent workspaces with their own files and memory, and they can pull from shared Skills.

ChatGPT GPTs are isolated. Claude composes. If you are running multiple GPTs that have stopped working as well as they used to (Mapi said hers "empiezan a inventarse cosas" on long conversations), the migration solves that. Per-seat cost is roughly $30 per user per month on Claude Team for a 2 to 5 person team.

Send me the list of GPTs you actually use weekly and I will tell you what becomes a Skill and what becomes an entry in CLAUDE.md. Book a 30-minute call.

You will get a real mapping of your existing setup before we discuss the migration.