I question the project heads for deciding to migrate rather than build a new product UI side by side with the existing from scratch.
Since 2014, we have done this several times
UI+backend went from [Cruddy coffeescript + Node.js] to [Jquery + django] to [React 15 + django] to [React 17 + django] and after we were acquired [AngularJS + django] is ongoing.
Backend has been python since the beggining.
Public API server went from python to golang.
Compute and Infra went from private baremetal to k8s.
At no point was there ever any already running code being refactored or framework updated.
We build an improved clone of what exists and plug it in after its been used by enough people in beta. We dont throw the old stuff away until new deployments are working on client premises under high loads and extreme usage.
We dont force clients to upgrade unless serious bug fixes exist.
We never change UI in a way that older customers have to do anything different - unless its a major feature upgrade.
Since 2014, we have done this several times
UI+backend went from [Cruddy coffeescript + Node.js] to [Jquery + django] to [React 15 + django] to [React 17 + django] and after we were acquired [AngularJS + django] is ongoing.
Backend has been python since the beggining.
Public API server went from python to golang.
Compute and Infra went from private baremetal to k8s.
At no point was there ever any already running code being refactored or framework updated.
We build an improved clone of what exists and plug it in after its been used by enough people in beta. We dont throw the old stuff away until new deployments are working on client premises under high loads and extreme usage.
We dont force clients to upgrade unless serious bug fixes exist.
We never change UI in a way that older customers have to do anything different - unless its a major feature upgrade.