1. Your migration record
Start here. Make one record for each GPT you own. It gives you somewhere to track the move, including the links you use to deliver a freebie or paid product.
GPT MIGRATION RECORD GPT name: Current link: Owner / person who can edit it: Account or workspace: Notice shown in that account: Migration option available? Yes / No / Unknown WHAT THIS GPT DOES The task it helps someone finish: A normal input: The output someone expects: MATERIAL TO CHECK Instructions saved at: Reference files saved at: Connected apps: Custom actions / integrations: Three example prompts and expected outputs: REPLACEMENT Plugin link: Who tested it: Their account type: Can they install / access it? Can they use the required apps? Result compared with original: Unresolved differences: DELIVERY LINKS Website / opt-in page: Checkout / product page: Welcome email / automated DM: Course / member lesson: Other places the old link appears: READY TO SHARE? Owner checked the result: Intended user tested access: Required integrations work: Delivery links checked: Date checked:
2. What OpenAI has announced
Existing GPTs still work until retirement. Custom GPTs are scheduled to retire on 11/12/2026, on every plan. After that date, GPTs and their GPT pages can’t be opened. Enterprise workspaces with an approved deferral get until 11/02/2027. OpenAI’s Enterprise timeline ends new GPT creation on 26/10/2026. These are OpenAI’s planned dates, so check your own account notice too.
The planned tool moves instructions into a skill and includes connected apps. Custom actions do not transfer: if your GPT pulls data in from another tool, you’ll need to rebuild that part with an available app or a custom MCP server. Check reference files; previous chats and conversation starters may not copy. The chosen model does not carry over.
After migration, the original becomes read-only until retirement. Replacement plugins start private. Old links are planned to redirect at retirement for people with access; a redirect does not grant access.
Read OpenAI’s current migration FAQ · Checked 27/09/2026.
3. Start the move when it is available
First, check whether migration is available in your account. Go to My GPTs and look for Migrate to plugin. It is rolling out, so if you can’t see it yet, it hasn’t reached your account.
Enterprise: the documented process
- Sign in as the GPT’s creator or a workspace admin. Plugins must be enabled.
- Open the published GPT. Drafts cannot migrate directly; published does not mean publicly shared.
- When Migrate to plugin appears in My GPTs, select it and follow the on-screen flow.
- Test the resulting plugin, then review sharing and customer access.
Personal account: follow your notice
OpenAI directs personal users to their in-app migration instructions. It has not documented a universal personal-account button sequence in this FAQ.
No migration option yet? Prepare your record below and keep using the existing GPT. In Enterprise, ask an admin to check availability, plugin settings and ownership.
OpenAI’s migration instructions and availability guidance.
Prepare the material with AI
Use this with material you own. It creates a preparation record and test cases; it does not perform the migration.
Help me prepare this GPT for migration. Use the instructions, file list and example outputs I provide below. Make a table with: component, where it lives, what I need to check, and any missing information. Separate reusable instructions, reference files, connected apps and custom actions. Write five test cases for the replacement: three normal requests, one request missing information, and one request outside the GPT's purpose. For each, describe what a useful response must contain. Do not claim the GPT has been migrated or that customer access works. Mark anything you cannot verify as unknown. Ask me for missing material instead of inventing it. MY MATERIAL: Paste the GPT instructions, file list and example outputs here.
4. Test the replacement
Use the same input in the original and the replacement. Record what changed.
| Test | Example: a content-planning GPT | Pass when |
|---|---|---|
| Normal request | Plan three posts using a supplied offer brief. | Each post matches the brief and requested format. |
| Missing details | Ask for posts without supplying the offer. | It asks for the missing details instead of inventing an offer. |
| Reference material | Include an exact phrase from your supplied brand guide. | It uses the correct material and wording. |
| Customer access | An intended user opens the replacement on their account. | They can access it and complete the task. |
| Connected tool | Try an action your workflow needs, with a harmless sample. | The authorised action completes and the result is checked. |
These are example tests. Replace them with the actual result your GPT promises. Keep an unresolved item open until you have evidence it works.
5. If it is a lead magnet or paid product
Check the delivery path using your migration record: opt-in or checkout, message containing the link, access on the intended account, then the task itself.
- Record everywhere you placed the original link.
- Keep screenshots of your test result and the account type used.
- Prepare the replacement link, but send it only after access is confirmed.
- If the replacement cannot deliver the promised task, record the gap and decide how you will support affected users.
For example, if your freebie promises a personalised content plan, test whether a new subscriber can actually produce one. Seeing the plugin on your own account is only the first check.
Useful next document: a short update stating what is changing, what works now, and when you will provide a tested replacement.
Build with me inside Wright Mode
AI training and practical resources for your business.
Explore the membership