Checked 27 September 2026.
What’s in a ChatGPT data export
A ChatGPT data export is a ZIP file of your conversation history as raw JSON. To request one, go to Settings, then Data controls, then Export, and confirm on the follow-up screen. OpenAI’s help center says the export can take up to seven days to arrive by email, and the download link expires 24 hours after that, so you need to grab it promptly. It’s available on ChatGPT Free, Go, Plus, Pro and eligible Edu accounts; Business, Enterprise and Healthcare workspace users have to go through their workspace owner instead.
The ZIP contains your chat history and other account data, but OpenAI’s own documentation doesn’t list your saved memories, custom instructions, scheduled tasks or custom GPTs as part of it. Two things follow from that. First, the export is useful for keeping a personal archive or searching old chats, since it can’t restore anything you’ve already deleted. Second, if what you want out of ChatGPT is the context it has built up about you, the export ZIP isn’t where that lives, and you need to go get it from the settings screens directly.
What ChatGPT memory and custom instructions store
ChatGPT keeps two separate layers of context, and they don’t move the same way. OpenAI’s memory help page describes saved memories as things you explicitly told it to remember or that it saved as useful on its own, and reference to chat history as a separate, looser layer that draws on past conversations and can change as ChatGPT updates what it thinks is useful. Both show up under Settings, then Personalization, then Memory, where you can review a memory summary and see the sources behind it, which can include past chats, saved memories, custom instructions, files in your Library, or connected apps like Gmail.
Custom instructions are a different setting: a text field where you tell ChatGPT what to know about you and how to reply, applied to every new conversation from then on. According to OpenAI’s custom instructions page, Free and Go accounts get up to 1,500 characters, while Plus, Pro, Enterprise, Business and Education accounts get up to 5,000, a limit OpenAI raised from 1,500 on 15 July 2026. Custom instructions shape how ChatGPT responds; they don’t give it knowledge it doesn’t otherwise have, which is worth knowing before you rely on them for facts rather than tone.
To carry either one to Claude, copy the text yourself: open the memory summary and the custom instructions field, and save what’s in them before you start the move.
Can you bring ChatGPT’s memory into Claude directly
Yes. Claude has a dedicated memory import and export tool, and it’s built for exactly this move. In Claude, go to Settings, then Memory, and select “Start import.” Claude gives you a prompt to paste into ChatGPT, asking it to list everything it has stored about you. Run that in ChatGPT, copy the output, paste it back into Claude, and click “Add to memory.” Claude extracts the text into individual memory entries you can review under “Manage edits.”
Anthropic’s own documentation is direct about the limits: memory imports are “experimental and still in active development,” and “Claude may not always successfully incorporate imported memories.” What transfers well is work-related: preferences, instructions on tone and format, professional details, projects, tools and frameworks. Personal details unrelated to work may not stick, since Claude’s memory is designed around work context. The import doesn’t bring across your ChatGPT conversation history itself, only what ChatGPT reports knowing about you. Updated memory should appear shortly after import, though Anthropic notes it can take up to 24 hours for some accounts. The tool is available on Free, Pro, Max and Team plans, on the web and in Claude Desktop.
What Claude offers to rebuild the rest of your context
Memory import handles preferences and facts. For the deeper context ChatGPT projects and custom GPTs carried, Claude’s closest equivalent is Projects: self-contained workspaces with their own chat history and a knowledge base of uploaded documents that Claude uses across every chat inside that project. Projects are available on every plan, including free accounts, which get up to five.
For instructions that should apply everywhere, not just one project, Claude has a separate account-wide setting called Instructions for Claude (Settings, then Profile), which is the rough equivalent of ChatGPT’s custom instructions field. For the services ChatGPT connected to, Claude has its own Google Workspace connectors for Gmail, Calendar and Drive, available to all Claude and Claude Desktop users, added and authorized separately from anything you connected on the ChatGPT side. And for recurring work, Claude Cowork has its own scheduled tasks on Pro, Max, Team and Enterprise plans, built the same way you’d set up a scheduled task in ChatGPT: describe the job once, pick a cadence, and it runs.
None of these import from ChatGPT automatically. Each one is a separate setup step, using the memory import as your starting point rather than a full copy of your ChatGPT account.
What doesn’t transfer, no matter what you do
| ChatGPT feature | What happens when you switch | Rebuild in Claude as |
|---|---|---|
| Saved memories and reference chat history | Partial: work-related items import via Claude’s memory tool | Memory (Settings, then Memory) |
| Custom instructions | Doesn’t import; copy the text yourself | Instructions for Claude (Settings, then Profile) |
| Full chat history | Exports as raw JSON, not usable as live context | Paste specific past chats into a project as needed |
| Custom GPTs | No import path; OpenAI is retiring GPTs in favor of Plugins, migration targeted for 17 September 2026 and Enterprise retirement set for 11 December 2026 | A Claude project with the same instructions and files, rebuilt manually |
| Connected apps (Gmail, Drive, Slack) | Each connection and its permissions are ChatGPT-specific | Reconnect and reauthorize per service in Claude’s connectors |
| Scheduled tasks | OpenAI’s own help page confirms they’re “not currently included” in data exports | Recreate the prompt and cadence in Claude Cowork’s scheduled tasks |
The pattern across the table is the same: Claude’s memory import moves preferences and stated facts, and everything that’s a configuration, a connection or a running process has to be rebuilt on the Claude side by hand.
A step-by-step migration checklist
- Request your ChatGPT export (Settings, then Data controls, then Export) so you have a personal archive, and download it inside the 24-hour window once it arrives.
- Open your ChatGPT memory summary (Settings, then Personalization, then Memory) and note anything important, since import can miss entries.
- Copy your custom instructions text from Settings, then Personalization, so you have it to paste into Claude’s Instructions for Claude field.
- Run Claude’s export prompt in ChatGPT. In Claude, go to Settings, then Memory, then Start import, and follow the prompt it gives you.
- Paste ChatGPT’s answer into Claude’s import screen and select “Add to memory,” then check the entries under “Manage edits” for anything that didn’t come through.
- Paste your custom instructions into Instructions for Claude, adjusting tone since the two fields aren’t scored the same way.
- Rebuild any custom GPT you rely on as a Claude project with the same files and instructions.
- Reconnect the apps you use, like Gmail or Drive, through Claude’s own connectors.
- Recreate any scheduled task in Claude Cowork with the same prompt and cadence.
- Check back after 24 hours and ask Claude what it learned about you, to confirm the memory import took.
Running ChatGPT and Claude side by side
You don’t have to pick one. Say Sam, a founder in our example cast, keeps ChatGPT for quick drafts and switches a research task to Claude when it needs to work through a longer document. That’s a reasonable way to use both, and plenty of people already do it. The friction shows up in the handoff: neither model knows what the other one did unless Sam tells it, so a decision made in one tool has to be manually carried into the next conversation in the other, every time.
Claude’s memory import narrows that gap for preferences and standing facts, since you can re-run it whenever ChatGPT’s memory picks up something new. It doesn’t close it for an active task. If Sam is mid-way through a competitor brief in ChatGPT and switches to Claude partway through, that brief’s research and drafts don’t come along, only whatever’s been explicitly saved to memory beforehand.
When this isn’t worth doing
If you use ChatGPT for a handful of one-off chats with no saved memory or custom GPTs, there’s nothing to migrate, and setting up Claude fresh is faster than exporting anything. The migration checklist above earns its time mainly if you’ve built up months of preferences, a custom GPT you rely on, or scheduled work you don’t want to write from scratch. And because Claude’s import tool is still experimental, plan on reviewing what it brought in rather than trusting it blind. For anything sensitive, check the imported entries under “Manage edits” before you keep using them.
The underlying issue is structural: ChatGPT’s memory belongs to ChatGPT, and Claude’s memory belongs to Claude, so any context you build in one gets re-created, by hand, when you add or switch to the other. Context that lives outside either vendor sidesteps that entirely. OperatorNest keeps memory you can read, edit and export yourself, and lets you send a given task to whichever model fits it, so a switch between models doesn’t cost you your context.