Overview
We're planning to retire custom GPTs and help creators migrate them to plugins. Plugins can bring reusable instructions, reference files, and connected apps together, so your guidance can work alongside the tools and information a task needs.
If you created a GPT, prepare to migrate and test it when migration is available for your account. If you use someone else's GPT, check its notice and the creator's guidance about a replacement. For more information about plugins, see: Plugins in ChatGPT and Codex.
Does this change affect all ChatGPT plans?
The transition affects all ChatGPT plans. Migration and plugin access may differ by account or workspace. Follow your in-product notice for the options available to you. Enterprise dates and admin guidance appear at the end of this FAQ.
If you use several accounts or workspaces, check where the GPT was created. The timeline and permissions for that account or workspace apply to the GPT, even if you use it from another account.
Timing and what to do now
Is my GPT already gone?
No. The announcement gives you time to prepare for a future retirement. Existing GPTs remain usable until the retirement date, subject to their existing access and workspace permissions.
After a GPT is migrated, the original remains usable until retirement but becomes read-only. Finish essential edits before migrating and maintain the replacement plugin afterward.
When are custom GPTs retiring?
Custom GPTs are scheduled to retire on Dec 11, 2026. For affected Enterprise workspaces with an approved deferral, the retirement date is Feb 11, 2027. This extension applies only to workspaces with a qualified, approved deferral. Follow the notice for your account or workspace, including any different timeline communicated to you.
Migration access may become available at different times. A target migration date does not guarantee that every account can migrate on that day. Restrictions on creating or publishing GPTs are separate from retirement of existing GPTs.
Do I need to take action immediately?
You can start preparing now. Identify the GPTs you rely on and whether you created them or use someone else's. Allow time to test a replacement before retirement.
If you created the GPT, review its instructions, reference files, and connected apps. Save a few familiar prompts so you can compare the replacement's results. Finish and publish any essential edits before migrating; public sharing is not required.
Allow extra time for GPTs that use custom actions. Those integrations do not transfer automatically.
If you created a GPT
How do I start migration?
When migration is available for your account, go to My GPTs and select Migrate to plugin for the GPT you want to migrate. Review the migration details and follow the instructions to create the plugin.
Migration uses the GPT's latest published version. Drafts and unpublished edits do not transfer. Publishing a GPT does not require sharing it publicly.
Review the migrated instructions and reference files, then test the replacement with tasks you normally use your GPT for. The plugin starts private, and migration does not automatically install it or give other people access.
Why don't I see a migration option?
Migration may not be available to your account yet, or plugin access may be disabled. Check the notice in your account and make sure you're using the account or workspace where you created the GPT.
Permission to use someone else's GPT does not give you permission to migrate it. In an Enterprise workspace, a workspace admin can also migrate GPTs when the required access is enabled.
What transfers to the plugin?
Under the planned migration workflow, the GPT's instructions become a skill within the new plugin. Connected apps are added to the plugin as apps.
The GPT's knowledge files are copied into the plugin's reference files. Review the instructions, files, examples, and tools before relying on the replacement.
The GPT's selected model does not carry over. In Enterprise workspaces, Enterprise defaults apply.
What happens to my existing conversations?
You can continue using the original GPT until its retirement date. Your existing conversations with custom GPTs will remain accessible after retirement. You don't need to take any action to preserve them.
What happens to custom actions?
GPT custom actions do not transfer through the migration workflow. Features that depend on them will not work in the plugin until you set up a replacement.
If your GPT uses a custom action to connect to another service, check whether an available app supports the tasks you need. Rebuilding the connection may require a custom MCP server and technical setup. Access to custom integrations depends on the options available to your account or workspace.
Test the integration before switching. A rebuilt integration should not be assumed to provide every capability of the original action.
Will the plugin work exactly like my GPT?
A migrated plugin may respond differently. Compare familiar prompts and at least one harder case. Check that it:
Selects the right skill and follows your instructions.
Uses the expected reference material.
Produces complete answers or files in the required format.
Has the tools and integrations the workflow needs.
Resolve differences that affect your tasks before relying on the replacement. Test any connected apps or rebuilt integrations separately.
What happens to the original GPT after migration?
The original GPT remains usable until retirement, but becomes read-only after migration and its creator cannot delete it. Make future changes to the plugin.
At the applicable retirement date, custom GPTs and their GPT pages become inaccessible. Migrate and test the replacement before the retirement date in your notice.
Can I keep sharing my GPT with the same people?
Migration doesn't carry over your GPT's sharing settings or give its existing users access to the replacement. A migrated personal plugin starts private. Making it public requires a separate plugin submission process.
Before asking people to switch, confirm that they can access and use the replacement.
If you use someone else's GPT
What should I do?
Check the notice on the GPT and any guidance from its creator about a replacement. You do not need to migrate a GPT you only use, and permission to use it does not let you migrate it yourself.
Access to the original GPT does not automatically give you access to a replacement plugin. Check whether a replacement is available to you before switching.
Could a public GPT I use be affected if I am on another plan?
Yes. Public GPTs created in affected Enterprise workspaces are included in the Enterprise transition, even if you access them from a personal account or another workspace. What matters is where the GPT was created, not only your own plan. Check any notice on the GPT and guidance from its creator. Access to a public GPT does not guarantee access to its replacement plugin.
Migration does not carry over the GPT's public sharing settings or automatically make its replacement available to everyone who used it.
What do I need to use a migrated plugin?
You need access to the replacement plugin and an account where plugins are available.
Any included apps still require their own app access, account authorization, and action approvals. Installing a plugin or connecting an account does not give you additional permissions to files or data in the connected service.
How do I use the replacement?
Once the plugin is available to you and installed, select an available plugin or skill for your task. In ChatGPT, you can use an @ mention or open + and select More, where supported.
ChatGPT may also use a relevant installed skill automatically when its description matches your request. Automatic selection depends on the task and available capabilities; the plugin will not necessarily run on every request.
Enterprise workspace guidance
Which dates should I plan around?
For affected Enterprise workspaces, the planned milestones are described below. Note that the dates are subject to change.
Sep 11, 2026: Admin notice to help organizations prepare.
Sep 22, 2026: Target for the migration experience and user banner. This is a target, not a guarantee that the option is available in every workspace.
Oct 1, 2026: Target for the migration banner in workspaces that already opted into delayed migration banners.
Oct 26, 2026 (planned): Creation of new custom GPTs ends. Publish any drafts you need to migrate before this cutoff; public sharing is not required. This creation freeze does not prevent edits to existing, unmigrated GPTs. Migration makes the original GPT read-only. Existing GPTs remain usable until their applicable retirement date.
Dec 11, 2026: Standard scheduled retirement. Custom GPTs and their GPT pages become inaccessible at the applicable retirement date. Migrate and test beforehand.
Feb 11, 2027: Retirement for workspaces with a qualified, approved deferral. This extension does not apply to every workspace.
Standard admin emails use the standard dates and are not tailored to workspaces with approved delays. Check your workspace-specific notice or contact your account team to confirm the timeline that applies.
Who can migrate a GPT in my workspace?
In the planned Enterprise workflow, a GPT’s creator or a workspace admin can migrate it when migration is available and plugins are enabled. The GPT must be published; drafts cannot be migrated directly. Publishing does not require sharing it publicly. Permission to use someone else’s GPT does not give you permission to migrate it.
Built-in migration does not require Upload plugins or Upload plugins with custom MCP servers. Rebuilding an integration is a separate task and may require additional permissions.
For affected Enterprise workspaces, migration is targeted for Sep 22, 2026. Workspaces that already opted into delayed migration banners have an Oct 1, 2026 banner target. Follow your workspace-specific notice. Before migration is available in your workspace, a missing migration option does not by itself indicate a problem.
If migration is available but you cannot use it, ask your admin to check that plugins are enabled, the GPT is published, and you are its creator or a workspace admin.
Will using or editing a plugin consume credits?
In Enterprise workspaces, using a migrated GPT without apps in Instant Chat has no incremental cost. Creating and editing plugins through a conversation use Work or Codex. Actions in Work consume credits.
How do we prepare and share the replacement?
Coordinate with your admin to identify the GPTs your team relies on, who maintains them, and who needs access to each replacement. For GPTs with custom actions, work with the appropriate technical and security teams to review rebuilt integrations and their permissions.
The replacement plugin starts private. Test and review it before sharing. After sharing, ask an intended user to install and test the replacement.
In an Enterprise workspace, sharing with people or groups requires Share plugins. Publishing to the workspace directory requires Publish plugins to workspace. These are separate permissions.
To use a migrated plugin in an Enterprise workspace, you need Use plugins permission and a workspace policy that lets you install the plugin or installs it for you.
For workspace settings, see: Admin controls, security, and compliance for plugins and apps.