The checklist
1. LIST YOUR GPTS. Which ones did you build, and which do you only use? You can only migrate a GPT you created. For someone else's, check the notice on it and ask the creator what replaces it.
2. PUBLISH YOUR LATEST EDITS FIRST. Migration uses the GPT's latest published version. Drafts and unpublished edits don't transfer. Publishing doesn't mean sharing it publicly.
3. SAVE A FEW PROMPTS YOU USE EVERY WEEK. You'll need them to compare the old GPT with the new plugin. OpenAI says a migrated plugin may respond differently.
4. MIGRATE. When it's available on your account: My GPTs > Migrate to plugin. The instructions become a skill, knowledge files are copied as reference files, and connected apps come across as apps.
5. TEST IT. Run your saved prompts and one harder case. Check it follows your instructions, uses the right files, and gives answers in the format your team needs.
6. REBUILD ANY CUSTOM ACTIONS. They don't transfer. Check whether an existing app does the job; if not, it may need a custom MCP server. Allow extra time for this one.
7. RE-SHARE IT. The plugin starts private. Sharing settings don't carry over and your team doesn't get access automatically. Share it, then ask one person to install and test it before everyone switches.
What else to know: after migration the original GPT becomes read-only and can't be deleted, so finish your edits first. It keeps working until retirement. Your old conversations don't move to the plugin, and the model you picked doesn't carry over. On 11 December 2026 custom GPTs and their pages become inaccessible.
Source: OpenAI Help Center, "Custom GPT retirement and migration FAQ", checked 30 Sep 2026. Migration may reach accounts at different times, so follow the notice in your own account.