OpenAI changes the Enterprise transition timetable
OpenAI’s dedicated custom GPT retirement FAQ now targets 22 September for the migration experience and in-product migration banner in affected Enterprise workspaces. It also moves the planned end of new custom GPT creation to 26 October. Earlier OpenAI guidance had pointed to 17 September for migration and 25 September for the creation cutoff, so the current FAQ materially extends both milestones.
The planned retirement date remains 11 December 2026. Existing GPTs can continue to be used until retirement, subject to workspace permissions. OpenAI says the transition affects all ChatGPT plans, while the detailed milestone table in the current FAQ applies specifically to Enterprise workspaces and warns that the migration target is not a guarantee that every workspace receives the experience on the same day.
Migration carries instructions and files, but not every GPT property
When migration is available, a creator can open My GPTs and choose Migrate to plugin. OpenAI says the latest published GPT version is transferred: its instructions become a skill, connected apps become plugin apps and knowledge files are copied into the new plugin as reference files. Draft or unpublished GPT edits are not included in that conversion.
Several properties do not transfer automatically. The GPT’s selected model is not preserved, previous conversations do not migrate and existing sharing settings do not carry over. Custom actions also do not transfer; OpenAI says workflows that depend on them may need to be rebuilt around a custom MCP server or another supported plugin integration.
The original GPT stays available but becomes read-only after migration
Migrating does not immediately remove the original GPT. OpenAI says it remains usable until the retirement date, but becomes read-only after migration and its creator can no longer delete it. The migrated plugin starts private rather than inheriting the GPT’s audience, and it is not automatically installed for people who previously used the GPT.
That makes the transition an access-management task as well as a format conversion. Enterprise administrators and GPT owners need to review who should receive the migrated plugin, whether its connected apps remain appropriate and whether any custom-action workflow needs a replacement before the old GPT surface disappears.
The latest FAQ is the operative schedule, with rollout uncertainty still explicit
Some broader OpenAI help pages still reflect the earlier September dates, while the dedicated retirement FAQ was updated with the later 22 September and 26 October targets. The wire therefore uses the more specific current FAQ for the schedule and preserves 11 December as the planned retirement date. In-product notices remain important because OpenAI explicitly says migration availability can differ by workspace.