TLDR: OpenAI has scheduled December 11, 2026 as the day custom GPTs and their pages become inaccessible, on every ChatGPT plan, with no exception listed for the person who built them. The migration path OpenAI offers, plugins, does not carry over a GPT's custom Actions, and a migrated personal plugin starts private. If your business runs on a GPT, the clock is real. The way through is to move the method out of the GPT and into a Skill your subscribers reach through a connector, from an assistant they already use. You keep the method, the customer list and the subscription. The GPT was only ever the delivery truck.
Key Takeaways
- December 11, 2026 is OpenAI's scheduled date for retiring custom GPTs on every plan; only Enterprise workspaces with an approved deferral get until February 11, 2027. OpenAI says the dates are subject to change.
- Personal accounts already cannot create or publish new GPTs.
- GPT custom Actions do not transfer through OpenAI's migration workflow, and a migrated personal plugin starts private.
- Your GPT held three things: your method, your subscribers and your billing. Only the first one is tied to the GPT format.
- A Skill is the same method in a form a supported assistant can use through a connector, with the creator deciding who gets in.
- Moving one GPT to one Skill is an afternoon, not a rebuild.
- Do it before your subscribers find out from an error message.
What actually stops on December 11
OpenAI's own help center says custom GPTs and their pages become inaccessible at the retirement date, and that the transition affects all ChatGPT plans. It lists no exception for the creator. Enterprise workspaces can apply for a deferral to February 11, 2027. OpenAI also says the dates are subject to change, which cuts both ways. Old conversations stay readable after that date; the GPT and its page do not.
Personal accounts (Free, Go, Plus and Pro) already lost the ability to create or publish new GPTs earlier this year. If you have been unable to publish a new GPT, that is why.
Why "just migrate to a plugin" is not a plan
OpenAI's replacement for GPTs is plugins. Three facts from OpenAI's own migration page matter for a creator with paying subscribers:
- GPT custom Actions do not transfer through the migration workflow. If your GPT checked a password or called your own server, that logic has to be rebuilt, and OpenAI notes it may need a custom MCP server.
- A migrated personal plugin starts private. Migration does not give other people access.
- Making it public needs a separate submission process, on OpenAI's schedule.
None of that is impossible. All of it is OpenAI's timeline, OpenAI's review and OpenAI's terms. Your subscribers did not sign up for that; they signed up for you.
Three things your GPT was holding for you
- The method. Your prompts, your knowledge files, your way of doing the work. This is the business.
- The subscribers. The people who pay you for access.
- The billing. Whatever you used to charge them.
Only the first one is locked to the GPT format, and it is the easiest to move. The method is text and files. It does not care which assistant reads it.
What a Skill is, in plain words
A Skill is your method written so that an AI assistant can follow it: the instructions, the knowledge, the steps. The difference from a GPT is where it lives and who controls the door. With TCOM, the Skill lives on our server. Your subscriber connects once, through a connector, from the assistant they already use. When they call your Skill, our server checks that they are on your list, then either hands the assistant the Skill for that chat (Password Protection) or runs the method for them and hands back only the result (IP Protection). You add people and remove people. The assistant is just the screen.
That connector works today in Claude and Perplexity, and we are testing it with more assistants as each one opens its door to outside connectors.
An afternoon, not a rebuild
Moving a GPT to a Skill means: paste the GPT's instructions in, upload the knowledge files it used, decide whether it should be password-protected or IP-protected, put it in a Stack, and add your subscribers. The method is the same. What changes is that you can now see who is using it, remove anyone who cancels, and stop depending on one company's product calendar.
Do it before your subscribers do it for you
On December 12 a subscriber who opens your GPT will see an error, not an explanation. The creators who come out of this well are the ones who wrote to their people in November with a link that already works. Start with your best-selling GPT. Move it. Send the connection steps. Then do the next one.
Want to feel the subscriber side first? Connect free and try the two demo Skills in five minutes, one Password-protected and one IP-protected. Then pick a plan and move your first GPT.
