Migrating Legacy App Strategy

Hi folks, long-time listener, first-time caller.

I've recently landed a job migrating a legacy fox pro app that has been built over the last 20 years. There is one MSSQL database and many "apps" that interact with it.

Many of the apps are written using the FoxPro WebConnection Framework

Long story short, the WebConnection framework helps create asp.net applications that can leverage Foxpro "backends"

The high-level flow is browser/client -> asp.net -> Foxpro -> MSSQL

We have identified 3 migration strategies (All strategies assume a new React Frontend) :

1. Start from scratch – New API, new DB (Modernize)
2. Write a new API Server against the existing DB (Bypass FoxPro)
3. Hybrid

Starting from scratch will take the longest (years) as it requires a lot of upfront development just to create an MVP. But lots of freedom.

New API to the existing database carries risks of interfering with existing processes and data. Could harm production? Lots of constraints.

Hybrid combines both issues but to a lesser degree. Pick and choose each module, class, page, and component to focus on and incrementally migrate. Limits blast radius in production.

I'm pushing for the hybrid.

I know this is a little vague but would love to hear opinions on things I should be thinking about. What questions naturally come up to this high-level overhaul task?