Project transition to Yii + angular, how to argue?

Question

Yii

Good afternoon. I will briefly describe the current situation.
There is an electronic document management system written in PHP, which is 7+ years old. It is being developed and redesigned all the time. Naturally, historically, everything there consists of shit and sticks. Softly switching to some kind of framework will not work, in fact, the foundation needs to be created from scratch.
Now the initiative group wants to start processing this whole thing, but for this it is necessary to get approval from the management (technical and general directors) for a partial freeze of the project.
I would be grateful for the advice of those who made such a transition, whether the end result is worth the effort spent (for programmers) and whether everything will go sideways later due to a weak increase in productivity (for bosses)

Answer 1

Аргументация проста - Деньги. Надо показать что стоимость поддержки того что есть дороже переделки. Разумеется всё в человеко-часах и зарплате. Если всё это посчитаете, то может быть и сами поймёте что пока лучше не трогать.

Answer 2

I'll add my 5 cents. There is a project written in parser3. Very few people work with it. We decided to switch to php. We have parser + php. Rewriting everything in php will not work because this is time, which means money. Then we started using yii 1 and now we have parser + php + yii1. There is no time and money to rewrite everything on parser and php to yii1. And this happens very often. Businesses will not invest in reworking what already works. We are making new functionality on yii1. But yii1 is also outdated and it's time to switch to yii2. And converting everything to yii2 is years of work, and by that time yii3 will appear and php 10 will be released))
Tip - make the project in the form of independent (ideal world) or semi-dependent (real world) services. Then you will be free to use the best tools for each specific task.

Answer 3

Here is a good article - https://habrahabr.ru/post/307282/
One of the best approaches, slow refactoring. When split into 2 teams, there is a risk of being stuck for many years with the release of a new version.
If index.php is used only, without calling ->run():
Then Yii2 can be used to speed up development, as a set of libraries. Rewrite the core of the current project on it, and then start switching individual parts. Although there may be conflicts if you do not use namespace.
It can also be used to rewrite part of the functionality in the style of microservices.