Skip to content

Switching from ChatGPT

Last verified: 13 February 2026 | Applies to: All plans

If you’re coming from ChatGPT, Claude will feel familiar in chat but different in architecture. ChatGPT has GPTs and a plugin store; Claude has Skills, Plugins, Cowork, and MCP Connectors. This guide maps the concepts, highlights the differences, and helps you migrate your workflows.

ChatGPTClaudeNotes
ChatChatSimilar — conversational interface with the AI
GPTs (custom)Skills + PluginsClaude separates knowledge (skills) from bundles (plugins). Skills work on Free; plugins need Cowork.
Plugin storeclaude.com/plugins + claude.com/connectorsSeparate directories for plugins and tool connections
Code InterpreterCode tab / CoworkClaude can run code in Chat (artifacts) and in Cowork (full file access)
Browse with BingCowork web browsing + Chrome extensionCowork browses autonomously; Chrome extension interacts with specific pages
Custom instructionsCLAUDE.md + SkillsFolder-level or global instructions that persist across sessions
MemoryProductivity plugin + CLAUDE.mdMore structured — explicit memory files you can read and edit
DALL-EClaude doesn’t generate images (as of Feb 2026)
Voice modeClaude Desktop doesn’t have voice input (as of Feb 2026)

List the GPTs and custom instructions you use in ChatGPT. For each, identify whether the equivalent in Claude is a skill, a plugin, or a connector.

Follow Your First 30 Minutes — enable skills, connect a tool, install the Productivity plugin.

If you have custom instructions in ChatGPT, create a CLAUDE.md file or custom skill with the equivalent instructions. See Skills.

Run your most important 3-5 workflows in Claude. Compare the output quality. Adjust prompts as needed — Claude and ChatGPT respond differently to the same prompts.

Give it a full week. Some things will feel better immediately; others need adjustment. The Cowork + plugin architecture takes a few days to appreciate.


Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.