Short answerSave instructions and files, list your Actions, write test questions, then migrate and compare answers. Finish edits to the original before migrating, because it becomes read-only afterward.
Before you migrate
- Confirm who the GPT is for and how it is shared.
- Copy the full instructions to a text file.
- Collect the original knowledge files in one folder and note any outdated ones.
- List every Action: endpoint, authentication and what the instructions tell the GPT to use it for.
- Note conversation starters and the description.
- Write 10 real test questions, including one hard case, and save the current answers.
- Check you have the permissions needed to migrate (creator or admin, GPT published).
- Finish any edits to the original GPT.
During migration
- Move instructions first, then files, then connections.
- Rebuild Actions as a separate task. They do not transfer through OpenAI's migration.
- Re-check the model and capability settings, because they may not carry over.
After migration
- Run your test questions and compare tone, accuracy and refusals.
- Test every connected tool end to end.
- Share with the right people and confirm they can install or access it.
- Tell users where the new version lives and update saved links and onboarding material.
- Keep your backup folder until you are sure nothing was lost.
The common mistakes page covers what usually goes wrong, and testing has the scorecard.
Check your GPT before you move it
Paste your instructions, file names and Actions schema into the free checker. It runs in your browser and builds a portable bundle. Nothing is uploaded.
Open the free checkerRelated guides
Sources
- ChatGPT Learn: Moving your custom GPT workflows to plugins
- OpenAI Help Center: Custom GPT retirement and migration FAQ
Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.