Skip to content
InvokeRank
Index snapshot 1 Oct

Move your custom GPT before 11 December

Custom GPTs become plugins. Instructions and knowledge move; custom Actions do not. Source: OpenAI’s Custom GPT retirement FAQ, 11 Sep 2026.
26 Oct 2026Enterprise workspaces stop creating new custom GPTs (planned)
11 Dec 2026Custom GPTs retire on every plan and leave the GPT directory
11 Feb 2027Retirement for Enterprise workspaces with an approved deferral

What moves to the plugin

In the GPTIn the pluginState
InstructionsA skill inside the pluginCarries over
Knowledge filesReference files in the skill; retrieval can differCheck
Conversation startersDo not transfer; save them as starter promptsCheck
Selected modelDoes not carry over; workspace defaults applyCheck
Custom ActionsDo not transfer; rebuild as an MCP serverAction needed

How Actions become MCP tools, step by step: GPT Actions to MCP.

Check your GPT

Copy each field from the GPT editor’s Configure tab. Nothing you paste is stored.
Only the names are read. The files stay on your computer.
Capabilities turned on
Custom ActionsNo Actions. Add one for each schema in the GPT editor.