Skip to main content

Buyer guide

Custom GPTs to Plugins: Migration Checklist

How to inventory, migrate, test, and share the custom GPTs your teams rely on before custom GPTs retire.

Reading time
1 min read
Sources
7 cited
In this piece
ChatGPT+14 Mixed

Before you migrate a custom GPT, name its owner, test the plugin on real tasks, and confirm sharing works, because migration makes the original GPT read-only. OpenAI is retiring custom GPTs in favor of plugins, which package reusable skills and connected apps. Migration turns a GPT's instructions and reference files into a skill, and custom actions do not transfer.

When you need this

  • Teams run internal workflows, such as an HR policy assistant, on custom GPTs.
  • Your admins received the retirement notice for custom GPTs.
  • You sell or share GPT-based tools with people outside the workspace.

Evaluation criteria

  1. Inventory

    Which GPTs does the team rely on, and who owns each?

    Look forList each GPT's purpose and audience, along with its instructions, reference files, and integrations. Name an owner for each GPT. Use workspace analytics to prioritize the shared GPTs people open most.

  2. What transfers

    Which parts of each GPT need rebuilding?

    Look forInstructions and reference files become a skill. Connected apps stay part of the plugin. Replace custom actions with a supported app or a custom MCP server.

  3. Permissions

    Can the owner share or publish the plugin in your workspace?

    Look forCheck the owner's plugin sharing and publishing permissions before announcing the switch. A Business workspace owner reported that a migrated HR GPT stayed private because sharing was disabled.

  4. Testing

    Does the plugin produce the same outputs on real tasks?

    Look forSave test prompts and expected outputs. Run each prompt with the skill selected, then as a normal request. ChatGPT selects installed skills automatically only when the task matches.

  5. Access outside the workspace

    Do external users rely on a public GPT?

    Look forTest access for external users. Migrated personal plugins start private. An independent creator reported that paying customers lost access.

Questions to ask vendors

  1. When do custom GPTs stop working in our workspace?
  2. Who maintains each plugin after migration?
  3. Which custom actions need an app or MCP server, and who builds it?

Red flags

  • Migrating a GPT, which turns it read-only, before the plugin is tested.
  • No owner named for GPTs that many employees use.
  • Announcing the switch before confirming sharing permissions.

Products in this piece

Sources

Official documentation
4
Public source
3
  1. ChatGPT docs: Migrate custom GPTs to pluginsOfficial documentationlearn.chatgpt.com
  2. ChatGPT admin docs: ChatGPT Work overviewOfficial documentationlearn.chatgpt.com
  3. OpenAI: Enterprise privacy at OpenAIOfficial documentationopenai.com
  4. OpenAI Help Center: ChatGPT Business overviewOfficial documentationhelp.openai.com
  5. OpenAI Community: Migrated GPT is private in ChatGPT Business (Sep 25, 2026)Public sourcecommunity.openai.com
  6. OpenAI Community: Custom GPT to plugin migration raises access concerns (Sep 23, 2026)Public sourcecommunity.openai.com
  7. BBVA: BBVA is now using ChatGPT to streamline legal queries and marketing processes (Jan 7, 2025)Public sourcebbva.com