What to do with your custom GPTs before they retire on December 11, 2026
On December 11, 2026, OpenAI retires custom GPTs and replaces them with plugins. We read closely what the move keeps and what it leaves behind, and the answer mostly depends on one thing: whether your GPT serves you alone or a whole team.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 18, 2026.
On December 11, 2026, custom GPTs are retired. ChatGPT plugins take their place, and OpenAI offers to migrate each GPT in a few clicks, from My GPTs1.
On paper, the move is simple. Reading OpenAI’s FAQ closely, though, we saw that it leaves two things behind that many GPTs depend on: their custom actions and their sharing.
The short version. If your GPT helps you alone to write or dig through your documents, move to the plugin without much thought. If it works as a tool for your colleagues or your clients, take an hour to decide what you want to do with it.
Here is what we recommend for each case, before going into detail.
| Your case | What we recommend |
|---|---|
| You use someone else’s GPT | Nothing to migrate: follow the notice shown on the GPT and the replacement its creator offers |
| You built a GPT for yourself, with instructions and files | Migrate it to a plugin, or move to a ChatGPT project |
| Your GPT calls other software through a custom action | Migrate it, then rebuild the action with a ChatGPT app, ChatGPT Sites or an MCP server of your own, which while can host |
| Your colleagues or clients use your GPT as a tool | Turn it into a tool on while, with its own address, that anyone you choose uses without a ChatGPT account |
What the plugin keeps from your GPT
A plugin brings instructions, files and connected apps together in one place, which makes it the natural successor to the GPT. When you migrate your GPT, here is what comes along1:
- The instructions become a skill of the plugin.
- The knowledge files become reference files.
- The connected apps move into the plugin as they are.
Your past conversations stay readable after December 11, with nothing to do on your side. Only FedRAMP workspaces and Enterprise workspaces with an approved deferral keep their GPTs longer, until February 11, 2027.
The model you had picked, on the other hand, does not carry over, so the answers may change. That is why we suggest keeping a few reference questions at hand, as you will see below.
A ChatGPT project, for personal use
If your GPT only kept instructions and files for you, a ChatGPT project is enough. It keeps them in one place, with nothing to migrate. Your past conversations with the GPT stay in your history, without moving into the project.
Migrating a custom GPT to a ChatGPT plugin, in four steps
The migration runs from the account where the GPT was created, and it starts from its latest published version1. Count on four steps:
- Publish your latest changes. Drafts do not carry over to the plugin. Publishing does not mean sharing the GPT with everyone.
- Write down a few reference questions. Pick questions you often ask your GPT, including a hard one, to compare its answers with the plugin’s later.
- Choose Migrate to plugin in My GPTs. If the button does not show, migration is not open to your account yet, or plugins are turned off there.
- Compare the answers. Read the plugin’s skill and files, then ask it your questions. ChatGPT decides on its own when to use an installed plugin, so call it by name to be sure.
Careful, the migration is final. The original GPT stays usable until December 11, but you can no longer edit or delete it. From then on, everything happens in the plugin1.
Rebuilding a GPT’s custom actions
A custom action let your GPT call other software: your shop’s API to track an order, your CRM’s to look up a client, or a spreadsheet to add a row.
OpenAI warns that they do not carry over to the plugin, and that rebuilding them may require an MCP server, a small program that makes those calls available to ChatGPT1.

Three paths, depending on your software and your plan
| Path | For whom | What to know |
|---|---|---|
| An app from the ChatGPT directory | The software already has its app there | Nothing to build: each person connects their own account1 |
| An MCP server hosted on ChatGPT Sites | Every ChatGPT plan | ChatGPT adds the server to a Site, which you publish. On a personal or Pro account, the plugin cannot be shared4 |
| An MCP server of your own | Business, Enterprise and Edu | Added from Plugins, and in Business by the workspace admins3 |
Your own MCP server, on while
The last path leaves you in control of everything, and this is where while saves you time: your AI writes the server and puts it on while itself. You only have to ask.
You, to your AI: Rebuild my GPT’s "order tracking" action as an MCP server, and put it on while.
We did it for an order-tracking GPT whose action queried a shop’s API. The server took about fifty lines, and it had its address on while in under a minute. What while brings next:
- The API credential for your software stays in while, and never goes through your AI.
- The same server also works with Claude, if you switch AI or your colleagues use another one.
- A person on your team approves opening the server to everyone, which ChatGPT needs to call it. If it reads private data, it asks for a sign-in, which ChatGPT knows how to handle3.
Keeping a GPT your team uses as a tool
This case calls for more thought, because many GPTs actually work as small tools: a quote calculator for sales, a catalog search for customer service, an onboarding guide for new hires. Their creator shared them by link, and everyone used them in ChatGPT.
With the plugin, this sharing narrows considerably (source 1, source 2):
| Your ChatGPT plan | Who can use the plugin |
|---|---|
| Business or Enterprise | Your colleagues, once the plugin is shared, then installed and connected by each person |
| Personal or Pro account | You alone, since making it public requires a submission to OpenAI |
| For your clients and suppliers | Only if they are part of your workspace |

What while changes for this tool
We built while precisely for these tools, the ones people build without coding with their AI. Instead of keeping your GPT locked inside ChatGPT, ask your AI, ChatGPT or Claude, to turn it into a tool with its own pages. Here is what you gain:
- An address of its own. Your colleagues use it in their browser, without a ChatGPT account.
- The choice of who uses it. Only your colleagues, a client or a supplier with an access link and a password, or everyone.
- Data that is kept. The tool keeps what people enter, backed up every day, and its automations run at a set time, like a reminder every Monday morning.
- Credentials kept safe. Those for your other software stay in while, and your AI never sees them.
- No dependence on a plugin. The tool works whatever AI you use tomorrow, and your AI improves it whenever you ask.
Try it with your GPT
To try it, give this message to your AI, ChatGPT or Claude. It has your AI read while’s page for AIs:
Read while.sh/agents and help me get started with while.
The trial is free, with no sign-up, and your tool has its address in 3 minutes. If you want to keep it, you create your account. Your tools are hosted in France by Nextmap.
Sources
- OpenAI, Custom GPT retirement and migration FAQ, accessed November 18, 2026
- OpenAI, Plugins in ChatGPT, accessed November 18, 2026
- OpenAI, Connecting custom MCP servers in ChatGPT, accessed November 18, 2026
- OpenAI, Hosting a plugin with ChatGPT Sites, accessed November 18, 2026