OpenAI o3 & o3-pro Deprecation, Shutdown Dates & Migration Guide
Track confirmed UTC deprecation and shutdown dates for OpenAI o3 & o3-pro (OpenAI) across OpenAI, Azure OpenAI. Preview o3-2025-04-16 → gpt-5.6-sol upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.
1. Quick .env & SDK Snippet Replacement Matcher
Edit or paste your .env assignment, LiteLLM route, or SDK model identifier below to check live 3-state EOL status and copy a ready-to-apply replacement diff locally in your browser.
Replacement Diff Preview (o3-2025-04-16 → gpt-5.6-sol)
# OPENAI_MODEL: o3-2025-04-16 -> gpt-5.6-sol [DEPRECATED · EOL 2026-12-11]
- OPENAI_MODEL="o3-2025-04-16"
+ OPENAI_MODEL="gpt-5.6-sol"
# AZURE_OPENAI_DEPLOYMENT: o3 (2025-04-16) -> gpt-5.6-sol [DEPRECATED · EOL 2026-11-19]
- AZURE_OPENAI_DEPLOYMENT="o3 (2025-04-16)"
+ AZURE_OPENAI_DEPLOYMENT="gpt-5.6-sol"
2. Cross-Ecosystem OpenAI o3 & o3-pro Lifecycle Matrix (9)
Direct vendor APIs and cloud platforms retire dated snapshots on independent schedules. Verify the exact model ID, vendor lifecycle stage, and UTC shutdown date matching your deployment.
| Model ID | Provider | Calculated Status | Confirmed Shutdown (UTC) | Vendor Lifecycle | Replacement & Migration | Source |
|---|---|---|---|---|---|---|
o3 (2025-04-16) |
Azure OpenAI | DEPRECATED (7d) | 2026-11-19in 7d | Deprecated | Docs ↗ | |
o3-deep-research (2025-06-26) |
Azure OpenAI | DEPRECATED (7d) | 2026-11-19in 7d | Deprecated | Docs ↗ | |
o3-pro (2025-06-10) |
Azure OpenAI | DEPRECATED (7d) | 2026-11-19in 7d | Deprecated | Docs ↗ | |
o3 |
OpenAI | DEPRECATED (29d) | 2026-12-11in 29d | Deprecated | Docs ↗ | |
o3-2025-04-16 |
OpenAI | DEPRECATED (29d) | 2026-12-11in 29d | Deprecated | Docs ↗ | |
o3-pro |
OpenAI | DEPRECATED (29d) | 2026-12-11in 29d | Deprecated | Docs ↗ | |
o3-pro-2025-06-10 |
OpenAI | DEPRECATED (29d) | 2026-12-11in 29d | Deprecated | Docs ↗ | |
o3-deep-research |
OpenAI | RETIRED | 2026-07-23112d ago | Retired | Docs ↗ | |
o3-deep-research-2025-06-26 |
OpenAI | RETIRED | 2026-07-23112d ago | Retired | Docs ↗ |
3. Production Migration Checklist (o3-2025-04-16 → gpt-5.6-sol)
Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:
- Inventory pinned model IDs: Search repositories and deployment manifests for
OPENAI_MODEL,openai/LiteLLM routes, and dated snapshot strings in the OpenAI o3 & o3-pro family (7 deprecated, 2 retired, 0 active variants tracked). - Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against
gpt-5.6-sol, then compare input, output, and cached token rates in DevToken. - Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated OpenAI o3 & o3-pro identifiers cannot re-enter production.
4. Related OpenAI & Ecosystem Migration Guides
Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:
GPT-4o
DEPRECATED (63d)GPT-4.1 & GPT-4.1 mini / nano
DEPRECATED (63d)GPT-4 Turbo
RETIREDGPT-4 (0613 / 32k / Vision)
RETIREDGPT-3.5 Turbo
RETIRED5. OpenAI o3 & o3-pro Deprecation & Upgrade FAQ
Is OpenAI o3 & o3-pro deprecated or retired across OpenAI, Azure OpenAI?
LLMEOL tracks 9 OpenAI o3 & o3-pro variants across OpenAI, Azure OpenAI: 7 deprecated with scheduled shutdowns, 2 retired past their UTC EOL date, and 0 active with no announced shutdown date. Check the cross-ecosystem matrix above for exact snapshot dates.
What is the recommended replacement model when migrating off o3-2025-04-16?
The primary recommended upgrade target for o3-2025-04-16 is gpt-5.6-sol. Always test prompt formatting, max output tokens, and tool schemas on gpt-5.6-sol, and compare token pricing in DevToken before switching production traffic.
How can I replace o3-2025-04-16 in .env and LiteLLM configs safely?
Paste your OPENAI_MODEL assignment or LiteLLM model block into the Quick Replacement Matcher on this page to generate an exact diff, or open the full Local Model Config Auditor to scan multi-service manifests with zero network upload.