We adopted a multistage strategy to overcome these challenges. This involved close collaboration with business partners to set realistic expectations regarding scope and time, maintaining regular communication with all stakeholders, integrating change-management and risk-handling mechanisms from the project's inception, developing systems and interfaces for seamless operations during the transition allowing on-premises environments to operate while cloud development and testing proceeded, minimizing code changes, and implementing a cutting-edge data migration and synchronization strategy.
A scarcity of industry-standard modern tooling hindered the direct migration of the 250 mainframe table structures with 100GB of data, and the bi-directional synchronization of over 400 data points across more than 40 table structures between mainframe and cloud environments. Our team developed a two-stage data extraction process: Initially, data was securely moved to an intermediate industry-standard database, then transformed and migrated to the cloud database using cloud-native tools. Data synchronization from on-premises to cloud was established through this process. To maintain data synchronization from cloud to on-premises, new integration APIs were developed for four classes of data based on data ownership and read/write access.
This project leveraged a previously Booz Allen-built, fully managed multi-tenant cloud platform at the agency for hosting application containers. The aim was to accelerate development, reduce the time needed to achieve Authority to Operate (ATO), and demonstrate the platform's viability for a lift-and-shift approach for our customer. The platform team managed infrastructure, security, and other critical tasks, allowing tenant application teams to focus on their products. Services offered included logging, analytics, container hosting, cloud databases, network integration, and inheritable security controls.
Containerizing the application expedited the timeline and enabled cloud deployment before all modernization challenges were addressed. This allowed legacy code to run with minimal changes, replicating the original hosting setup, and deferring costlier modifications until after migration to deliver the application sooner and save on-premises costs.