Clarification needed: Custom GPT migration path for personal Plus accounts

GPT builders
, , , ,
1

The new Custom GPT retirement FAQ explains that GPTs will migrate to Plugins, and that for personal accounts users should follow the migration instructions provided through an “in-product notice”.

However, I’m having trouble understanding what the replacement workflow will actually look like for a personal ChatGPT Plus account, especially because some of the current Plugin, Skill and MCP capabilities appear to depend on plan/workspace type.

Could OpenAI clarify the following?

  1. Migrated GPT without Custom Actions

If a personal Plus user’s GPT contains only instructions and knowledge, the FAQ says that its instructions will become a Skill inside the migrated Plugin.

Will the resulting Plugin be usable normally in ChatGPT web/mobile as well as desktop, or will it be treated as a local/Codex plugin?

Will a Plus user also be able to edit and maintain the Skill contained in that migrated Plugin, even if standalone Skill creation is not otherwise available on Plus?

  1. Creating new Plugins on Plus after GPT retirement

After Custom GPT creation is retired, will a Plus user be able to create a new private Plugin directly for personal use in ChatGPT web, desktop, Codex, or all of them?

  1. GPTs that currently use Custom Actions

The FAQ says that Custom Actions are not migrated and must instead be rebuilt using a supported connector or a custom MCP server.

What is the supported path for a personal Plus user whose GPT currently relies on a Custom Action?

Will personal Plus accounts eventually be able to register a private custom MCP app/server in ChatGPT, or would such a workflow require upgrading to a Business/Enterprise/Edu workspace?

  1. Relationship between Plugins, Skills and Apps

Is the intended long-term model that:

  • a Skill contains reusable instructions/workflow logic;
  • a Plugin is the installable/distributable package that may contain one or more Skills and external integrations;
  • an App is a registered external integration, typically backed by MCP;
  • MCP is the technical protocol used for custom external tools/data?

If this is not accurate, it would be helpful to have an official architecture diagram or terminology clarification.

  1. Meaning of “in-product notice” for personal accounts

Does this simply mean that personal users will receive account-specific migration instructions later, or does it imply that the migration capability itself will be exposed directly in ChatGPT?

The main concern is that today a Plus user can have a fairly sophisticated Custom GPT with Actions, while the documented replacement capabilities do not yet appear to provide an obviously equivalent personal-account path.

Any clarification specifically for Plus and Pro personal accounts would be very useful.

2

Hi @simbon,

I recommend to check this post by Support if it might be of help: Please Don’t Retire CustomGpts: CustomGPTs and Neurodivergent Developers - #2 by OpenAI_Support

3

It looks like some of the questions above may end up being answered by the ongoing rollout of new functionality. Today, on my personal ChatGPT Plus account, a new “Skill” section appeared inside the Plugin tab; this was not present for me yesterday.

More importantly, the UI currently offers options to create a Skill with ChatGPT, create one with the editor, or upload one from the computer, and Work also exposes the @skill-creator workflow.

This suggests that the capabilities available to Plus accounts are still evolving as the GPT retirement/migration rollout approaches, so some of the limitations I mentioned in the original post may soon change. It will be interesting to see whether this becomes the supported replacement path for instruction/knowledge-based Custom GPTs on personal accounts, and how the remaining questions around Actions/MCP will be addressed.