Business continuity and process excellence are critical to growth, and graduating from a legacy environment to a robust and agile accounting system is imperative for banks and financial services firms to remain competitive. Our client, a leading, US-based financial services company, was looking to partner with an experienced service provider to migrate their unsupported accounting systems to the supported Windows version, as mandated by internal information security team. Coforge, with its deep domain knowledge and cutting-edge migration capabilities assumed overall responsibility of the migration process for the client, reducing risks from potential gaps and providing continual process improvement. With our support, the client not only transitioned to a modern accounting environment, but was also able to rake in dollar benefits.
A financial services company, the client is a global provider of investment processing, investment management, and investment operations solutions. The company provides products and services to institutions, private banks, investment advisors, investment managers, and private clients.
The client’s accounting system application was running on an unsupported Windows version (Windows 2000) with unsupported third-party software (Blaze Rule Engine). It was critical to migrate the application to a supported Windows version since the accounting system was a Web-based application for creating accounts on the core platform. This was a critical application for serving the business needs of existing customers and for setting up new customers on the core platform. This migration had been delayed in the past due to critical dependencies on third-party software. Due to unavailability of support for the Windows 2000 OS, the application server could not be updated with the latest security patches released by Microsoft. This made the server vulnerable to external threats in production. The Blaze Rule Engine, too, was a black box with no vendor support available for the current version of the software used in the application.
Additionally, there were also functional, technical, and budgetary challenges to migrating the application to the supported environment: