LLMEOL CodeAP Studio

GPT-4o mini Deprecation, Shutdown Dates & Migration Guide

Runs locally in your browser — 0 bytes uploaded Synced 2026-11-12 UTC · 3 variants · 2 ecosystems

Track confirmed UTC deprecation and shutdown dates for GPT-4o mini (OpenAI) across OpenAI, Azure OpenAI. Preview gpt-4o-mini-2024-07-18 → gpt-6-luna upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.

Tracked Variants 3
Earliest Upcoming EOL 2027-01-14
Recommended Upgrade gpt-6-luna
Ecosystems Covered OpenAI, Azure OpenAI

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.

2 of 2 configured models need migration
Full .env Auditor → Compare gpt-6-luna Cost in DevToken →

Replacement Diff Preview (gpt-4o-mini-2024-07-18 → gpt-6-luna)

# OPENAI_MODEL: gpt-4o-mini-2024-07-18 -> gpt-6-luna [DEPRECATED · EOL 2027-01-14]
- OPENAI_MODEL="gpt-4o-mini-2024-07-18"
+ OPENAI_MODEL="gpt-6-luna"

# AZURE_OPENAI_DEPLOYMENT: gpt-4o-mini (2024-07-18) -> gpt-6-luna [DEPRECATED · EOL 2027-04-14]
- AZURE_OPENAI_DEPLOYMENT="gpt-4o-mini (2024-07-18)"
+ AZURE_OPENAI_DEPLOYMENT="gpt-6-luna"

2. Cross-Ecosystem GPT-4o mini Lifecycle Matrix (3)

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.

GPT-4o mini lifecycle status, UTC shutdown dates, and replacement models across OpenAI, Azure OpenAI
Model ID Provider Calculated Status Confirmed Shutdown (UTC) Vendor Lifecycle Replacement & Migration Source
gpt-4o-mini-2024-07-18 OpenAI DEPRECATED (63d) 2027-01-14in 63d Deprecated
gpt-6-luna Cost → Audit →
Docs ↗
gpt-4o-mini (2024-07-18) Azure OpenAI DEPRECATED (153d) 2027-04-14in 153d Deprecated
—Audit →
 Docs ↗
gpt-4o-mini-search-preview-2025-03-11 OpenAI RETIRED 2026-07-23112d ago Retired
gpt-5.6-terra Cost → Audit →
Docs ↗

3. Production Migration Checklist (gpt-4o-mini-2024-07-18 → gpt-6-luna)

Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:

  1. Inventory pinned model IDs: Search repositories and deployment manifests for OPENAI_MODEL, openai/ LiteLLM routes, and dated snapshot strings in the GPT-4o mini family (2 deprecated, 1 retired, 0 active variants tracked).
  2. Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against gpt-6-luna, then compare input, output, and cached token rates in DevToken.
  3. Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated GPT-4o mini identifiers cannot re-enter production.

Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:

5. GPT-4o mini Deprecation & Upgrade FAQ

Is GPT-4o mini deprecated or retired across OpenAI, Azure OpenAI?

LLMEOL tracks 3 GPT-4o mini variants across OpenAI, Azure OpenAI: 2 deprecated with scheduled shutdowns, 1 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 gpt-4o-mini-2024-07-18?

The primary recommended upgrade target for gpt-4o-mini-2024-07-18 is gpt-6-luna. Always test prompt formatting, max output tokens, and tool schemas on gpt-6-luna, and compare token pricing in DevToken before switching production traffic.

How can I replace gpt-4o-mini-2024-07-18 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.