Engineering decision
Use a reversible migration strategy for a production framework change
A high-risk migration was planned around reversibility so modernization did not put product continuity at unnecessary risk.
Context
The Dashboard migration involved a 26-step plan, 460-file cutover, and a production framework change from Next.js to Vite and React Router.
Options
- Big-bang migration with limited rollback options
- Incremental cutover with a dual-runtime Docker image and documented rollback
Decision
Use the reversible path with a dual-runtime image and production rollback plan.
Trade-off
The migration required more planning and operational discipline, but reduced rollout risk.
Outcome
The high-risk framework swap became a 2-minute reversible deploy with end-to-end rollout ownership.