Somewhere in your link-in-bio, your welcome email, your course bonus page or your onboarding doc, there is probably a link to a Custom GPT you built. A mini-you. A free lead magnet. A client intake bot.

That link has an expiry date now.

OpenAI has scheduled Custom GPTs to retire on December 11, 2026, and its retirement FAQ says the change affects every ChatGPT plan. The old GPT link stops working on 11 December, which means every place you ever published it quietly becomes a dead end unless you do something first.

The replacement is a plugin. OpenAI is retiring Custom GPTs and replacing them with plugins built around reusable skills, reference files and connected tools. Most of what you wrote survives the move. The part coaches actually monetised mostly does not.

The dates

Custom GPTs are scheduled to retire on Dec 11, 2026. For affected Enterprise workspaces with an approved deferral, the retirement date is Feb 11, 2027, and that extension applies only to workspaces with a qualified, approved deferral.

The creation cutoff is messier and depends where you sit. Custom GPTs are scheduled to go away for good on Dec. 11, 2026, while OpenAI's current Enterprise schedule ends creation of new ones on Oct. 26; individual workspaces can see different timing. Michigan State's IT desk tells its ChatGPT EDU users migration rollout began on September 22, 2026, and new Custom GPTs can no longer be created after October 26, 2026. OpenAI notes the dates are subject to change.

Translation for a solo coach: don't plan around the fine print. Plan around December 11.

What survives, and what quietly doesn't

The "Migrate to plugin" button moves your GPT's name, instructions, knowledge files and connected apps. It leaves behind Custom Actions, sharing settings, the selected model, conversation starters and capability settings.

Read that second sentence again, because it contains four separate problems.

Conversation starters. They do not transfer one to one. Those four suggested prompts were the onboarding for everyone who had never used your tool before. They were the reason a cold prospect got a good first answer instead of a blank box.

Capabilities. Web search, images and data analysis are not guaranteed to carry across, and each one needs testing. If your "content idea machine" quietly relied on browsing, assume it's broken until you've proven otherwise.

The model. The model selected for the original GPT does not transfer. Anyone who spent an afternoon tuning tone against a specific model is retuning it.

Custom Actions. This is the one that bites consultants. Custom actions connected a GPT to external services; in a plugin, apps connect to services and supported actions, and GPT custom actions need to be rebuilt separately. OpenAI says a rebuild "may require a custom MCP server and technical setup", and that a rebuilt version shouldn't be assumed to do everything the original did.

If your GPT pushed a lead into your CRM, booked a call, or wrote a row into a spreadsheet, that's not a migration. That's a rebuild project.

The expensive part is sharing

Here is the line that should go on a sticky note. OpenAI's migration FAQ states: "Migration doesn't carry over your GPT's sharing settings or give existing users access to replacement." Anyone using your GPT today needs a fresh invitation to the plugin once one exists.

The new plugin is private, and making it public takes a separate review by OpenAI. A migrated personal plugin starts private, and making it public requires a separate plugin submission process.

So the free GPT you've been using as a top-of-funnel giveaway does not reappear as a free public plugin on December 12 by itself. You migrate it, then you queue up for a review you don't control the timing of.

Three other traps worth knowing:

You can only migrate a GPT you created. If you sold a programme that included "my private GPT" built inside a client's workspace, you may not be the one holding the button.

Only the latest published version migrates. Unpublished edits are lost. Those tweaks sitting in draft since August go in the bin.

The original GPT stays usable until retirement, but becomes read-only after migration and its creator can no longer delete it. Migrate in haste and you've frozen the version your audience is still using.

One piece of good news: your old chats with the GPT stay readable.

The 20-minute audit, this weekend

1. Open My GPTs. Write down every GPT you built, and next to each one, where its link is published. Bio. Lead magnet page. Email sequence. Course module. Proposal template. Slide 42 of your keynote deck.
2. Mark the ones that use a Custom Action. Those are rebuilds, not migrations. Price the work or kill the feature.
3. Separate what you built from what you recommend. You do not need to migrate a GPT you only use, permission to use it does not let you migrate it yourself, and access to the original does not automatically give you access to a replacement plugin. If you teach clients to use someone else's GPT, that lesson may expire without warning.
4. Migrate one, then test it as a stranger. Open My GPTs, select the GPT, choose Migrate to Plugin, and ChatGPT copies the instructions, apps and knowledge files into a plugin within a minute. After sharing, ask an intended user to install and test the replacement.
5. Fix the links. Update your docs, onboarding and saved bookmarks before the link does it for you.

If you run a team workspace, there's a shortcut with a catch: admins can migrate GPTs in bulk through the ChatGPT Admin plugin, but bulk migration does not copy sharing.

The wider lesson is one coaches have now learned on Instagram, on Facebook groups, on Clubhouse, and on whatever comes next. On December 11 Custom GPTs stop running and leave the GPT directory. That directory was free distribution. It was also someone else's shelf, and the shelf is being taken away with eight weeks' notice.

The coaches who'll barely notice are the ones whose GPT was a front door to an email list they own. The ones who'll feel it are the ones whose GPT was the product.