Short answerList every GPT with its owner, purpose, users, files, Actions and sharing, then decide: migrate now, migrate later, retire or ignore. Fix the important ones first.
Template (copy into a spreadsheet)
| Column | What to write |
|---|---|
| GPT name and link | As it appears in My GPTs |
| Owner | Creator (needed to migrate) |
| Purpose | One sentence |
| Users | How many, who |
| Knowledge files | Count and key names |
| Actions | Yes/no and which services |
| Last edited | Date |
| Decision | Migrate now / later / retire |
| Destination | Plugin / other platform / hosted |
How to decide
- Used weekly by customers or the team: migrate first.
- Has Actions: schedule extra time.
- Unused for months: retire it, but save the instructions.
For org-wide timelines see the countdown plan, and for client work the agency process.
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
Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.