Financial services firm retires legacy PHP and COBOL on Azure

The project

A longstanding Winmill client and financial services leader was facing mounting challenges with an aging technology stack: an unstable web-based PHP application prone to crashes during upgrades, and an obsolete COBOL desktop application heading toward a support cliff as key developers retired. A previous attempt with offshore developers had consumed two years and produced an unusable modernization. The client turned to Winmill for a way forward that wouldn’t put business operations at risk.

The challenges

• Fragile legacy systems. The PHP application crashed during upgrades, and the COBOL application’s support depended on a shrinking pool of retiring developers.
• No room for disruption. These were business-critical systems, so the migration couldn’t interrupt operations.
• A failed first attempt. Two years of offshore development had produced nothing usable, so confidence had to be rebuilt along with the applications.

The solution

Winmill proposed a phased migration to modern cloud-native architecture on Azure, stabilizing the existing code bases while incrementally migrating functionality. Critical components of the PHP application moved to Azure-hosted environments phase by phase, each one integrating cleanly with what remained. The aging COBOL application was transformed into a web-based application on Azure’s platform capabilities, opening the door to future scalability.

The architecture is fully cloud-native, relying entirely on Azure’s managed services with no third-party dependencies: Application Gateway with WAF for security, Storage Blobs hosting web pages, Function Apps for scalable application services, managed database instances, Azure API Management, and Azure Firewalls with security groups. This serverless approach means there are no operating systems to manage, and every component stays current with the latest security patches automatically. Azure DevOps automates continuous integration and deployment, eliminating manual build and release work.

The results

• Five nines. The business-critical systems achieved 99.999 percent availability on an architecture that scales on demand without downtime.
• Continuity throughout. The incremental approach kept business operations running uninterrupted through the entire transition.
• Lower cost, lower risk. Incremental migration and optimized cloud resources kept the project within budget, and the fully managed architecture reduces the complexity and risk of traditional infrastructure.

The hard part of a modernization isn’t the destination architecture. It’s getting there without stopping the business, and that’s what this engagement proved.