The fact that it’s known code, with known shortcomings, known limitations and known work-arounds?
Statements like these make it seem like it’s a straightforward affair to port something over to what is almost only in name a successor and ignores the fact that legacy exists.
Didn’t we recently have [Poll] Kinetic users: Kinetic EOL in April, what is your migration plan? with some surprising outcomes?
Nothing wrong with encouraging users to look at newer options, but @alainsanguinetti probably has a good reason to ask the question.