Analysis | Symaxx Digital
Prepared 27 October 2026
OpenAI's 26 October cutoff has ended new custom GPT creation in affected ChatGPT Enterprise workspaces, excluding FedRAMP workspaces. Existing, unmigrated GPTs remain usable and editable until their applicable retirement date. The immediate task for business owners is to identify which workflows need a replacement and who will check that they still work. OpenAI's GPT guidance.
The broader retirement programme was announced in OpenAI's 11 September release notes. This is an effective milestone in that transition, not a new announcement that all ChatGPT users lost GPT creation on 26 October.
Check which workspace and deadline apply
Custom GPTs are configured assistants inside ChatGPT. This cutoff is not a shutdown notice for a chatbot embedded in a business website or an assistant built with the API. Those are different implementations, as OpenAI's product guidance explains.
The standard retirement date is 11 December 2026. FedRAMP workspaces and affected Enterprise workspaces with a qualifying, approved deferral have a later date of 11 February 2027. The later deadline is not universal. Check the specific workspace notice before scheduling work. OpenAI's current timing guidance.
South Africa appears on OpenAI's supported countries list. That confirms general ChatGPT support, not migration access for every South African account. This is a workspace transition rather than a South Africa-specific rollout.
For an agency managing several clients, record the workspace in which each GPT was created. Do not treat a colleague's successful migration as confirmation that another client has the same options or deadline.
Understand what migration carries across
OpenAI's migration FAQ describes the transfer: instructions become a skill, knowledge files become reference files, and connected apps transfer. The selected model and custom actions do not.
Migration uses the latest published version, not unpublished edits. The original becomes read-only; the replacement starts private, without automatically giving existing users access. Custom integrations may need rebuilding, and equivalent behaviour is not guaranteed.
That makes the acceptance decision more important than the migration button. A tool that produces a plausible answer can still fail its business purpose if it uses an old price list, omits a required section or cannot reach an authorised system.
Build a small migration register
Start with a list of GPTs used in recurring work, rather than every experiment anyone has created. Give each entry an accountable owner, a business purpose, intended users and a dependency list. Note whether it supports an internal task or something delivered to a client.
Prioritise workflows with custom actions, external users or deadlines that leave little room for manual recovery. A draft-writing assistant and a tool that updates customer records should not receive the same testing plan. Decide who can approve the replacement before technical work begins.
For each priority workflow, record representative prompts, the reference material it should use and what an acceptable output contains. Define failures in practical terms: an incorrect currency, a missing disclaimer, an unauthorised record change or an answer unsupported by the supplied material.
Keep this register in an approved internal location. There is no need to send private client documents, credentials or customer records to an outside adviser just to establish the migration plan. Use sanitised examples where they can test the same requirement.
Test the workflow and the people using it
Run the replacement against the recorded tasks and compare it with the agreed acceptance criteria. Include an incomplete brief and a request that should be refused or escalated. Record the result, the reviewer and any unresolved issue instead of relying on a general impression that the output looks good.
Have an intended user test from their own authorised account. Confirm access to the plugin, the relevant files and each permitted app action separately. OpenAI's admin controls guidance distinguishes workspace access, action controls and provider permissions. A working administrator account is not proof that the team can use the workflow.
For a client-facing dependency, agree a replacement link and a support contact before changing instructions or removing an old link. Keep a documented manual alternative for essential work while issues are resolved. Do not widen data access simply to make a test pass.
Budget for review as well as rebuilding
In Enterprise, using a migrated GPT without apps in Instant Chat has no incremental cost. Conversational plugin creation and editing use Work or Codex; Work actions consume credits. These conditions are set out in the migration FAQ.
They do not provide a universal migration-project price. Estimate any integration rebuilding, staff review and ongoing usage separately. Approve a switch only when the owner has evidence that the replacement meets the business requirement and intended users can access it. For South African teams, that is a more useful response to the cutoff than rushing every GPT through migration at once.