The Builder Era Ends: Custom GPT Creation Closes Today as OpenAI Begins Its Great Plugin Migration

Today, September 25, 2026, the “Create” button goes dark. According to OpenAI’s official Custom GPT retirement and migration FAQ, this is the scheduled date when creation of new Custom GPTs ends across ChatGPT plans. From tomorrow on, the no-code builder that let millions of people package instructions, knowledge files, and actions into shareable mini-apps simply stops accepting new entries. The GPTs that already exist keep running until December 11, 2026 — the day custom GPTs are scheduled to stop running entirely and leave the GPT directory.

It is a quiet ending for what was once the loudest idea in consumer AI. Custom GPTs debuted at OpenAI’s DevDay in November 2023 as the flagship “everyone can build a product” pitch, and the GPT Store followed in January 2024 with promised monetization for builders. Less than three years later, the entire surface is being folded into something else: OpenAI’s plugin and skills architecture.

The timeline of a retirement

The wind-down moved fast once it started:

• September 11, 2026 — OpenAI confirmed the retirement in its ChatGPT release notes and began notifying affected Enterprise workspaces by email.
• September 17, 2026 — The in-product GPT-to-plugin migration experience was targeted to begin appearing for creators.
• September 25, 2026 — Creation of new Custom GPTs is scheduled to end. If you didn’t start a GPT before today, you never will.
• December 11, 2026 — Scheduled full retirement: custom GPTs stop running and disappear from the GPT directory.

Two weeks from announcement to the end of new creation is brisk even by OpenAI’s standards, and it lands four days before DevDay 2026 on September 29 — a scheduling choice that practically guarantees the replacement architecture will be the centerpiece of the keynote.

What survives the migration

OpenAI’s FAQ spells out what the migration path actually preserves, and the mechanics are more reasonable than the headline suggests. When a creator migrates a GPT to a plugin:

• Instructions become a skill. The system prompt and behavioral configuration that defined the GPT are converted into the skill format used by ChatGPT’s newer agentic stack.
• Knowledge files become reference files. Uploaded documents survive as references the plugin can draw on.
• Connected apps become plugin connections. Integrations established through ChatGPT’s connected-apps system carry over.

For the Enterprise migration workflow specifically, a GPT must be published before it can be migrated — though “published” does not mean public. Workspace-private GPTs qualify, which spares internal tools that were never meant for the storefront.

What doesn’t

The gaps are where the anger lives. Three things do not survive the move:

Conversations don’t migrate. Every chat a user has had with a custom GPT stays behind. For people who treated a GPT as a long-term collaborator — a writing partner with context, a study tutor with history — the relationship resets to zero on December 11.

Custom actions don’t carry over. GPTs that called external APIs through custom actions, defined via OpenAPI specifications, lose those integrations entirely. Any GPT whose value depended on reaching outside ChatGPT — querying a database, filing a ticket, hitting an internal service — has to have its wiring rebuilt by hand as a plugin.

Sharing resets. Migrated personal plugins start private, and existing users do not automatically receive access. A GPT with a real audience wakes up as a plugin with zero users, and every one of them has to be re-onboarded manually.

The community is not quiet about it

OpenAI’s developer forums tell the story of the collateral damage. A thread titled “Custom GPT → Plugin is not an equivalent migration” questions the rationale outright, arguing that for professional use cases the plugin model genuinely loses capabilities. Another thread on migration access concerns includes a user reporting a business built on 47 GPTs serving 25 active customers — a small operation, but a real one, now facing a forced platform rewrite. A third, from mid-September, is a direct appeal titled “Please Don’t Retire CustomGPTs,” describing how the specific workflow Custom GPTs enable matters for neurodivergent developers who rely on the constrained, predictable builder interface.

The common thread is not that plugins are worse technology. It’s that the migration is not a translation — it’s a re-platforming, and the costs of re-platforming are being paid by the people who built on OpenAI’s invitation.

Why OpenAI is doing this anyway

The strategic logic is not hard to reconstruct. Plugins and skills are the substrate of ChatGPT’s agentic turn: the September 23 update brought plugins into the Live voice experience across web, iOS, and Android, letting users check email and manage calendars by speaking. Reports ahead of DevDay — including a Forbes analysis of OpenAI’s “managed agents” plans — point to a keynote built around agents that act across surfaces. Custom GPTs, a 2023-era construct optimized for shareable chat personas, don’t fit that picture. One agentic architecture, not two parallel extension systems, is the obvious end state.

There is also a governance argument OpenAI won’t make publicly: consolidating extensions into a single plugin pipeline with unified permissions, references, and skills is easier to secure and audit than a parallel GPT ecosystem with its own action system. The company’s September threat-intelligence report, detailing nine months of disrupted misuse, is a reminder of how much weight that consideration now carries.

What to do before December 11

If you own or depend on custom GPTs, the practical checklist is short:

1. Inventory now. List every GPT you’ve created or rely on, including others’ GPTs embedded in your workflow.
2. Publish anything you want to keep. Unpublished drafts can’t be migrated.
3. Export your conversations. Anything with history worth keeping needs to leave ChatGPT before the cutoff.
4. Document custom actions. Pull the OpenAPI specs and credentials for every integration — you’ll be rebuilding them.
5. Plan re-distribution. Assume zero inherited users and prepare to re-share the migrated plugin with everyone who used the original.

The retirement of Custom GPTs is not a scandal, and the replacement is probably better technology. But it is the cleanest recent example of platform risk in the AI era: OpenAI told millions of people to build, they built, and now the ground under two years of that work is being swapped out on an 11-week timeline. Watch DevDay on September 29 — what replaces the builders’ era will be on that stage.