Preparation begins. Confirmed notice date.
IntelligencePrivate by design Saved on this device
Workflow continuity · migration decision
Move the workflow, not just the bot.
Inventory one custom GPT, map what will and will not transfer, run an old-versus-new acceptance pack, and leave with a cutover decision.
Your inputs stay in this browser unless you export them or request a review.
New custom GPT creation is planned to end. Date may change.
Custom GPTs are scheduled to stop running. Confirm your workspace notice.
Step one
Name the workflow people will miss.
Start with business dependence, not the GPT’s title. A rarely used test bot and a daily operating tool should not share a migration queue.
Saved on this device
Step two
Separate what transfers from what must be rebuilt.
OpenAI says instructions become a skill and connected apps are added as apps. Custom actions do not transfer. Prior chats, conversation starters, and the chosen model may not carry over as expected.
Dependency capture
Migration limit: OpenAI says a rebuilt integration should not be assumed to provide every capability of the original custom action. The replacement also starts private, and a redirected GPT link does not grant plugin access.
Step three
Make the replacement earn the switch.
Run every checked case in both the current GPT and replacement plugin. Save the input, output, result, model, tool use, tester, and date.
Twelve old-versus-new tests
Check a case only after the replacement meets the written acceptance rule.
Step four
The migration decision.
This decision combines business dependence, dependency capture, access readiness, and side-by-side tests. It is an operating recommendation, not an OpenAI migration status.
0readiness
Recommended laneRebuild first
Dependencies captured0/8
Tests passed0/12
Days to retirement0
Gaps to close
Fourteen-day migration plan
Migration decision memo
Decision
Business owner
Maintainer
Target cutover
Need an outside review before cutover?Bring Aule the workflow, dependency map, failed tests, and target date. The source and readiness result travel with the request.
Bring the evidence to Aule →Sources, method, and limits
- OpenAI Custom GPT retirement and migration FAQ, updated September 11, 2026. OpenAI says it plans to retire custom GPTs. For affected Enterprise workspaces, it lists a September 17 migration target, a planned September 25 end to new custom GPT creation, and a scheduled December 11 retirement. Dates may change and plan or workspace timelines can vary.
- The same FAQ says instructions become a skill and connected apps are added as apps. Custom actions do not transfer. Conversation starters and prior chats may not copy, the selected model does not carry over, a migrated plugin may respond differently, and the replacement starts private.
Method: Readiness gives 40% weight to eight dependency checks, 40% to twelve acceptance cases, 10% to named owners and fallback, and 10% to a dated cutover and structured evidence. Any custom action without the rebuild check, missing fallback, missing owner, or fewer than eight passed tests prevents a Ready to switch recommendation. These are Aule operating gates, not OpenAI requirements.