The current migration path from Custom GPTs to Plugins creates a serious continuity problem for creators who use GPT links as public destinations.
Many Custom GPTs are already linked from Medium articles, GitHub repositories, websites, QR codes, documentation, bookmarks, newsletters, and search results. Those URLs are part of the published work itself.
The current documentation says GPT pages will become inaccessible at retirement, migration does not preserve sharing settings, and replacement plugins start private. There is also no documented permanent redirect from the old GPT URL to the migrated plugin.
That means a technically successful migration can still break the public distribution layer around the GPT.
Please consider preserving existing GPT URLs through permanent redirects, carrying forward public access settings where feasible, and providing a direct public landing page for migrated GPTs.
Plugins are useful as capabilities inside ChatGPT. Custom GPTs also function as public destinations. Preserving that second use case would prevent large amounts of existing published material from becoming stale.