There is no official way to move ChatGPT memory into Claude, because neither company wants your context to travel. There are two real paths: the manual paste, which works today and goes stale tomorrow, and a portable file that was built to move.
In ChatGPT, ask: "Write a compact profile of me from your memory: how I work, what I am working on, how I like answers." Copy the result. In Claude, open a Project and paste it into the project instructions, or simply make it your first message. Claude will meet you warmer immediately. The catch is that you will be doing this again next month, and neither copy updates the other.
Memory is the strongest retention feature an AI product has. The more an assistant knows you, the more it costs you to leave, so no lab has an incentive to ship an export that works. Waiting for ChatGPT and Claude to interoperate on your profile means waiting for both to volunteer to make leaving easier. That is not coming.
A pupil inverts the ownership. You take a short free read, it becomes a signed file of who you are and how to meet you, and you paste that same file into ChatGPT, Claude, and whatever ships next. You edit every line, each AI gets exactly what you allow, and revoking access takes one tap. The file is yours, so the question of transferring between companies stops mattering.
Take the free four-minute read, get your word and your one-of-a-kind eye, and add your pupil to ChatGPT or Claude in about two minutes. Revoke it all with one tap, anytime.
Take your read, free Watch the revoke demoWithin a Project, the instructions you paste persist for every chat in that project. Claude also has its own memory features, but like ChatGPT, what it learns stays inside Claude.
Only paste what you would be comfortable with each provider storing. A pupil helps here because you choose exactly which lines travel, and the sensitive layer never leaves you at all.