Can you still migrate before the renewal?
The most expensive sentence in IT is "we ran out of time, renew for another three years." Pick your migration path and renewal date; the planner back-schedules every phase from the deadline and gives you an honest verdict, plus calendar events you can drop straight into the team's calendar.
Pick your renewal date to see whether a ~15-week Azure OpenAI → Llama (Meta) migration still fits before it, and what has to start when.
Why plan backwards from the renewal?
Migrations that race a renewal date fail in a predictable way: the assessment and design phases run long because nobody scheduled them against a deadline, and by the time the pilot proves the runbook, the only options left are renewing anyway or cutting over without one. Back-planning inverts that: it fixes the finish (your renewal, minus a safety buffer), sizes the phases from the same per-path effort estimates our migration guides use, and surfaces the real decision, the required start date, while you can still act on it.
The production-migration phase deliberately gets the largest share of the timeline: waved cutovers with verification between waves are where estates actually spend their weeks. If your verdict comes back "tight" or "late", the corresponding migration guide covers what compressing each phase actually costs in risk, and the calculator models whether a short-term renewal beats a rushed migration on 3-year cost.