What just changedCustom GPTs are retiring. What happens to yours.
5 minute read
Updated
OpenAI is retiring custom GPTs on 11 December 2026. Enterprise workspaces with an approved extension get until 11 February 2027. Until then your GPTs keep working as they do today.
OpenAI is moving them to plugins, and most of a GPT moves across with little work. The part that does not is the part most businesses care about: what your GPT does inside your other systems, and who is allowed to use it.
What moves across on its own
OpenAI offers a migration that turns each GPT into a plugin.
- Your instructions become a skill inside the plugin.
- Your knowledge files become reference files.
- Apps you had connected may come along with it.
What does not move
This list decides how much work you have.
- Custom Actions. If your GPT looked things up in, or wrote to, your own systems through an action, that connection has to be rebuilt.
- Sharing. The new plugin starts private. The colleagues or customers who used the GPT do not get access until you share it again.
- Past conversations.
- The model you picked for the GPT.
Who needs a plan before December
A personal GPT that helps you write will move across in a few clicks. Three kinds of business use need more than that, because they either stop working or quietly change.
- A GPT your customers use, from a link on your website or in your emails. Once the old GPT retires, every link you handed out points at nothing.
- A GPT your team relies on that reads from or writes to another system through a Custom Action: your CRM, your booking tool, a shared spreadsheet.
- A GPT whose answers you tuned on one particular model. The plugin will not keep that choice, so test the answers again after the move.
A checklist for the next ten weeks
None of this is hard. It only goes wrong when it is left to the last week.
- List every GPT your business uses, and who uses each one.
- Mark the ones with Custom Actions. Those are the rebuilds.
- Mark the ones customers or outside people use. Those need new sharing, and new links wherever you published the old ones.
- Migrate one GPT early and compare its answers with the original before you move the rest.
- Ask whether each job still belongs inside ChatGPT at all.
The question worth asking now
A GPT lives inside someone else's product and changes on someone else's schedule. That is fine for a personal helper. It is a risk for anything your customers or your daily work depend on.
If a GPT has become part of how you serve customers or run a process, this is a good moment to move that job into something you own: a chatbot on your own website, or an automation in your own accounts, that keeps working whatever ChatGPT changes next.
What we would do
If your GPTs are personal helpers, run the migration and move on. It is built to be easy.
If a GPT talks to customers or touches your systems, treat 11 December as the deadline for a small project, not a button to press in December. Plan the rebuilt connections and the new links now, while the old GPT still works and you can compare the two side by side.
If you want a second pair of eyes, our free AI check-up covers exactly this: what you have, what will break, and the simplest way to keep it running.
Still not sure which applies to you?
Fifteen minutes on a call is usually enough to settle it, and we will tell you if the answer is something we do not sell.
Book a callFAQ
Common follow-up questions.
Give your team its hours back.
A free 15-minute call. We look at where your week goes, show you what would take the most off it, and you see exactly what it costs before you decide.