Custom GPT migration checklist (Dec 11, 2026 deadline)

§ Checklist

The checklist

0 of 25 doneDownload the CSV templateTicks are saved in this browser only.

1. Inventory (this week)

List every custom GPT your team relies on, with its owner (the creator) and the workspace it was created in.
Note who uses each one: just you, named people, a group, the workspace, or the public.
Mark whether each GPT is published. Drafts and unpublished edits don’t transfer.
List its knowledge files and connected apps.
List every custom action and the service it calls. These do not transfer.
Note any model dependency. The selected model does not carry over.
Decide the destination for each: plugin (OpenAI’s path), Project, workspace agent, or retire.

2. Prepare

Finish essential edits now. The original becomes read-only once migrated.
Publish the version you want to keep. Publishing does not require sharing publicly.
Save five familiar prompts and one hard case per GPT, with the answers you expect.
Enterprise: confirm plugins are enabled and who holds Share plugins and Publish plugins to workspace.
Enterprise: if you want bulk migration, get a workspace Owner to pull the full GPT inventory through the ChatGPT Admin plugin.
Check your workspace notice for your date: December 11, 2026, or February 11, 2027 for FedRAMP and approved deferrals.

3. Migrate

In My GPTs, select Migrate to plugin and follow the steps.
Review the new skill (the old instructions) and the reference files (the old knowledge files).
For a Project instead: New project → paste instructions in Project settings → upload the files.
Rebuild each custom action on an existing app or a custom MCP server.

4. Test

Run the saved prompts. The right skill is selected and the instructions are followed.
The expected reference material is used.
Answers and files come out complete and in the required format.
Each rebuilt integration is tested on its own, reads before writes.

5. Share and switch

Share the plugin (Share Plugin can prefill the original GPT’s audience in managed workspaces). Review it and select Save.
Ask one real user to install and test the replacement.
Tell everyone who used the GPT which plugin or project replaces it, and by what date.
Make all future changes in the plugin, not the read-only GPT.

§ Migration triage

Get a fixed migration quote

Answer four questions and we’ll reply within one business day with a fixed fee and the earliest start date. Custom GPT migration is starting at $2,500. Appearly is not affiliated with OpenAI.

§ FAQ

Questions we hear

Is this checklist free?

Yes. Use it, print it, or share it. The CSV template has one row per GPT and a column for each check. Ticks you make on this page are stored only in your browser.

What is the deadline for migrating custom GPTs?

OpenAI’s standard retirement date is December 11, 2026. FedRAMP workspaces and Enterprise workspaces with a qualifying, approved deferral have until February 11, 2027.

Which GPTs should I migrate first?

Start the ones with custom actions now, because actions don’t transfer and have to be rebuilt on an app or a custom MCP server. Simple GPTs with only instructions and files migrate quickly.

Keep reading

Sources · checked November 13, 2026

OpenAI figures are OpenAI’s, quoted as published on the date checked. Appearly is not affiliated with OpenAI. ChatGPT is a trademark of OpenAI.