OpenAI is retiring custom GPTs, and the deadline is close. The company's current help guidance says custom GPTs stop running on December 11, 2026, with a later date of February 11, 2027 for FedRAMP workspaces and for Enterprise workspaces with an approved deferral. If you rely on a custom GPT for recurring work, now is the time to move it. The good news is that the migration path is clear, and your past conversations will stay accessible.
Step 1: Check Your Deadline
Dates depend on your workspace, so confirm yours before planning. Standard accounts face December 11. Enterprise workspaces are on a different track. In affected Enterprise workspaces, the ability to create new GPTs ended on October 26, 2026, except for FedRAMP workspaces. Anyone who needs a new assistant in one of those workspaces should look at plugins or projects instead of creating another GPT.
Step 2: Inventory Every GPT
Make a list of each custom GPT you use, along with its purpose and who created it. Note whether it uses custom actions, which connect a GPT to outside systems, and whether it is shared with a team or published publicly. Only a GPT's creator, or an Enterprise admin, can migrate it, so a GPT built by a colleague may need to be handled by them.
For each one, classify its job. A repeatable process, a knowledge base and a cross-system workflow each call for a different replacement. The classification determines whether you migrate it as a plugin, rebuild it as a project or connect it to an app.
Step 3: Save What You Will Need
Before migrating, copy each GPT's instructions, reference files and common prompts somewhere outside ChatGPT. A plain text file or a snippet manager works well. Keeping these materials in a neutral place also makes it easier to reuse them in other AI tools if you decide to switch providers later.
Migration is not a complete copy. Based on OpenAI's guidance as reported by migration guides, the following items do not transfer:
- Custom actions: these may need to be rebuilt to reconnect to your systems.
- Selected model: the replacement will not automatically keep the GPT's model setting.
- Sharing settings: you will need to reshare the plugin and confirm that the audience can access it.
- Past conversations: chats stay with the original GPT, which becomes read-only after migration.
Step 4: Migrate and Test
When you migrate a GPT, its instructions become a skill inside a plugin, and its uploaded knowledge files become reference files. Connected apps can carry over. Finish any pending edits and publish the latest version before you start, so the migrated copy reflects your current setup.
Testing matters more than migration itself. A skill is used when its description matches a request, which means a plugin may not trigger on every request the old GPT handled. Save a set of familiar test prompts and run them against the plugin. Check formatting, reference file use and whether the assistant follows the same rules as before.
Step 5: Rebuild Actions and Reshare
If your GPT relied on custom actions, rebuild those connections before you switch over. Then reshare the plugin with its intended audience and confirm that people can open it. Doing this in the week before the deadline leaves little room for error, so start now.
Alternatives If a Plugin Does Not Fit
Not every GPT belongs in a plugin. For ongoing work that involves a set of chats, files and instructions, a ChatGPT project keeps everything together, although projects do not carry over actions or sharing settings. For work that depends on outside systems, connected apps or a rebuilt integration may be the better path. Choose the replacement based on what the GPT actually did, not simply on what is easiest to copy.
Why It Matters
Custom GPTs were one of the first ways many people customized a chatbot for their work, and their retirement is a reminder that AI tools change quickly. Anyone who has built prompts or workflows inside one vendor's product faces the same risk. Keeping instructions and reference files in a portable form protects your work from the next platform change.
