ALL USERS: How do I migrate my custom GPTs to plugins in ChatGPT?

OpenAI is retiring custom GPTs in ChatGPT and replacing them with plugins. This applies to all ChatGPT plans, including BSU’s ChatGPT for Business.

Note: These instructions are written for BSU’s ChatGPT for Business plan. Steps may differ on other ChatGPT plans.

Plugins work much like GPTs. You can share a plugin only with members of BSU's ChatGPT for Business plan.

Key dates

  • October 26, 2026 (BSU recommended deadline): Publish any GPT you want to keep. OpenAI plans to end new GPT creation on this date for Enterprise plans but hasn’t announced a date for ChatGPT for Business. We recommend treating October 26 as your deadline in case our plan follows the same schedule.
  • December 11, 2026: Custom GPTs stop working on all ChatGPT plans, including ours, and links to them no longer open. Your past conversations stay in your chat history.

Who needs to migrate

  • If you created a GPT: You must migrate it to a plugin before December 11 to keep using it. Only the GPT’s creator can migrate it.
  • If you use a GPT someone else created: You can’t migrate it yourself. Ask its creator when a replacement plugin will be available.

Before you migrate

  • Finish your edits: After migration, the original GPT becomes read-only. We recommend finishing any edits and republishing your GPT before you migrate. You can also migrate first and edit the plugin afterward (see Edit your plugin or add reference files below).
  • Publish your GPT: Migration uses the GPT’s latest published version. If it’s already published and you haven’t changed it since, then you don’t need to republish it. Drafts and unpublished edits do not transfer. If your GPT has never been published, or if you changed it after publishing, then select Publish with access set to Only me.

Find your GPTs

  1. Sign in to ChatGPT for Business with your BSU credentials.
  2. In the left sidebar, select the three-dot (…) icon, then select GPTs (or Explore GPTs).
    ChatGPT navigation sidebar menu showing the highlighted option GPTs.
  3. Select My GPTs to see the GPTs you created.

Migrate your GPT to a plugin

  1. In your list of GPTs, select Migrate to plugin next to the GPT you want to migrate.
    My GPTs dashboard showing a list of custom GPTs with a highlighted Migrate to plugin button next to Article Buddy.
  2. A window summarizes what will migrate. Your instructions become a skill, and your knowledge files become reference files. Select Migrate to plugin to confirm.
    Migration modal titled Migrate Article Buddy highlighting the black Migrate to plugin confirmation button.
  3. Select Try in chat to test the plugin.
    Confirmation banner showing Your plugin was successfully migrated above the Article Buddy plugin details page.

What doesn’t carry over: Custom actions, the selected model, and sharing settings. Your new plugin is private until you share it. Your past conversations with the GPT stay in your chat history, even after retirement.

Edit your plugin or add reference files

After migrating, make all future changes in the plugin. You edit a plugin by asking Plugin Creator in a chat.

  1. Open a new chat, type @Plugin Creator, then type @ followed by your plugin’s name. You can also open your plugin and select Edit Plugin, which starts the request for you.
  2. To add or replace a reference file, select + or Files and attach the document.
  3. Describe the change: name the file or behavior to change, explain what you want, and say what should stay the same.
  4. Send the message, then review the plugin’s updated instructions and files.
  5. Test the plugin in a new chat, using a few prompts you used with your GPT.

Example change that adds a new file for your plugin to use as instructions:

@Plugin Creator Edit @[plugin name] to add the attached [file name] as a reference file. Use it when [describe when to use it]. Keep the other reference files and instructions unchanged. Tell me what you changed.

Making several changes: You can request several related changes in one message. Make larger or unrelated changes one at a time and test in between, so you can tell which change caused an unexpected problem.

Replacing a file: To replace an outdated file, name the old file and explain how the new one should be used. Otherwise, the plugin may keep both versions and could still use the old one.

Choosing files: Only upload files that are appropriate for everyone you plan to share the plugin with. People who use a shared plugin may see content from its reference files.

If an edit doesn’t finish: If an edit is still running after several minutes or shows an error, stop it, check whether your plugin changed, and try a smaller change. If it still fails, contact the IT Help Desk.

Share your plugin with members of your plan

You can share a plugin only with members of BSU's ChatGPT for Business plan. It can’t be shared with BSU users in other ChatGPT plans or those with personal ChatGPT accounts (Free, Plus, or other individual plans).

Your plugin is private by default, so only you can use it. To share it:

  1. Test the plugin to make sure it works as expected.
  2. Open the plugin, select Share plugin, and choose who in the plan can access it.
  3. Ask one member to install and test the plugin.
  4. Tell everyone who used your GPT where to find the plugin.

Note: Sharing settings from your GPT don’t carry over during migration. Even if your GPT was shared with everyone in the plan, no one else can use the plugin until you share it. If Share plugin is unavailable, contact the IT Support, since sharing may need to be turned on by a workspace admin.

Need help?

IT is available to support you through the migration. Contact itsupport@bridgew.edu.

Print Article