Your Custom ChatGPT GPT Is Being Retired. Here’s How to Move It to a Plugin Before It’s Gone
If you ever built one of those custom “GPTs” in ChatGPT — a specialized assistant trained on your own instructions and files — OpenAI wants you to know it’s going away. The company is retiring custom GPTs on December 11, 2026, and replacing them with a new format called plugins. If you created a GPT you still rely on, or your team uses one someone else built, there’s now a clear deadline and a specific migration path you need to know about.
This isn’t a vague “coming soon” warning. OpenAI has published exact dates, a step-by-step conversion process, and a detailed account of what carries over automatically and what you’ll have to rebuild yourself. Here’s what’s actually changing, who it affects, and how to move your GPT over without losing the work you put into it.
Photo: OpenAI / ChatGPT (learn.chatgpt.com) — official documentation graphic
What Happened?
OpenAI first flagged the change in an admin notice and release-note update on September 11, 2026, and has since published a full help-center FAQ and a detailed migration guide on its developer documentation site. The plan: custom GPTs — the feature that let anyone package instructions, uploaded files and connected tools into a shareable mini-assistant — are being folded into a broader, newer feature called plugins.
A plugin, per OpenAI’s own description, is “a reusable package for a workflow” that can bundle together:
- Skills — reusable instructions, essentially what a GPT’s custom instructions used to be
- Apps — connections to external services like Slack, Google Drive or Jira, replacing what custom GPTs did with “Actions”
The idea is that plugins work in both ChatGPT and OpenAI’s coding tool, Codex, and can be installed, shared and managed more like an app than a standalone chatbot persona.
Photo: OpenAI / ChatGPT (chatgpt.com/features/plugins) — official product graphic
There’s a wrinkle worth knowing up front: if you’re on a personal plan (Free, Go, Plus or Pro), you may have already noticed you can’t create a new custom GPT anymore. According to OpenAI’s help center, new GPT creation and publishing are no longer available on personal accounts — only Business, Enterprise and Edu workspace members with the right permissions can still build new ones, and even for them that door is scheduled to close on October 26, 2026 (planned). If you already have GPTs, though, nothing has been taken away yet — you can keep using and editing them until the retirement date.
The Key Details
Here’s what OpenAI has confirmed, straight from its official FAQ and migration guide:
| Milestone | Date | What it means |
|---|---|---|
| Admin notice to Enterprise workspaces | Sept 11, 2026 | Early heads-up for organizations to start planning |
| Migration experience target | Sept 22, 2026 | “Migrate to plugin” option starts appearing — not guaranteed for every account on this exact day |
| Delayed migration banner target | Oct 1, 2026 | For workspaces that opted into a later rollout |
| New custom GPT creation ends | Oct 26, 2026 (planned, Enterprise) | No more new GPTs can be created or published; editing existing ones is unaffected |
| Standard retirement | Dec 11, 2026 | Custom GPTs and their GPT pages become inaccessible |
| Deferred retirement | Feb 11, 2027 | Only for Enterprise workspaces with an approved extension |
A few things worth being precise about, since OpenAI’s own wording draws careful distinctions:
- The transition affects all ChatGPT plans, but the dated milestones above are published specifically for Enterprise workspaces. OpenAI says “other plans are expected to follow the same timeline,” so if you’re on Plus or Pro, watch for an in-product notice rather than assuming Dec 11 is locked in for you with the same certainty.
- Migration availability rolls out gradually. A target date doesn’t mean every account gets the “Migrate to plugin” button that day.
- This is separate from the creation freeze. Losing the ability to create new GPTs doesn’t affect GPTs you already built — you can keep editing and using those right up until retirement.
What transfers automatically — and what doesn't
This is the part that matters most if you’ve put real effort into a GPT. According to OpenAI’s documentation:
Carries over: – Your GPT’s published instructions → become a Skill in the new plugin – Uploaded knowledge files → copied into the plugin’s reference files – Connected apps (not custom Actions) → added to the plugin as apps
Does NOT carry over: – Custom Actions. If your GPT calls an external API or service through a custom Action, that integration has to be rebuilt — either using an app OpenAI already supports, or a custom MCP server. This is the single biggest piece of extra work for technically involved GPTs. – Existing conversations. Your chat history with the GPT stays where it is; it doesn’t move into the plugin. – The GPT’s selected model. The plugin uses default models (Enterprise workspace defaults apply in business settings), not whatever model your GPT was configured to use. – Sharing settings and conversation starters. The new plugin starts private by default, even if your original GPT was shared publicly or with a team. You have to re-share it, and example prompts don’t transfer one-to-one.
Only a GPT’s latest published version migrates — unpublished drafts are left behind, so finish and publish any pending edits before you migrate. Publishing doesn’t require making the GPT public.
Why It Matters
Custom GPTs became one of ChatGPT’s most popular personalization features after they launched in the GPT Store — everything from writing-style assistants to internal company tools got built this way. A lot of that work lives in instructions and files that took real time to tune. Losing access to it without warning would be a genuine problem for the people and small teams who depend on these GPTs for daily work.
To OpenAI’s credit, this isn’t a Twitter-announcement-and-silence kind of shutdown. The company has published a genuinely detailed FAQ, a step-by-step guide for both individual creators and workspace admins, and even an email template admins can send their teams. That level of documentation suggests OpenAI expects this migration to be bumpy for GPTs that rely on custom Actions or specific model choices, and wants to reduce the number of people caught off guard.
It’s also a signal about where ChatGPT is heading. Plugins are a broader, more “appified” concept than custom GPTs — a plugin can be installed, automatically triggered when relevant, and used inside Codex as well as chat. OpenAI appears to be consolidating several past extension mechanisms (custom GPTs, Actions, and earlier plugin concepts) into one unified system.
What It Means for You
If you created a GPT (personal accounts)
- Go to My GPTs and find your GPT under “Created by me.”
- Check for a “Migrate to plugin” option. If you don’t see it yet, migration may not have reached your account. Keep using your existing GPT in the meantime — it still works.
- Before migrating: publish any unfinished edits, and save two or three prompts you normally use (plus one harder, edge-case prompt) so you can compare results afterward.
- Migrate, then test. The conversion takes about a minute. Afterward, check that the plugin picks the right skill, uses your reference files correctly, and produces output in the format you expect — OpenAI explicitly warns “a migrated plugin may respond differently.”
- Re-share it. Your new plugin starts private even if the old GPT was public or shared with specific people. If others relied on your GPT, they’ll need access to the replacement separately.
- If your GPT uses a custom Action, budget extra time — that integration needs to be rebuilt, and OpenAI says this may require a custom MCP server depending on what the Action did.
If you only use someone else’s GPT
You don’t need to do anything to migrate it — only its creator or a workspace admin can do that. But you should check the GPT for OpenAI’s retirement notice and ask the creator about a replacement, since access to the original GPT does not automatically carry over to its plugin version.
If you manage a Business, Enterprise or Edu workspace
OpenAI has built an admin-specific workflow: you can use the ChatGPT Admin plugin to run a report of GPTs by recent usage, prioritize migrating the ones your team actually relies on, and even batch-migrate selected GPTs by asking the Admin plugin directly (for example: “Migrate [GPT IDs] to plugins, show me the selection and ask for confirmation first”). Built-in migration doesn’t require extra upload permissions, but sharing the resulting plugins with your team does — review your workspace’s “Share plugins” and “Publish plugins to workspace” permissions ahead of time. Sharing settings are not copied over in bulk migrations, so plan to re-share each replacement individually.
Photo: OpenAI (ChatGPT Help Center) — official documentation screenshot
What Happens Next?
A few open questions are worth watching:
- Exact dates for personal (Plus/Pro) accounts. OpenAI has only confirmed detailed milestones for Enterprise workspaces so far and says other plans are “expected to follow the same timeline” — a firmer personal-account schedule hasn’t been published yet.
- How well custom Actions translate. Since these don’t migrate automatically, the real test of this transition will be whether OpenAI’s existing apps and custom MCP servers can realistically replace what people built with Actions.
- Whether the Oct 26 creation freeze slips. OpenAI labels it “planned,” which leaves room for the date to move, as has already happened once with the migration-experience target.
Final Takeaway
If you have a custom GPT you actually use — whether it’s a personal writing assistant or something your team depends on — don’t wait for December. Check My GPTs now, note whether you have a “Migrate to plugin” option yet, and if you do, migrate and test it on a quiet day rather than scrambling in the first week of December. Pay special attention to anything built around a custom Action, since that’s the one piece of the puzzle OpenAI can’t move for you automatically. The underlying instructions and files that make your GPT useful aren’t disappearing — but the format they live in is changing, and the clock on that change is now running.
Sources
This article is based on OpenAI’s official Custom GPT retirement and migration FAQ, its migration guide for ChatGPT Work, its Plugins and Creating and editing GPTs help articles, the ChatGPT Plugins product page, and secondary reporting from Visual Studio Magazine, Ragan Communications, and EdTech Innovation Hub for additional context.