New Approach to Vita Builder Transition
While VB remains our long‑term direction, we will continue supporting both tools in the near term and no longer maintain a mandatory deprecation timeline for Legacy Vitas.
We are updating our approach to the Legacy/Vita Builder (VB) transition by shifting from a mandatory migration model to a institution-led, value‑driven strategy. This change reflects our current roadmap priorities (focused on platform stability, meeting bug SLOs, and enhancing accessibility) as well as institution feedback indicating that migration represents significant effort and, for some, is not yet feasible. Our goal is to promote Vita Builder based on its value rather than enforcement, maintain trust, and support sustainable, organic adoption over time.
The overall goal to move all institutions to Vita Builder remains the same, but the September 2026 depreciation deadline has been removed.
Updated Approach
The updated transition strategy reflects a more flexible and institution‑aligned approach:
- Continue to support both Legacy Vitas and Vita Builder (VB) in parallel.
- Encourage, but do not require, institutions to adopt VB.
- Remove the previously communicated hard deprecation deadline for Legacy Vitas.
- Promote the benefits of VB in a measured, value‑focused way.
- Invest in incremental improvements to VB based on roadmap capacity and value to institutions.
Rationale for Change
-
Roadmap priorities reduce bandwidth for parity work. This year’s roadmap is centered on:
- Platform stability
- Meeting our bug SLO commitments
- Required accessibility improvements
-
Migration effort is significant. Feedback indicates that:
- Moving from Legacy Vitas to VB requires substantial effort from institutions.
- Many institutions would not choose to prioritize this work at this time.
-
Feedback indicates importance of emphasizing value over mandates. VB offers meaningful advantages such as advanced customization options, robust template management, improved flexibility and future scalability.
Our new approach highlights these benefits organically, encouraging adoption based on value rather than obligation.
- Legacy evaluation users cannot migrate. Some institutions using legacy evaluation workflows cannot transition to VB under current conditions. As a result, full deprecation of Legacy Vitas is not feasible at this time.