OpenAI has set a date for Custom GPTs. On December 11 they retire, and every GPT you built for proposals, onboarding or your content week has to move somewhere new.
Most of it moves on its own, which is the good news. The fine print is where people will get caught, because a GPT you only use and did not build cannot come with you at all.
Ten weeks is plenty of time. It is also exactly the kind of deadline that shows up on December 10.
The AI Move
Start with a list. Open ChatGPT, go to your GPTs, and write down every one you touch in a normal week. Then sort them into the ones you built and the ones someone else built.
The ones you built mostly migrate for you. Your instructions become a skill inside a new plugin, your knowledge files become reference files, and your connected apps come along. Three things stay behind: the model you picked, your old conversations, and any custom actions, which you rebuild by hand.
The ones someone else built are the real risk. If a GPT from a program you bought runs part of your week, ask the creator now whether a replacement is coming, and save anything you rely on out of those chats before it disappears.
Then do the part that outlasts this deadline. Copy each GPT’s instructions and files into your business folder, the same one we have been building over the last few weeks. The folder becomes the home, and ChatGPT, Claude or whatever comes next reads from it. The next time a tool changes its rules, the thinking behind your system is already sitting somewhere you own.
Before December, run the three prompts you use most in the old GPT and the new version side by side. If the answers drift, check the model setting first, since that one does not carry over.
One afternoon this month saves you a scramble on December 10.
This week’s prompt
Paste this into ChatGPT or Claude. It will sort your GPTs by risk, turn each one into a file you own, and give you the tests to run before the deadline.
ROLE: You are helping me move my Custom GPTs before OpenAI retires them on December 11, 2026.
CONTEXT: Here are the GPTs I built, with the name, full instructions and knowledge file list for each: [paste]. Here are the GPTs someone else built that I use, and what I use each one for: [list].
REQUEST:
1. Rank every GPT by how much my business depends on it, most urgent first.
2. For each GPT I built, rewrite the instructions as one clean markdown file I can keep in my business folder. Keep my wording where it works and flag anything vague.
3. For each one, tell me which pieces carry over to the new plugin and which I need to rebuild. Include any custom actions and the model setting.
4. For each GPT I only use, tell me what I lose on December 11 and sketch the instructions for a version of my own that covers the job I use it for.
5. Write three test prompts per GPT so I can compare the old and new versions before the deadline.
If anything is missing, ask me one question at a time before you start.
If you would like company while you move all this, the Unstoppable Community opens in Q1 2027 and the waitlist is open now. Early names help decide what gets built first. Join at theunstoppableai.com/community.