Migration field guide
ChatGPT to Claude: transfer context carefully
Transfer selected context and working documents. A memory import is not a recreation of every conversation or custom assistant.
Edited by Clinton Feyisitan · Documentation checked
Review scope: Official documentation and field mapping reviewed. The steps below are a proposed validation procedure, not a completed native migration or a measured completion-time claim.
What the documented route supports
OpenAI documents account-data export through eligible account settings or its Privacy Portal; some managed workspaces require an administrator. Claude documents importing memory through Settings → Your Claude (or Memory in older layouts). This imports remembered context, not an automatic transfer of chat threads, custom GPTs, connectors or subscription entitlements.
Map before importing
| Source | Destination | Check |
|---|---|---|
| Conversation archive | Secure reference copy | Do not assume conversations become native Claude threads. |
| Saved preferences | Reviewed memory entries | Check every imported claim and remove obsolete context. |
| Custom GPT instructions | Manually recreated task instructions | Tools and actions require separate configuration. |
| Subscription / API billing | Separate accounts and plans | No automatic credit or entitlement transfer is established. |
A controlled migration
- List the conversations, files, instructions and recurring tasks you actually need. Remove third-party confidential information that you are not permitted to transfer.
- Request and securely download the eligible ChatGPT export. Check the archive before deleting or merging any source account.
- Prepare a short, reviewed context document. Use Claude’s memory import flow for selected remembered preferences, then inspect what it retained.
- Recreate task instructions and upload only the necessary documents. Reconnect integrations only after checking their separate permissions and availability.
Acceptance checks
Record the result and evidence for each check. Stop the cutover if a required check fails.
- Run the same non-sensitive task with its original source documents.
- Check citations, calculations, missing constraints and remembered preferences.
- Confirm unwanted personal details were not imported.
Budget for overlapping plans, required features, seats, storage or usage, and the time to reconcile exceptions. Check the current provider quote; this guide does not reuse historical subscription prices.
Keep a way back
Keep the original archive and account access until you are satisfied. Remove incorrect destination memories through its controls. A different answer is not evidence that the source data was successfully transferred.
Official sources
Source availability and account UI can change. Native account execution remains untested in this guide.