Migrate Your Custom GPTs to Plugins

Quick Links: | Article Summary | Before You Migrate | Migrate Your Custom GPT | Review What Will Migrate | Test the Migrated Plugin | Share the Migrated Plugin | What Does and Does Not Transfer | Additional Resources |

Article Summary  

OpenAI is retiring Custom GPTs and providing a built-in process to migrate GPTs you created into plugins. During migration, ChatGPT converts supported parts of your GPT into the new plugin format and identifies features that may require additional attention.

After migration, you should test the plugin before using or sharing it. The migrated plugin starts private, and existing GPT sharing permissions do not automatically transfer.

Before You Migrate  

Before beginning the migration, review the GPT and make any final changes you want to preserve.

  • The migration uses the GPT's latest published version.
  • Draft or unpublished changes do not transfer.
  • You must be the GPT's creator or, where supported, a workspace administrator with permission to migrate it.
  • Plugins must be enabled for the migration option to be available.
  • Custom actions do not automatically transfer and may require a replacement integration.

Consider saving several prompts you commonly use with the GPT. You can use these prompts after migration to compare the behavior of the new plugin with the original GPT.

Migrate Your Custom GPT  

  1. Sign in to ChatGPT using the account and workspace where the GPT was created.
  2. Open GPTs from the left side navigation menu.
  3. Select My GPTs in the upper right.
  4. Locate the GPT you want to migrate.
  5. Select Migrate to plugin for that GPT.

My GPTs page in ChatGPT showing three custom GPTs under “Created by me.” Each GPT has a “Migrate to plugin” button, along with edit and delete icons.

If you do not see the migration option, confirm that you are in the workspace where the GPT was created, that the GPT has been published, and that plugin access is enabled for your account.

Review What Will Migrate  

  1. After selecting Migrate to plugin, review the migration summary displayed by ChatGPT.
  2. Review each section carefully to understand which GPT features can be migrated automatically and which may require additional work.
  3. Pay particular attention to integrations, custom actions, reference material, and other features identified as requiring review.
  4. Continue through the migration process to create the replacement plugin.

ChatGPT migration dialog for a custom GPT. The dialog states that the GPT will be turned into a plugin using its instructions and knowledge files, will start private, and cannot be edited after migration. Status sections show “Instructions and files: No issues found,” “Apps and actions: No issues found,” and “Access and sharing: Sharing enabled,” with migration in progress.

The exact wording and categories shown in the migration summary may change as OpenAI updates the migration experience. Follow the information presented in ChatGPT for the GPT you are migrating.

Test the Migrated Plugin  

A migrated plugin may not behave exactly like the original GPT. Test it before making it available to other users.

  1. Open the migrated plugin.
  2. Review its migrated instructions and reference files.
  3. Run several prompts that you previously used successfully with the original GPT.
  4. Test at least one more complex task that exercises the GPT's primary workflow.
  5. Confirm that the plugin:
    • follows the expected instructions;
    • uses the expected reference material;
    • produces the expected type and format of response; and
    • has access to any tools or integrations required by the workflow.
  6. Correct any migration issues before sharing the plugin with other users.

After migration, the original GPT remains available until OpenAI retires Custom GPTs, but the migrated GPT becomes read-only. Future changes should be made to the replacement plugin.

Share the Migrated Plugin  

Migration does not preserve the GPT's existing sharing settings. The migrated plugin starts private, even if the original GPT was previously shared with other Chico State users.

  1. Finish testing and validating the migrated plugin.
  2. Open the plugin's sharing options.
  3. Configure access for the appropriate people, groups, or workspace audience.
  4. Have an intended user confirm that they can access and use the replacement plugin.

Do not assume that users who could access the original GPT automatically have access to the migrated plugin.

What Does and Does Not Transfer  

OpenAI currently documents the following migration behavior:

  • GPT instructions: Converted into a skill within the new plugin.
  • GPT knowledge files: Copied into the plugin's reference files.
  • Connected apps: Added to the plugin as apps when supported.
  • Selected GPT model: Does not transfer.
  • Custom actions: Do not automatically transfer and may need to be rebuilt using a supported app or integration.
  • Existing GPT conversations: Do not transfer to the plugin.
  • Sharing permissions: Do not transfer. The migrated plugin starts private.

Review the migration summary for each GPT because the features used by individual GPTs may differ.

Additional Resources  

 Still need help? Open a AI Support/Feedback ticket for further troubleshooting.
  
 Please do not leave the comment section blank! Provide constructive feedback to make this page better.

Print Article