Services

Start a project Chat on WhatsApp
News & Insights

Your Custom GPT Stops Working on December 11. Move It Before It Goes

If your business runs on a custom GPT in ChatGPT, that helper has an end date. OpenAI is retiring custom GPTs on December 11, 2026, and after that date your GPT and its page become inaccessible. The good news is that you have time to move, and OpenAI has built a migration path. The harder news is that not everything moves, and the part that does not move is often the part your business depends on most. Here is what is happening, what it means for a small business, and the four steps to take before December 11.

What happened

OpenAI announced that custom GPTs are being retired and replaced by plugins in ChatGPT. A custom GPT is a version of ChatGPT with its own instructions, reference files and connected apps, built for one job such as answering customer questions in your tone or drafting replies to a set of rules. Many small businesses built one for exactly those jobs.

OpenAI’s own help centre puts the retirement date at December 11, 2026, for most accounts. A small number of workspaces get until February 11, 2027: FedRAMP workspaces and Enterprise workspaces with an approved deferral. The change affects all ChatGPT plans, and the notice in your own account or workspace sets the timeline that applies to you. New GPT creation already ended on October 26, 2026 for affected Enterprise workspaces, so this is not a distant plan. It is already under way.

What moves to a plugin and what does not

When migration is available for your account, you open My GPTs and select Migrate to plugin. OpenAI says the GPT’s instructions become a skill inside the new plugin, its knowledge files are copied into the plugin’s reference files, and its connected apps are added as apps.

Three things do not make the trip. Custom actions, the connections that let a GPT call another service, do not transfer, so anything your GPT does through an outside system stops working until you rebuild it. The model you selected does not carry over. And sharing settings do not carry over: the new plugin starts private, and nobody who used your GPT gets access to it automatically. Drafts and unpublished edits do not transfer either, because migration uses the latest published version of the GPT. After migration the original GPT becomes read-only, though it stays usable until the retirement date.

One more difference matters. A GPT applied its instructions to every message in the chat. A skill inside a plugin only runs when ChatGPT decides its description matches your request, and OpenAI says plainly that the plugin will not necessarily run on every request. That is why OpenAI tells creators to test the replacement with familiar prompts and at least one harder case before relying on it.

Your past conversations are safe. Existing chats with a GPT stay accessible after retirement, and you do not need to do anything to keep them.

What it means for a small business

A custom GPT feels like your own tool, but it was always rented ground. Three risks land on a small business first.

First, the helper that answers your customers or drafts your replies stops working on a fixed date, in the middle of December, with no warning to the people who used it. If nobody on your team owns the move, the work falls back on you the week it disappears.

Second, the instructions your team refined over months live in one place you do not control. If you never copied them out, you rebuild them from memory.

Third, the quiet break. If your GPT connects to another service, through a custom action, that connection does not transfer. The plugin can look finished while the part that fetched your orders, checked your stock or filed your tickets is simply gone.

There is one more case to check. If you only use someone else’s GPT, you cannot migrate it yourself. Only the creator, or a workspace admin in Enterprise, can do that, and access to the original does not guarantee access to the replacement. Check the notice on the GPT and any guidance from its creator before December 11, or you may find the tool you relied on has no replacement you can reach.

What to do before December 11

OpenAI’s own guidance comes down to four steps. Do them in order, and start with the second one today.

  1. List the GPTs you rely on, and who created each one. Only the creator, or a workspace admin in Enterprise, can migrate a GPT. If you only use someone else’s GPT, watch for the creator’s guidance about a replacement.

  2. Copy out what makes each GPT work. Save the instructions, the reference files and a few prompts you use often, plus the kind of answer you expect. Do this while you can still edit the GPT, because migration makes the original read-only. A plain copy of your best instructions also protects them from the next change, whatever tool you use next.

  3. Migrate and test. Finish and publish any edits first, since drafts do not transfer. Then check that the plugin picks the right skill, follows your instructions, uses the right reference material and returns answers in the format you need. Test it with a familiar prompt and one harder case, and do not rely on it until it passes both.

  4. Rebuild custom actions and reshare. Allow the most time for GPTs that connect to other services. Those connections need an available app or a custom MCP server to rebuild, and OpenAI says a rebuilt integration should not be assumed to do everything the original did. Once the plugin works, share it with the original audience and confirm they can install and use it before you ask them to switch.

If your GPT was mainly a place to keep instructions and files together for ongoing work, OpenAI suggests a ChatGPT project instead. A project keeps related chats, files and instructions in one place, though it does not carry over custom actions or sharing settings either.

The bigger lesson: own the helper your customers talk to

A custom GPT was always rented ground. OpenAI could change it, and now it has. If the helper that answers your customers lives inside someone else’s feature, its future is someone else’s decision.

A chatbot you own, on your own website or on your WhatsApp number, keeps working when a platform retires a feature, and nobody can switch it off with a product announcement. Digilistan builds AI chatbots and WhatsApp bots for small businesses in the United Kingdom, the United States and Pakistan. If your customer helper is about to lose its home, this is the moment to give it one you control.

Related reading: ChatGPT Now Lets Your Business Claim Its Own Profile. Here Is What a Small Business Should Do. ChatGPT Wallet: AI Agents Can Now Buy for Your Customers.

Sources: OpenAI Custom GPT retirement and migration FAQ. TextExpander: Custom GPT Retirement: What Changes and What to Do Next.

Start the conversation

Tell us what you are building

Whether you need a website, a chatbot that never sleeps or a workflow that gives your team its evenings back, start with a short conversation. We reply to every serious enquiry personally.

  • Your message goes to the founder, not a call center.
  • We suggest the smallest service that fixes the problem.
  • The first conversation costs nothing but a few minutes.

Prefer to talk first? Message us on WhatsApp and skip the form.

Chat with us