People who use ChatGPT as a portable workbench—opening the same specialized assistant across a laptop, tablet, or phone—will need to plan for a significant workflow change. OpenAI says Custom GPTs are scheduled for retirement on December 11, 2026, with migrations moving users to its newer Plugins + Skills system rather than to Projects.
The change applies across ChatGPT plans, although the migration option may arrive at different times for individual accounts. In affected Enterprise workspaces, the migration experience is already rolling out. OpenAI also plans to stop the creation of new Custom GPTs on October 26, while existing ones will continue working until the December retirement date.
A different container for repeatable AI work
Custom GPTs grew out of the GPT Store model: a user could assemble a focused assistant from instructions, knowledge files, and, in some cases, Actions, then keep it private or share it with others. The new approach splits that setup into a Plugin and one or more Skills. A Skill holds instructions and workflows, while a Plugin can also include connected apps and other reusable capabilities. ChatGPT may automatically select a Skill when a request matches its description.
OpenAI’s migration tool will appear under My GPTs as “Migrate to plugin.” For relatively simple assistants, the conversion should preserve the core material needed to recreate a repeatable task setup.
- GPT instructions are converted into a Skill.
- Knowledge files become reference files.
- Connected applications can be included in the Plugin.
What creators will have to rebuild
The transition is not a one-to-one archive or clone. That distinction matters most for people who depend on a carefully tuned GPT for recurring research, classwork, client support, or team processes from multiple devices. OpenAI cautions that the migrated Plugin may respond differently from the original GPT and recommends testing the same prompts before committing to the change.
- Existing conversations will not migrate.
- The model selected for the Custom GPT will not be retained.
- Custom Actions will not transfer automatically; external API integrations may need to be rebuilt through an available app or an MCP server.
- Sharing settings will not carry over. A migrated Plugin starts private, and prior recipients will not automatically receive access.
That leaves the most work for creators whose GPTs combine external Actions, public or team distribution, and workflows refined over time. A basic assistant built from instructions and a small document collection should have a more straightforward path to a Skill and Plugin. For everyone else, the practical deadline is December 11, 2026—and the remaining unknown is exactly when each account will receive its migration controls.
Post Footer automatically generated by Add Post Footer Plugin for wordpress.
