Strategies for Migrating Large Legacy App: Views + ViewModels

So I have a large codebase that will likely take a while to finally get 'modern'. It is still only 1/2 Kotlin, and very little coroutine usage... to give you an idea.

Multi Activity based without any ViewModels, all View based UI composition.

I'm wondering if moving to MVI (I personally have tons of experience with MVVM + MVI, and would like to move to MVI if possible) and compose views (only 1 person on the team has real experience with compose, ironically not me, b/c I keep getting put on older projects and have only played round with it myself)

I'm just wondering if moving to fragments with View based UI , and then slowly moving single Custom Views over from Views to Compose Views would be technically viable (The idea is to improve the code, get view models that are testable and 'slow roll' Compose (to give devs plenty of time to adapt to it while still making quicker progress on ViewModels)

Basically looking for experience from people who did this and what they found works?

Go MVVM first? then move to MVI when we go fully Compose?