Migrating off ft-o4-mini-2025-04-16 — retirement date and replacement
OpenAI is retiring ft-o4-mini-2025-04-16 on 2026-10-23 — in 85 days. The provider’s documented replacement is gpt-5.6-terra. This page is built from OpenAI’s official deprecation notice and is rechecked weekly; the source link is below.
When is ft-o4-mini-2025-04-16 being deprecated?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| ft-o4-mini-2025-04-16 | OpenAI | 2026-10-23 | gpt-5.6-terra |
Source: OpenAI deprecation notice · announced 2026-04-22
What should I migrate ft-o4-mini-2025-04-16 to?
OpenAI documents gpt-5.6-terra as the successor. Migrating within the same provider keeps your endpoint, authentication and region behaviour unchanged — the measured latency below does not move when you switch models on the same host.
Measured latency of the OpenAI API host
| Region | p50 TTFB | p95 | Uptime | Probes |
|---|---|---|---|---|
| Asia (Tokyo) | 198 ms | 273 ms | 100% | 289 |
| Europe (Germany) | 290 ms | 402 ms | 99.7% | 290 |
| South America (São Paulo) | 230 ms | 407 ms | 100% | 288 |
| US (Central) | 126 ms | 203 ms | 100% | 289 |
Edge latency to the provider’s API host over the last 24 hours, measured from 4 regions. This measures the endpoint, not the model: swapping models on the same host does not change these figures, which is exactly why they are useful when deciding whether to stay with OpenAI or leave. Compare providers →
What else retires on 2026-10-23?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| ft-babbage-002 | OpenAI | 2026-10-23 | gpt-5.4-mini |
| ft-davinci-002 | OpenAI | 2026-10-23 | gpt-5.4-mini |
| ft-gpt-3.5-turbo | OpenAI | 2026-10-23 | gpt-5.4-mini |
| ft-gpt-4 | OpenAI | 2026-10-23 | gpt-5.5 |
| ft-gpt-4.1-nano-2025-04-14 | OpenAI | 2026-10-23 | gpt-5.4-nano |
| gpt-3.5-turbo | OpenAI | 2026-10-23 | gpt-5.6-terra |
| gpt-4 | OpenAI | 2026-10-23 | gpt-5.6-sol |
| gpt-4-turbo | OpenAI | 2026-10-23 | gpt-5.6-sol |
| gpt-4.1-nano | OpenAI | 2026-10-23 | gpt-5.6-luna |
| gpt-4o-2024-05-13 | OpenAI | 2026-10-23 | gpt-5.6-sol |
| gpt-image-1 | OpenAI | 2026-10-23 | gpt-image-2 |
| o1 | OpenAI | 2026-10-23 | gpt-5.6-sol |
| o1-pro | OpenAI | 2026-10-23 | gpt-5.6-sol (reasoning.mode: pro) |
| o3-mini | OpenAI | 2026-10-23 | gpt-5.6-sol |
| o4-mini | OpenAI | 2026-10-23 | gpt-5.6-terra |
Same shutdown date. If you call more than one of these, they are one migration, not several.
Other OpenAI models being retired
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| gpt-5.2-chat-latest | OpenAI | 2026-08-10 | gpt-5.6-sol |
| gpt-5.3-chat-latest | OpenAI | 2026-08-10 | gpt-5.6-sol |
| Assistants API | OpenAI | 2026-08-26 | Responses API and Conversations API |
| Videos API | OpenAI | 2026-09-24 | — not named |
| sora-2 | OpenAI | 2026-09-24 | — not named |
| sora-2-2025-10-06 | OpenAI | 2026-09-24 | — not named |
| sora-2-2025-12-08 | OpenAI | 2026-09-24 | — not named |
| sora-2-pro | OpenAI | 2026-09-24 | — not named |
How is this calendar maintained?
Entries are pulled from provider documentation by an automated weekly job and every one carries a link to its source. Nothing is inferred from blog posts or social media. When a provider changes a date, the change appears here after the next run and is visible in the changelog. The full calendar across all providers is on the deprecations page, and this provider’s own list is at OpenAI deprecations.