AI Tools
How to Move Your Custom GPT to Claude Before 11 December
What OpenAI's retirement means for the GPT you built, when its own plugin route is enough, and how to rebuild it as a Claude Project or Skill.
To move a Custom GPT to Claude, you rebuild it by hand: the instructions and knowledge files go into a Claude Project, and a procedure you repeat can become a Claude Skill. It's worth starting now, because OpenAI's Help Center says Custom GPTs are scheduled to retire on 11 December 2026, after which the GPT and its page can no longer be opened (checked 17 November 2026). Before you rebuild anything, check OpenAI's own Migrate to plugin option, which may be the shorter route if you're staying in ChatGPT.
The steps below come from OpenAI's and Anthropic's own help pages, checked on 17 November 2026. I haven't run a real GPT through either migration, so where your screen looks different from what I describe, trust the screen and the help page.
When do Custom GPTs retire, and what happens to yours?
The standard date is 11 December 2026. OpenAI's Help Center says Custom GPTs are scheduled to retire that day, and that the GPTs and their GPT pages then become inaccessible (checked 17 November 2026). OpenAI says the change affects all ChatGPT plans, and existing GPTs keep working until the date.
The same page gives a later date, 11 February 2027, only to FedRAMP workspaces and affected Enterprise workspaces with a qualifying, approved deferral, and says that date doesn't apply to every workspace. Unless your account notice says otherwise, plan for 11 December.
Your old conversations stay accessible after retirement, according to OpenAI. One detail matters if you use several logins: the timeline of the account or workspace where the GPT was created is the one that applies. Check where each GPT was created before you plan around a date.
In my view, the real exposure sits in the GPT nobody remembers relying on, until someone clicks an old link after the date.
What should you save before you choose a path?
Save the instructions and knowledge files of every GPT you created, because after the date you can't open the GPT to copy them. OpenAI's own advice is to list the GPTs you rely on, note whether you created them, and save a few familiar prompts to compare against the replacement (OpenAI Help Center, checked 17 November 2026).
Keep the inventory to one page: each GPT's name, who uses it, where its link has been shared, and whether it calls an outside service through a custom action. My suggestion is to save five prompts you use often, with the answers you liked. That's your test set for either path.
Custom actions need extra care. OpenAI says custom actions don't transfer through its migration and asks creators to allow extra time for GPTs that use them.
If you only use a GPT someone else built, you can't migrate it. OpenAI says permission to use a GPT doesn't give you permission to migrate it, so check the notice on the GPT and any guidance from its creator about a replacement.
Is OpenAI's plugin migration enough?
For a simple GPT, it may well be. If yours is instructions plus a few files, with no custom actions, and your team already works in ChatGPT, OpenAI's Migrate to plugin route is the shorter one. I'd rather say that plainly than talk you into a move you don't need.
A plugin is OpenAI's replacement for the GPT. When migration is available for your account, OpenAI says you open My GPTs and select Migrate to plugin (OpenAI Help Center, checked 17 November 2026). The instructions become a skill within the new plugin, the knowledge files are copied into its reference files, and connected apps are added as apps.
Two rules on OpenAI's page decide the order of work. Migration uses the GPT's latest published version, so unpublished edits don't transfer, and afterwards the original GPT becomes read-only. Finish and publish essential edits first, then migrate (publishing doesn't mean sharing it publicly, OpenAI notes).
OpenAI says custom actions and the selected model don't carry over. The plugin starts private, so your users don't get access automatically, and public sharing settings don't carry over either. OpenAI also warns that a migrated plugin may respond differently.
If you don't see the option, OpenAI says migration may not be available to your account yet, or plugin access may be disabled. Check your account notice, and make sure you're in the account or workspace where you created the GPT.
Why would you move to Claude instead?
Usually for one of two reasons: your team already works in Claude, or you'd rather not rebuild your process inside another format that one vendor controls.
The second is the risk reason. A Custom GPT lives on one company's platform, and that company has decided it ends. A plugin is OpenAI's format too. A Claude custom skill is a folder with a skill.md file, and Anthropic's help page points skill authors to the open Agent Skills specification, so skills can work across platforms that adopt it (Claude Help Center, checked 17 November 2026). My read: that's worth something, though a standard only helps as far as other tools adopt it.
The cost is real: you rebuild by hand, and you retest. I haven't timed a move on a real GPT, so I won't guess how long yours will take. A GPT with custom actions needs extra time on either route, as OpenAI warns for its own, because the connection has to be rebuilt.
If you're still weighing the two products, my plain comparison of Claude and ChatGPT is a sensible start. For a wider rethink, see the AI tools I'd look at first.
Project or Skill: which one fits your GPT?
A Project fits a GPT that mostly says "act as this, using these documents". A Skill fits a GPT that runs the same procedure every time, such as turning a client brief into a quote in your format.
Anthropic's help page draws the same line: projects give Claude background knowledge that is always loaded, while skills are procedures that switch on when a task needs them (Claude Help Center, checked 17 November 2026). The same help pages say projects are open to all users, with up to five on a free account, and that skills work on the Free, Pro, Max, Ultra, Team and Enterprise plans once code execution is switched on in your settings.
If your GPT is a bit of both, I'd start with a Project, because it's the closer match and the simpler one to set up, and add a Skill later for the procedure you repeat most.
The Claude Help Center says you can share projects with other people in your organization on a Team or Enterprise plan. On the other plans, expect each user to set up their own copy.
How do you rebuild your GPT in Claude, step by step?
Build one Project from your saved files, then test it before anyone else switches. One caution: Anthropic says it is rebuilding Projects as a new beta version that is rolling out in stages, so your screens may differ from these steps (Claude Help Center, checked 17 November 2026).
- Open your saved folder with the instructions, knowledge files and test prompts.
- Create the Project. Go to claude.ai/projects and click New Project. The Claude Help Center notes that Claude can't see the project's name and description, so anything it must know goes into the instructions.
- Add the instructions. Click Set project instructions, paste in your GPT's instructions and save. The Help Center says Claude uses them in every chat in the project.
- Upload the knowledge files with the plus button in the project knowledge area. The Help Center says they're used across all chats in the project.
- Build a Skill only if you need one. It's a folder with a skill.md file that starts with a name and a description, and Claude uses the description to decide when to apply it (Claude Help Center, checked 17 November 2026). Name the folder after the skill, zip it with the folder at the root, and upload it under Customize, then Skills.
- Rebuild the actions separately. Anthropic's skill guide points to MCP connections for outside services, so check whether a ready-made connection exists for each one. If none does, OpenAI's page says rebuilding may require a custom MCP server and technical setup, which is a job for a developer. Before you connect anything, my comparison of the 2026 AI agents covers what each one does with your data.
- Test with your saved prompts plus one hard case, and compare the answers. OpenAI says even its own migrated plugin may respond differently, so expect to adjust the wording of your instructions.
- Tell your users, and replace every link to the old GPT in emails, documents and course pages before the retirement date.
What doesn't carry over to Claude?
Your instructions and files carry over by copy and paste. Custom actions, the model setting and your shared links have to be replaced.
| Part of your GPT | Claude equivalent | Effort |
|---|---|---|
| Instructions | Project instructions, or a Skill | Copy, paste and retest |
| Knowledge files | Project knowledge | Upload again |
| Custom actions | An MCP connection or a custom build | Rebuild, may need a developer |
| Selected model | Your model choice inside Claude | Check |
| Public sharing settings | Not carried over (OpenAI Help Center) | Replace every link you shared |
| Old conversations | Stay accessible in ChatGPT after retirement (OpenAI Help Center) | Nothing to do |
Basis: OpenAI Help Center, Custom GPT retirement and migration FAQ, and the Claude Help Center pages on projects and skills, all checked 17 November 2026. The effort column is my own judgement, not a measurement.
The row I'd watch is sharing. An old GPT link in an onboarding email or a course page fails quietly, and nobody tells you.
How much time do you have, and what should you do first?
You have until 11 December 2026 on the standard date, according to OpenAI's Help Center (checked 17 November 2026). The 11 February 2027 date applies only to FedRAMP workspaces and some Enterprise workspaces with an approved deferral, so follow your account notice.
My suggestion: save every GPT's instructions and files today, then rebuild and test the one you'd miss most within the next few days. After that, move the rest and tell your users. Aim to be done by 4 December, which leaves a week for anything that breaks.
From a risk point of view, the deadline should never be the first day you test the replacement. OpenAI says migration access may arrive at different times, so check your account notice again before the date.
Frequently asked questions
When do Custom GPTs retire?
OpenAI's Help Center says Custom GPTs are scheduled to retire on 11 December 2026 (checked 17 November 2026). That is the standard date for all ChatGPT plans. FedRAMP workspaces and some Enterprise workspaces with an approved deferral have until 11 February 2027, and OpenAI says the later date doesn't apply to every workspace.
What happens to my Custom GPT after 11 December 2026?
According to OpenAI's Help Center, the GPT and its GPT page become inaccessible at the retirement date (checked 17 November 2026). Your existing conversations with Custom GPTs stay accessible after retirement, and you don't need to do anything to keep them. Anything you want to reuse, such as the instructions and knowledge files, should be saved before the date.
How do I move a Custom GPT to Claude?
You rebuild it by hand: copy the GPT's instructions into a Claude Project's instructions and upload the knowledge files to the project knowledge. A repeatable procedure can become a Claude Skill, which is a folder with a skill.md file uploaded as a ZIP under Customize, then Skills (Claude Help Center, checked 17 November 2026). Test the result with prompts you saved from the GPT before you switch.
How do I migrate a Custom GPT to a plugin?
When migration is available for your account, OpenAI's Help Center says you go to My GPTs and select Migrate to plugin (checked 17 November 2026). Migration uses the latest published version, so finish and publish essential edits first, because the original GPT becomes read-only afterwards. If you don't see the option, check that you're in the account or workspace where you created the GPT.
Do custom actions transfer when I move my GPT?
No. OpenAI's Help Center says custom actions don't transfer through its migration workflow, and that rebuilding the connection may require a custom MCP server and technical setup (checked 17 November 2026). The Claude Help Center points to MCP connections for outside services, so the action has to be rebuilt in Claude too.
Can I migrate a Custom GPT that someone else created?
No. OpenAI's Help Center says permission to use someone else's GPT doesn't give you permission to migrate it (checked 17 November 2026). Check the notice on the GPT and any guidance from its creator about a replacement before 11 December 2026.
Can I use Claude Projects and Skills on the free plan?
Yes, with limits. The Claude Help Center says projects are available to all users, and free accounts can create up to five (checked 17 November 2026). Skills are also available on the free plan, but they need code execution switched on in your settings.
Where to go from here
Open each GPT you built today and save its instructions and knowledge files, before you decide anything else. In my view, the choice between a plugin and Claude matters less than having a tested replacement before OpenAI's 11 December date. Then pick the one GPT you'd miss most and move it first.
If you'd like one short, practical note on AI and risk a week, The Risk Memo goes out every Tuesday.
Disclosure: Freistyle AI is part of Anthropic's startup program, which gives the business free Claude credits. Prices and features above come from each company's own pages.
Researched with AI tools, written and fact-checked by Dominic.
Sources
- OpenAI Help Center, Custom GPT retirement and migration FAQ (checked 17 November 2026)
- Claude Help Center, What are projects? (checked 17 November 2026)
- Claude Help Center, How can I create and manage projects? (checked 17 November 2026)
- Claude Help Center, What are skills? (checked 17 November 2026)
- Claude Help Center, Use skills in Claude (checked 17 November 2026)
- Claude Help Center, How to create custom skills (checked 17 November 2026)