Migrate to Gemini 3.5 Flash to Prevent Service Shutdowns
Update your API model IDs to avoid service interruptions.
Proactively migrate your AI integrations from deprecated models like Gemini 2.0 or Imagen 4 to newer versions like Gemini 3.5 Flash or Nano Banana.
The Scenario
A developer is using 'gemini-2.0-flash' or 'Imagen 4' in their application and needs to avoid service shutdown by migrating to a newer stable version.
Before & after
Maintaining legacy code with deprecated model IDs can lead to sudden app crashes and hours of troubleshooting when the service shuts down.
Switching to gemini-3.5-flash or gemini-3.1-flash-lite via the config file takes about 5 minutes of engineering work.
The Prompt
I am currently using [OLD_MODEL_ID, e.g., imagen-4.0-generate-001]. Help me rewrite my API configuration to use [NEW_MODEL_ID, e.g., gemini-3.1-flash-image].
Google has announced that Gemini 2.0 models and older Imagen models are being phased out in mid-2026. Developers should move to Gemini 3.5 Flash or Gemini 3.1 Flash Image (Nano Banana).
Source
Release notes | Gemini API | Google AI for Developers"Use gemini-3.5-flash or gemini-3.1-flash-lite instead... update to a newer model... to avoid service disruption."
