migration
Every record this desk has filed under migration, newest first, each with the number of sources it can still show you.
OpenAI has scheduled custom GPTs to retire on December 11, 2026 across ChatGPT plans, and a rewrite of its migration FAQ that no release note mentions moved the Enterprise cutoff for creating new GPTs from September 25 to October 26 and removed a sentence saying migrated GPT links were planned to redirect to their replacements.
OpenAI's help center says custom GPTs are scheduled to retire on December 11, 2026, that the transition affects all ChatGPT plans, and that Enterprise workspaces with an approved deferral get until February 11, 2027. At retirement, GPTs and their pages become inaccessible. The replacement is a plugin: migration turns a GPT's instructions into a skill and copies its knowledge files, but custom actions, past conversations, sharing settings and the selected model do not carry over, and the original becomes read-only. This desk compared the migration FAQ as read on September 27 with Internet Archive copies from September 17, 18 and 25. Between September 16 and September 25 it was rewritten with no release-note entry: the Enterprise cutoff for creating new GPTs moved from September 25 to October 26, the migration target from September 17 to September 22, and a sentence saying migrated GPT links were planned to redirect was removed. Two other OpenAI help articles still give the September 17 target. On personal Free, Go, Plus and Pro accounts, new GPTs already cannot be created or published.
Also filed underopenaichatgptcustom-gptsretirementspluginsdated-terms
The most important column in a deprecation notice is the one nobody reads
A deprecation table encodes two completely different events in one shape. 'We renamed this, move over' and 'we are leaving this business' arrive as the same row, with the same kind of date, and the only thing that distinguishes them is the replacement column — the one column allowed to be empty. Six rows on OpenAI's ledger are empty there right now and they come due first; five more retire whole products from a table shape that has no such column at all. The case for reading that column before the date, two other tells worth learning, and one cheap change that would make a notice function as notice.
Also filed underdeprecationsplatform-riskopenaimethodology
OpenAI's deprecation ledger carries fifty-four dated shutdowns. Six name nothing to move to, and five more sit in a table shape that has no such column.
Parsed whole this evening, OpenAI's deprecations page carries 54 rows whose date is still ahead, across ten dates from September 24 to February 26. Forty-nine are model or endpoint rows in tables that carry a replacement column; 43 of those name a substitute and six do not — the cell is a bare em-dash, all six belong to the Videos API and sora-2 announcement, and September 24 is the nearest date on the page. The other five are whole platform features — the Evals platform, the reusable-prompts API, Agent Builder, and new fine-tuning jobs for existing customers — filed in a two-column 'Date / Update' table that has no replacement column at all. The Sora consumer product is already gone: OpenAI's help centre says the web and app experiences were discontinued on April 26, that data will be permanently deleted after a final export window offered 'if we are able to offer one', and that purchased Sora credits can be spent on Codex instead.
Also filed underopenaideprecationsdeadlinessoraapi
A record appears here because it carries migration in its own tags. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.