Custom GPTs Are Being Retired: What to Do Next
OpenAI is retiring custom GPTs and moving creators to a newer feature called plugins. Your GPTs still work today, but OpenAI has set a retirement date, so the safe move is to save each GPT's instructions and knowledge files now and test a replacement before the cut-off. If you only use someone else's GPT, you do not migrate anything, but you should check the notice on it for a replacement.
This post covers what is happening, the dates from OpenAI's own help page checked on 24 October 2026, exactly what transfers to a plugin and what does not, and a one-page inventory you can fill in to make sure nothing important is lost.
Key takeaways
What is changing: OpenAI plans to retire custom GPTs and move creators to plugins.
When: GPTs are scheduled to retire on 11 December 2026 (Enterprise with an approved deferral: 11 February 2027). They keep working until then.
What transfers: your instructions become a skill and knowledge files are copied to the plugin. Custom actions and the selected model do not carry over.
What to do now: save a copy of each GPT's instructions and files, and do not start building a brand new GPT.
What is happening to custom GPTs?
OpenAI says it is planning to retire custom GPTs and help creators migrate them to plugins. A custom GPT was a version of ChatGPT you set up with your own instructions and files. A plugin is the replacement, and OpenAI describes it as something that brings together skills, connected apps and reusable workflows in one place.
The change affects all ChatGPT plans, though the exact migration steps and timing can differ by account or workspace. OpenAI's advice is to follow the notice shown inside your own account, because that reflects what applies to you.
When do they stop working?
Custom GPTs are scheduled to retire on 11 December 2026, according to OpenAI's migration FAQ. For Enterprise workspaces with an approved deferral, the date is 11 February 2027, and that extension applies only to workspaces that qualified for it.
Your existing GPTs stay usable until the retirement date. After you migrate a GPT, the original keeps working until retirement but becomes read-only, so finish any essential edits before you migrate.
One more date worth knowing: OpenAI's Enterprise timeline planned 26 October 2026 as the day creating brand new custom GPTs ends. That date will have passed by the time you read this, so check your own account to see whether it applies. Dates are described as subject to change, so reopen the FAQ for your own account before you plan around any of them.
Can I still create a new GPT?
This is where you should check your own account rather than trust an old tutorial. OpenAI's timeline includes a planned end to creating new custom GPTs, and many how-to articles still walk you through building one. If your account no longer offers GPT creation, that is expected, not a fault.
The practical takeaway: do not start building a new GPT now. Put that effort into a plugin instead, or into saving the GPTs you already rely on.
What are plugins and how are they different?
A plugin is OpenAI's new container for the things a task needs. According to the Plugins help page, a plugin can include skills (reusable instructions and workflow guidance), connected apps (links to services like Slack), and extensions you interact with. Some plugins are only skills and need no app connection at all.
So the closest mapping is this: your GPT's instructions become a skill inside a plugin. The difference is that a plugin can also hold connected apps and can be used automatically when its description matches your request, or by typing an @ mention. A plugin is not identical to a GPT, so expect to test it rather than assume it behaves the same.
OpenAI's "Skills in ChatGPT" help page backs this up: it defines a skill as a reusable, shareable workflow that ChatGPT can use automatically when it is helpful, and says a plugin can include skills, apps, or both. So a migrated GPT's instructions living on as a skill matches how OpenAI describes skills.
What moves over and what does not
This is the part to read twice, because some things transfer and some do not. Here it is as labelled lines.
Transfers: your GPT's instructions become a skill in the plugin. Your knowledge files are copied into the plugin's reference files. Connected apps are added to the plugin as apps.
Does not transfer: custom actions do not carry over through migration, so any integration that called an external service will not work until you rebuild it, which may need a custom MCP server and setup. The GPT's selected model does not carry over. Your sharing settings do not carry over, and a migrated plugin starts private.
Also note: migration uses your GPT's latest published version, so drafts and unpublished edits are not included. Publish essential edits before migrating. Public sharing is not required to migrate.
How to list and save your GPTs this week
Before any migration, make your own record. If migration has a hiccup, this is your backup. Fill one row per GPT you actually use.
GPT name | What job it does | Instructions saved? (copy the full text) | Knowledge files saved? | Any custom action? | Replace with
Work top-down from the GPTs you open most. Copy the full instruction text into a document and keep a copy of each knowledge file. For any GPT with a custom action, flag it, because that is the part that will not move on its own.
How to migrate and test a plugin
When migration is available for your account, OpenAI says you go to My GPTs and select Migrate to plugin for the GPT you want to move, then follow the steps to create the plugin.
After migrating, test it properly. OpenAI's own advice is to compare familiar prompts and at least one harder case, and to check that the plugin picks the right skill, uses the expected reference material, produces output in the format you need, and has any tools the workflow requires. Run three prompts you would normally give the GPT and compare the results side by side before you rely on it.
For writing the skill instructions clearly, the same habits that made a good GPT prompt apply. See how to write ChatGPT prompts that work and the ready-to-adapt set in 50 ChatGPT prompts for business owners.
If you only use someone else's GPT
You do not migrate a GPT you did not create, and permission to use one does not let you migrate it. OpenAI's advice is to check the notice on the GPT and any guidance from its creator about a replacement.
Be aware of one trap: a public GPT made inside an Enterprise workspace follows that workspace's transition, even if you use it from a personal account. So a GPT you depend on could change on a date set by someone else's workspace, not yours. If a GPT is important to your routine, ask its creator what their replacement plan is.
Alternatives while you wait: Projects and saved instructions
You do not have to wait for migration to get organised. Two things already help.
Projects keep related chats, files and instructions together, which covers a lot of what people used simple GPTs for. Saved instructions let ChatGPT remember how you like answers, so you do not retype the same setup each time.
For many small businesses, a Project plus a clear saved prompt replaces a basic GPT well enough to bridge the gap. If your GPT was doing something closer to automation, note that plugins can also run scheduled or event-based tasks, which is a separate capability worth exploring once your plugin exists.
OpenAI's "Scheduled tasks in ChatGPT" help page confirms this automation: tasks can run one-time, on a recurring schedule or on a supported app event, and event-triggered tasks run in Work. It also prints active-task limits by plan, for example 3 on Free and Go and 5 on Plus, so check your own plan before relying on heavy automation.
Google is making a similar change to its own saved assistants. If you also use Gemini, see Gemini Gems are becoming skills: what to do now, because the preparation steps are nearly the same.
FAQ
Are custom GPTs really going away?
Yes. OpenAI says it plans to retire custom GPTs and migrate creators to plugins. They are scheduled to retire on 11 December 2026, with 11 February 2027 for Enterprise workspaces that have an approved deferral.
Will I lose my GPT's instructions and files?
No, if you migrate. OpenAI says instructions become a skill and knowledge files are copied to the plugin. Custom actions, the selected model and sharing settings do not transfer, so save everything yourself as a backup.
Can I still make a new custom GPT?
Check your account. OpenAI's timeline includes a planned end to creating new GPTs. If the option is gone, build a plugin instead.
What happens to my old conversations?
OpenAI says existing conversations with custom GPTs stay accessible after retirement, and you do not need to do anything to keep them.
Is a plugin the same as a GPT?
No. A plugin holds skills, connected apps and extensions, and can be used automatically or by @ mention. Expect it to behave a little differently, so test it before relying on it.
What if I only use a GPT someone else made?
You do not migrate it. Check the notice on the GPT and ask its creator about a replacement. A public GPT built in an Enterprise workspace follows that workspace's dates, even if you use it from a personal account.
Book a consultation
If you built a GPT your business runs on and you want help moving it safely into a plugin without losing a step, you can book a consultation at pratiksinghrajput.com/book-online.






Comments