AI news, problem solutions & tool picks
DigestX

Problem Solutions

Custom GPTs Are Retiring Dec 11: How to Save Yours

· 3 min read

A man typing on a laptop showing the ChatGPT interface
Photo via Pexels

OpenAI is retiring custom GPTs. The company announced on September 11, 2026 that GPTs will be replaced by plugins, and existing GPTs will keep working only until December 11, 2026. After that date, your GPTs and their pages become inaccessible. If you built a custom GPT for work, study or a hobby, the time to save it is now, not in December.

This is not a rumour or a leaked plan. OpenAI published the change in its own Help Center, in a retirement and migration FAQ, and it has already started: new GPT creation is closed on personal plans — Free, Go, Plus and Pro. Enterprise workspaces lost the ability to create new GPTs on October 26, 2026.

The dates that matter

Three dates decide what happens to your GPTs. December 11, 2026 is the retirement date for most users: on that day, custom GPTs and their pages become inaccessible. February 11, 2027 is the later date, but it applies only to FedRAMP workspaces and to Enterprise workspaces with an approved deferral. If you are on a personal plan, December 11 is your deadline. October 26, 2026 has already passed: that was the day Enterprise workspaces lost the ability to create new GPTs, and personal plans lost it earlier.

What moves to a plugin

OpenAI's replacement for a custom GPT is a plugin, and the migration carries most of a GPT across. Your instructions become a skill. Your knowledge files become reference files. Your connected apps become apps. The idea is that the same assistant keeps working, just in a different form — and plugins, unlike GPTs, can be used across ChatGPT, not only inside a single GPT page.

What does not transfer

The migration is not complete, and the gaps matter. Custom actions do not transfer at all: if your GPT calls an external service through a custom action, you must rebuild it, possibly as a custom MCP server. The model you selected for the GPT does not carry over. Your sharing settings do not carry over. Drafts and unpublished edits do not carry over. And your conversations do not move: old chats stay readable after retirement, but they do not become part of the plugin.

The catch: your migrated plugin starts private

The detail most people will miss is access. When you migrate a GPT to a plugin, the plugin starts private. Nobody who used your GPT gets access to the plugin automatically — not your team, not your subscribers, not the people who bookmarked the GPT page. You must share it again yourself. And once you migrate, the original GPT becomes read-only, so you cannot go back and fix an instruction you forgot.

How to migrate, step by step

First, finish your essential edits while the GPT is still editable, because migration locks it. Second, open My GPTs and choose “Migrate to plugin” on the GPT you want to keep. Third, test the new plugin with the prompts you use most, and check that it answers the way the GPT did — especially if the GPT relied on knowledge files, because those are now reference files with different behaviour. Fourth, re-share the plugin with everyone who used the GPT. Fifth, if your GPT used custom actions, plan the rebuild now: a custom MCP server is the path OpenAI points to, and it takes longer than the migration itself.

What to do before December 11

Make a list of the GPTs you actually use, and migrate the important ones first. Download or copy any instructions and knowledge files you cannot afford to lose, so you have them outside ChatGPT as well. Check which of your GPTs use custom actions, and decide whether each one is worth rebuilding. And tell the people who use a shared GPT that it is moving: after December 11, the old GPT page will simply stop working, and anyone who tries to open it will find nothing there.