The best custom GPT migration options, in order.

Stay in ChatGPT

In the order OpenAI presents them: the official path first.

1. 01

   Migrate to plugin (OpenAI’s official path)

   Built-in migration

   Best for: Shared GPTs other people run: proposal writers, policy helpers, support triage.

   • Go to My GPTs and select Migrate to plugin. Instructions become a skill, knowledge files become reference files, and connected apps carry over.
   • Migration uses the latest published version. Custom actions, the selected model and sharing settings don’t transfer; the plugin starts private.

   Watch out: Rebuild custom actions before you switch people over.

   Sources: OpenAI Help Center: Custom GPT retirement and migration FAQ · ChatGPT Learn: Moving your custom GPT workflows to plugins

2. 02

   Move it to a Project

   OpenAI’s named alternative

   Best for: GPTs you used for your own ongoing work with the same instructions and files.

   • OpenAI names a Project as the alternative when the GPT mainly kept instructions and files together.
   • Paste the instructions into Project settings and upload the files. Custom actions and sharing settings don’t transfer, and old chats can’t be moved in.

   Source: OpenAI Help Center: Custom GPT retirement and migration FAQ

3. 03

   Rebuild custom actions as an MCP server

   Developer route

   Best for: GPTs that called your own API through a custom action.

   • Custom actions don’t transfer through the migration workflow. OpenAI points to an existing app or a custom MCP server as the replacement.
   • OpenAI’s developer docs cover building an MCP server and packaging it as a plugin.

   Watch out: OpenAI warns not to assume a rebuilt integration has every capability of the original action. Test reads before writes.

   Sources: OpenAI Help Center: Custom GPT retirement and migration FAQ · OpenAI developers: Build an MCP server

4. 04

   Rebuild it as a workspace agent

   Separate product (Business, Enterprise)

   Best for: Work that should run on a schedule, from Slack, or from an API call.

   • Workspace agents are a separate product for ChatGPT Business and Enterprise, not OpenAI’s migration target.
   • Rebuild the GPT on purpose if a scheduled or triggered agent fits the job better than a plugin.

   Source: OpenAI Help Center: ChatGPT workspace agents for Enterprise and Business

Leave or let go

1. 05

   Move to another assistant

   Outside ChatGPT

   Best for: Teams that already live in Microsoft 365, Google Workspace, Claude or Perplexity.

   • Copy the instructions and knowledge files before December 11, then rebuild in the other tool.
   • We compare the options, with each vendor’s own docs, in custom GPT alternatives.

   Source: Appearly: custom GPT alternatives

2. 06

   Retire it on purpose

   Do nothing, deliberately

   Best for: GPTs nobody has opened in months.

   • Custom GPTs and their GPT pages become inaccessible on December 11, 2026 (February 11, 2027 for FedRAMP and approved-deferral Enterprise workspaces).
   • Existing conversations stay accessible, and OpenAI says you can still migrate a GPT after retirement.

   Watch out: Tell the GPT’s users before the date.

   Source: OpenAI Help Center: Custom GPT retirement and migration FAQ

Get help

1. 07

   Appearly custom GPT migration

   Done-for-you service

   Best for: Teams with many GPTs, or GPTs with custom actions, and little time before December 11.

   • Starting at $2,500 as a fixed fee after a short review. Our free migration checklist covers the same steps if you’d rather do it yourself.

   Watch out: Listed last because every option above is free to do yourself.

   Disclosure: this is our own service. Appearly (appearly.app) publishes this list. We included ourselves under the same criterion as everyone else, and nobody paid to be listed.

   Source: Appearly pricing