Customer Workflow Redesign Day 0

My employer owns a [Monolith Product] that provides customers the ability to place one of two different kinds of [ABC Orders], [ABC Order Type 1] and [ABC Order Type 2]. Customers choose the Location of their [ABC Order] and, depending on that Location, the [Monolith Product] will communicate with one of at least four other [ABC APIs]. Each [ABC API] has a slightly different understanding of what an [ABC Order] consists of, so the workflow that we render varies--both for the Type of the [ABC Order], and for the Location. Many elements overlap, and some elements are completely different

Like much of the legacy software alive today, the [Monolith Product] was engineered by developers underprepared to deliver the original product requirements on schedule. No judgement, this is simply the state of things

We would like to redesign this customer workflow so as to

1. Replace legacy technology (ASP.NET MVC Razor views) with modern technology (React)
2. Reimplement the workflow with more shared components and fewer one-off JQuery functions
3. Reimplement the workflow with a more refined user experience

Product and I sat down last week and walked through the idiosyncrasies of each [ABC Order] workflow. I compiled the notes, and today I began transferring the notes onto a Visio diagram, with one page of notes and screenshots for every page of the workflow. I finished transferring the notes for [ABC Order Type 1 API 1], and intend to transfer one additional set of notes every day until completion. At that point I will begin compiling a list of individual common elements (text boxes, dropdowns, etc.) from the annotated screenshots, so as to determine the full scope of possible common elements