OpenAI plans to retire custom GPTs. If you created a custom GPT that you want to keep using, prepare to migrate it to a plugin, test the replacement, and make sure the right people can use it.
Important: The migration experience is being released in stages. The dates and buttons you see can differ by account or workspace. Follow the notice in your Cedarville ChatGPT workspace.
What is changing?
A custom GPT is a tailored version of ChatGPT with its own instructions, knowledge files, and optional tools or connections.
A plugin packages a workflow for ChatGPT. A plugin can include one or more skills (the reusable instructions), reference files, and connected apps. In other words, when a GPT is migrated, its instructions become a skill inside a new plugin.
Key dates
For affected Enterprise workspaces, OpenAI currently lists these planned milestones. Cedarville uses an Edu workspace, so the notice in your workspace is the source to follow for your available dates.
| Planned milestone |
What it means |
| September 22, 2026 |
Target date for the migration experience and user banner in affected Enterprise workspaces. It may not appear for every workspace on that date. |
| October 26, 2026 |
Planned end of creating new custom GPTs in affected Enterprise workspaces. Existing, unmigrated GPTs may still be edited; publish any draft you want to migrate. |
| December 11, 2026 |
Standard scheduled retirement date for custom GPTs. Migrate and test before the date shown in your workspace notice. |
Before you migrate
- Find your GPTs. In ChatGPT on the web, open My GPTs. Identify the GPTs you created and want to keep.
- Decide what is worth keeping. Retire old or duplicate GPTs instead of moving everything.
- Review the current version. Check its instructions, knowledge files, connected apps, and any custom actions.
- Save a few test prompts. Keep examples of normal and more difficult requests so you can compare results after migration.
- Publish any final GPT edits. Migration uses the latest published version. A draft or unpublished change will not transfer. Publishing for migration does not mean you must share the GPT publicly.
How to migrate a GPT you created
- Use ChatGPT on the web and make sure you are in the same account and workspace where you created the GPT.
- Open My GPTs and select the GPT you want to move.
- Select Migrate to plugin when that option is available.
- Review the migration details and follow the prompts to create the plugin.
- Review the new plugin's skill instructions, reference files, and any included apps.
- Test the plugin using the prompts you saved. Confirm that it follows the instructions, uses the expected files, and creates the result you need.
- Share the plugin only after testing it. A migrated plugin starts private, and people who used the GPT do not automatically receive access to the replacement.
Do not skip testing. A migrated plugin may respond differently from the original GPT. The GPT's selected model and its conversation history do not transfer. Custom actions also do not transfer automatically.
Frequently asked questions
What if I cannot migrate my GPT?
First, make sure you are signed into the same account and workspace where you created it. You must be the GPT's creator or a workspace administrator, the GPT must be published, plugins must be enabled for your workspace, and the migration option must be available to your account. If those items are true and you still cannot migrate, contact the IT Help Desk with the GPT name and a screenshot of what you see.
Why do I not see “Migrate to plugin”?
The migration experience is released in stages, so it may not be available in your workspace yet. You also will not see it for a GPT someone else created. Check your workspace notice and confirm that you are in the correct workspace.
Can I migrate a GPT that someone else created?
No. Permission to use someone else's GPT does not give you permission to migrate it. Contact the creator and ask whether a replacement plugin will be shared. A workspace administrator may be able to assist when the required access is enabled.
Why can I not publish or share my plugin?
New plugins start private. Your workspace role may not have permission to share plugins or publish skills to the workspace. An administrator controls these permissions. Ask the IT Help Desk if you believe you need access for a Cedarville work purpose.
Does publishing my GPT make it public?
No. For migration, the GPT must be published so the latest version can transfer. Publishing it for this purpose does not require making it public or available to everyone.
What transfers to the plugin?
The GPT's instructions become a skill in the new plugin, and its knowledge files become reference files. Connected apps are added as apps, but each app still needs its own access and authorization.
What does not transfer?
Your existing GPT conversations, its selected model, sharing settings, and custom actions do not transfer automatically. If your GPT uses a custom action, you may need an available app or a separate technical solution to rebuild that connection.
Will everyone who used my GPT be able to use the plugin?
No. Sharing does not carry over. After testing, choose who should have access and confirm that each person can install and use the plugin. Any connected app still follows its own permissions.
Can I use the plugin right away?
Once it is available to you and installed, use an @ mention or open + and select More, where those choices are available. ChatGPT may also use a helpful installed skill automatically.
Official OpenAI resources
Need help?
If you have questions about this transition or need assistance, contact the CU IT Help Desk.
Call or text: 937-766-7905
Email: techhelp@cedarville.edu