Migration notice · verified July 19, 2026
Sora is being discontinued: what to migrate now
FlowVideo no longer accepts new Sora generation jobs. We are keeping this URL as a factual migration guide so existing Sora users can preserve their search intent, prompts, and production workflow without being sent to a discontinued purchase flow.
Official shutdown timeline
- Web and app
- Discontinued April 26, 2026
- Sora API
- Scheduled to end September 24, 2026
Source: OpenAI, “What to know about the Sora discontinuation”. Check the official notice before making a final migration decision because dates can change.
Choose an alternative by job, not by brand name
General text-to-video draft
Start with Happy Horse in the main generator and keep the initial prompt, duration, and framing explicit.
Image-to-video
Use the Wan 2.7 image-to-video workflow when the first frame and visual identity matter more than open-ended world simulation.
Character or motion control
Use a reference-driven workflow and keep character images, motion references, aspect ratio, and duration explicit.
Audio-led production
Separate visual generation from narration or sound when you need repeatable timing, then combine the approved assets in the workspace.
Sora API migration checklist
- 1. Export first. Download Sora source files, prompts, seed notes, aspect ratios, durations, and approved outputs while the official export path remains available.
- 2. Inventory the contract. Record whether each workflow depends on text-only generation, a first frame, reference media, synchronized audio, or a fixed duration.
- 3. Run a controlled comparison. Test the same prompt and inputs on one alternative before migrating a batch. Preserve failures as well as successful outputs.
- 4. Update billing assumptions. Replace Sora-specific duration and price logic with the selected model’s visible credit estimate and refund behavior.
- 5. Remove the old endpoint. Stop new calls before September 24, 2026 and keep old task history read-only for customer support.
Alternative, replacement, and API migration queries
For a Sora alternative or replacement, compare the current input contract and per-second cost rather than matching a model name. For API migration, first map required media inputs and duration, then move the endpoint, billing reservation, failure refund, and history reader together.
Compare current model inputs, limits, and cost