Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- September 22 is the target date for the Enterprise migration experience, October 26 is the planned cutoff for creating new GPTs, and December 11 is the planned date when custom GPTs stop operating. Plans may change; a date does not prove availability for every account.
- Stopping creation is different from stopping operation: existing GPTs remain usable until their applicable retirement date. After migration, the original GPT still runs but becomes read-only; maintain subsequent changes in the replacement plugin.
- The planned Enterprise process requires a published GPT and migration by its creator or a workspace administrator. Unpublished drafts cannot migrate directly, and publishing does not mean public sharing.
- Migration uses the latest published version: instructions become a skill, connected apps join the plugin, and knowledge files are copied as reference files. Custom Actions, old chats and conversation starters do not transfer automatically; the selected model is not inherited.
- Replacement plugins start private. Use, sharing, installation and app authorization have separate permissions. All plans are in scope for retirement, but check availability milestones against each account or workspace’s notices; PRODUCT_FIT=NONE.
Separate the three planned milestones from actual availability
As of September 19, 2026, the official migration FAQ had updated the Enterprise timeline: administrators were notified on September 11; September 22 is the target date for the Enterprise migration experience; October 26 is the planned cutoff for creating new GPTs; and December 11 is the planned date when custom GPTs stop operating. Dates may change, and no exact time or time zone was given for each milestone. The former September 17 and September 25 schedule should no longer be used as operational deadlines.
OpenAI says retirement affects all ChatGPT plans. Specific migration entry points and schedules still depend on account or workspace notices. Do not interpret the Enterprise target as availability for every personal, Business or Edu account, or assume that access to an old GPT gives access to its replacement plugin.
Inventory creation location, creator and purpose, not just GPT links
List the GPTs you actually depend on, their creator accounts and workspaces, maintainers, users, essential instructions, reference material, Actions and several familiar test questions. Check workspace notices, plugin permissions and sharing recipients with administrators. For unpublished drafts that genuinely need migration, official guidance is to complete necessary edits and publish before the planned creation cutoff. Publishing for migration does not require public sharing.
This is a preparation checklist, not evidence that the migration button is available. For GPTs with unknown owners, only an old link or sensitive integrations, ask the creator or administrator to confirm permissions and retention arrangements first. Do not publicly share unreviewed content to meet a planned milestone.
If the migration entry point is missing, check eligibility rather than assuming the GPT is gone
Once the migration experience is available, look for Migrate to plugin in My GPTs. The published GPT’s creator or a workspace administrator must perform migration; usage access alone is insufficient. If the button is missing, check account or workspace availability, plugin settings, publication status and role permissions. Do not infer that the old GPT has been deleted.
Existing GPTs continue operating until their applicable retirement date under their original permissions. After migration, the original GPT becomes read-only and its creator cannot delete it; update the plugin from then on. The planned October 26 creation cutoff does not mean existing GPTs are deleted that day.
Separate automatic conversion, required rebuilding and items to review
Migration uses the latest published version; unpublished edits and drafts are not included. Instructions become a skill in the plugin, connected apps are added, and knowledge files are copied as reference files. Conversation starters and past conversations are not copied, the old GPT’s selected model is not inherited, and Enterprise uses default settings. Check file completeness, tool permissions and answer behavior after migration.
Custom Actions do not transfer automatically through migration. Maintainers and technical and security teams must assess supported connectors or custom MCP servers for workflows that depend on old Actions, then revalidate authorization, output and failure handling. Rebuilt integrations are not guaranteed to provide every capability of the original Action.
Validate the replacement workflow before reopening sharing
Choose several everyday questions and at least one difficult case. Compare whether the plugin selects the correct skill, follows key instructions, cites expected material, generates complete files or answers and can invoke required tools. Resolve business-impacting differences before switching original users. This reveals behavioral changes better than checking installation alone.
Replacement plugins start private and are not automatically installed or shared. Sharing with members or groups, publishing to a workspace directory, using plugins and installing them are each subject to permissions and policies; included apps require their own authorization. Do not rely on old links to switch users automatically. Explicitly provide the replacement entry point and have target users verify visibility and necessary operations in their own accounts.
What cannot yet be treated as final
As of September 19, 2026, these are the current official plans and migration boundaries. This article has not tested availability, conversion quality or specific costs in any workspace. Near September 22, October 26 and December 11, recheck the official FAQ and in-product notices. If planned dates change, adjust arrangements to the new applicable notice.
PRODUCT_FIT=NONE: this change concerns product eligibility, content conversion and workspace permissions. Network egress or a fixed IP cannot restore an unavailable migration button, bypass administrator settings or preserve custom Actions.
Sources
Frequently Asked Questions
Why is the migration button still missing after September 22?
September 22 is the Enterprise target date, not a guarantee of simultaneous availability for every account. Check workspace notices, plugin settings, GPT publication status and whether you are its creator or an administrator. Other plans should follow their own notices.
Will the October 26 creation cutoff delete existing GPTs?
Stopping creation and stopping operation are separate milestones. The current official plan keeps existing GPTs running until the applicable December 11 retirement date, under their existing permissions. These dates may still change.
Do drafts, custom Actions and old chats fully migrate to plugins?
Unpublished drafts and edits cannot migrate directly; migration uses the latest published version. Custom Actions, past chats and conversation starters do not transfer automatically. Knowledge files are copied as reference files and should still be checked individually.
Will migrated plugins automatically become available to the original users?
No. Replacement plugins start private and are not automatically shared or installed. Usage and app authorization have separate permission controls. Provide the new entry point explicitly and have target users verify it.