Planned custom GPT retirement and migration to plugins
If your organisation has built custom GPTs — say, an internal FAQ bot or a client-facing assistant — they will stop working in their current form once OpenAI's retirement date for your plan hits. Take stock of any GPTs your team relies on now, work out who built them, and plan the move to OpenAI's new plugin format before that date so a tool you depend on doesn't vanish without warning.
What changed
Source summary
OpenAI is retiring custom GPTs across all ChatGPT plans and providing a migration path to plugins, which combine reusable instructions with connected apps. Existing GPTs keep working until each plan's specific retirement date; OpenAI recommends reviewing which GPTs you rely on, who created them, and who needs access before migrating.
Why it matters to your work
Practical interpretation
If your organisation has built custom GPTs — say, an internal FAQ bot or a client-facing assistant — they will stop working in their current form once OpenAI's retirement date for your plan hits. Take stock of any GPTs your team relies on now, work out who built them, and plan the move to OpenAI's new plugin format before that date so a tool you depend on doesn't vanish without warning.
When this could help
Start planning now: review the custom GPTs you rely on, identify their creators, and note who needs access — so you are ready to test and migrate when the migration path becomes available for your plan.
OpenAI has announced plans to retire custom GPTs across all ChatGPT plans and provide a migration path to plugins, which combine reusable instructions with connected apps. No firm retirement date has been set, but preparation is advised.
How to get started
Review the custom GPTs you rely on and identify their creators.
Provider guidance ↗Note who in your team needs access to each GPT's functionality.
Provider guidance ↗When migration becomes available for your plan, test the migrated plugins and review sharing and permissions.
Provider guidance ↗
Build it into your routine
SCALA suggested workflow
GPT migration readiness
Create a list of all custom GPTs your team uses, their creators, and their purpose. When the migration path opens, work through the list systematically: migrate, test, update sharing, and confirm with users before the retirement deadline.
What to check
- No firm retirement date is given. Timing and migration availability vary by plan and workspace. Source ↗
Sources & provider guides
Official documentation checked 12 Oct 2026. SCALA prompts and workflows are suggestions, not claims of hands-on testing.
Source & availability
This is a summary of a published provider announcement, with practical context from SCALA’s feed.
Plan, region, workspace and rollout conditions may affect access in Australia. Check the original source for current availability.
help.openai.com