How to Switch From ChatGPT to Claude: Memory and Projects

To switch from ChatGPT to Claude, collect the context you rely on, review any memory text you want to import, then rebuild one project with its instructions and source files. Claude has an experimental memory-import feature. It does not recreate your ChatGPT workspace or load your account export as working chat history.

Keep an archive where your account permits it. Check the rebuilt setup on a representative task before depending on it or adding tool connections.

Capability notes checked on 11 October 2026.

I used ChatGPT as my default AI for two years. My setup included Custom GPTs, memory and saved prompts. When I moved most of my daily work to Claude, losing that setup was the part I dreaded.

Quick workflow: move one useful project first

1. List the instructions, decisions, examples and files that the project needs.
2. Request an account export if eligible, and keep the original source documents.
3. Review a short memory summary, then use Claude's memory-import option if available.
4. Create a Claude Project and add the relevant instructions and approved files.
5. Test one familiar task. Fix omissions before connecting other tools.

Keep ChatGPT available until you have checked the work you intend to move.

Make a context inventory before exporting

Start with work you will actually do next week. Fill in this worksheet for one project:

A summary generated from an old conversation may omit a decision or preserve an outdated one. Check it against the original records before treating it as current context.

Leave out credentials, API keys, private URLs and unnecessary personal information. Use redacted examples for the first test. Only move customer records, contracts or private correspondence when you have permission and the destination meets your requirements.

Export ChatGPT data as an archive

Eligible accounts can request an export under Settings > Data controls > Export data. The ZIP includes chat history and other account data. It can take up to seven days, and the download link expires after 24 hours. OpenAI's export instructions

Self-service exports are unavailable in ChatGPT Business, Enterprise and Healthcare workspaces. Ask your workspace owner about the approved process. Do not bypass workspace restrictions.

Keep the export as an archive. Check it against your inventory rather than assuming every Project asset or saved-memory entry is included. Collect original files and editable instructions separately.

How to import reviewed memory into Claude

Anthropic documents this path in the newer interface: Settings > Memory > Start import. Paste the text you have reviewed, select Add to memory, then inspect the resulting entries. Accounts using the legacy interface should follow the Settings > Capabilities instructions in the same help page. Claude's memory import and export guide

The import is experimental, focuses on work-related context and may omit information. Check what was added. Follow the documented availability for your account rather than assuming every plan has the same controls.

You can ask ChatGPT for a short starting summary:

Summarize my current work, output preferences and ongoing projects for me to review. Mark uncertainty and exclude sensitive details.

That response is a suggested summary, not an exhaustive memory export. Compare it with the saved-memory interface and your original records. Remove obsolete or sensitive information before copying it across. Keep project-specific documents separate from a general profile.

Rebuild instructions and files in a Claude Project

Claude Projects support uploaded reference material and project instructions. Use those features to rebuild the work context you need. Anthropic's Projects guide

For a Custom GPT you own, collect the instructions you can access and the original reference files. Create a Project, rewrite provider-specific instructions where needed, then upload only the approved material relevant to that project.

A Project does not establish a one-to-one recreation of a Custom GPT. Review any actions, tools and sharing requirements separately. Do the same with saved prompts: try them on the actual task before assuming their behavior will carry over.

For a broader explanation of arranging knowledge, decisions and workflows, see the AI second brain guide. If your destination is Claude Code rather than a chat Project, use the Claude Code guide for knowledge workers for that separate setup.

What does not transfer automatically?

Keep these boundaries in your migration notes:

• An account archive does not become Claude chat history simply because you download or upload it.
• A reviewed memory import can leave gaps and does not recreate files or project instructions.
• Provider-specific tools, actions and sharing behavior need their own checks.
• Connections and permissions need separate configuration. Importing memory does not connect your ChatGPT account to Claude.

Keep a short list of missing material and unsupported actions. If a task still needs the original setup, leave that task there until you have a verified replacement.

Test the rebuilt setup before connecting tools

Choose a task with an answer you can assess, such as a project update from two redacted documents and a dated decision note.

Use this acceptance checklist:

• The answer reflects the current project goal and decision.
• Factual claims can be checked against the supplied documents.
• Missing information is identified rather than filled in.
• The output follows the instructions and example you provided.
• Any proposed external action stays within your stated permissions.

Record what failed and the context needed to correct it. Repeat the same task after the correction. Add a connection only when that task genuinely needs access to another system, and configure its permissions separately.

Afterward, the Second Brain Health Check can help you review the setup. If you want a structured starting point beyond this migration, Second Brain is an optional setup route. Neither replaces the checks above.

FAQ

Can I transfer all my ChatGPT history to Claude?

An export gives you an archive. These instructions do not document importing it as complete Claude chat history. Select useful material and rebuild the workspace.

Can I transfer ChatGPT memory to Claude?

You can review memory text and use Claude's documented import feature where available. It may omit entries. Compare the result with your inventory before relying on it.

Is a Claude Project the same as a Custom GPT?

A Project can hold instructions and reference material. That does not prove equivalent tools, actions or distribution. Check the requirements of the specific GPT you are rebuilding.

Can I connect ChatGPT to Claude instead of migrating?

The export and memory-import procedures above are data-transfer steps. They do not establish a live connection between the accounts.

Do I need to move everything at once?

Start with one project and one representative task. Keep the original material available until the rebuilt setup passes your checks.