Original reporting: Network World | Original post date: February 22, 2020
Google Cloud Buys Cornerstone Technology
Google Cloud acquired Cornerstone Technology, a firm specializing in mainframe-to-cloud migration services, with the explicit goal of helping enterprises running “Big Iron” workloads transition to private and public cloud infrastructure. The acquisition was announced in February 2020.
According to Howard Weale, Google’s Director of Transformation Practice, the core of Cornerstone’s value lies in its G4 platform — an automated toolchain that can decompose legacy mainframe programs written in COBOL, PL/1, or Assembler and recast them as cloud-native services running in managed, containerized environments.
“Through the use of automated processes, Cornerstone’s tools can break down your COBOL, PL/1, or Assembler programs into services and then make them cloud native, such as within a managed, containerized environment.”
Howard Weale, Director of Transformation Practice, Google Cloud
What the Cornerstone Platform Offers
Google stated that the Cornerstone technology would form the foundation of its future mainframe-to-Google Cloud product offerings. The platform is designed to address three common migration challenges:
- Migration roadmap assessment: Google will evaluate a customer’s existing mainframe environment and produce a structured roadmap toward a modern services architecture.
- Cross-language and cross-database conversion: The toolchain is designed to convert source code from one language to another (for example, COBOL to Java) and migrate data from legacy databases to modern equivalents.
- Automated workload migration: Automated pipelines move converted workloads onto Google Cloud infrastructure, reducing manual re-platforming effort.
Weale noted that a key use case is breaking apart mainframe monolithic applications into either Java monoliths or Java microservices — aligning legacy systems with contemporary service-oriented and microservices architectures that most enterprises now favor for new development.
Why This Matters for Google’s Enterprise Strategy
Mainframe workloads represent some of the most business-critical and deeply entrenched systems in industries such as banking, insurance, and government. Winning migration contracts in these sectors is a significant revenue opportunity — and a strong signal to large enterprises that a cloud provider can handle their most demanding requirements.
“Easy mainframe migration will go a long way as Google attracts large enterprises to its cloud.”
Matt Eastwood, Senior Vice President, Enterprise Infrastructure, Cloud, Developers and Alliances, IDC
The Cornerstone acquisition also positions Google Cloud more directly against competitors that already offer mainframe migration services, including Amazon Web Services, IBM/Red Hat, and Microsoft Azure. Each of these vendors has made investments in tooling or partnerships to help enterprises retire or re-platform mainframe workloads.
Analyst Caution: Mainframe Migration Is Not Always the Right Move
Despite the momentum behind cloud migration, Gartner issued a pointed warning — referenced in a report titled Considering Leaving Legacy IBM Platforms? Beware, as Cost Savings May Disappoint, While Risking Quality — advising organizations to scrutinize mainframe migration decisions carefully before committing.
“The value gained by moving applications from the traditional enterprise platform onto the next ‘bright, shiny thing’ rarely provides an improvement in the business process or the company’s bottom line. A great deal of analysis must be performed and each cost accounted for.”
Gartner, Considering Leaving Legacy IBM Platforms? Beware, as Cost Savings May Disappoint, While Risking Quality
Gartner’s core argument is that mainframes, while perceived as dated, continue to evolve. IBM and other vendors are actively integrating open-source tooling and modernizing hardware, making the platforms more accessible to developers. Application leaders were advised to re-evaluate the actual capabilities and total cost of ownership of their existing mainframe platforms before initiating a migration.
Key Takeaways for DevOps and Platform Engineering Teams
- Automated language conversion is the hard part. COBOL-to-Java conversion at scale has historically been error-prone and expensive. Evaluate any toolchain’s output quality rigorously before trusting automated conversions in production.
- Containerization is not free modernization. Wrapping a converted monolith in a container does not automatically make it cloud-native. Teams should plan for behavioral equivalence testing and performance validation post-migration.
- TCO analysis is essential. Mainframe licensing models differ fundamentally from cloud pricing. A detailed total-cost-of-ownership model, including staffing, testing, and ongoing cloud spend, is necessary before a business case can be made.
- Phased migration reduces risk. Rather than a full lift-and-shift, consider migrating lower-risk workloads first to validate tooling and build organizational confidence.
- Vendor lock-in trades. Moving from mainframe to a single cloud provider replaces one form of lock-in with another. Multi-cloud or abstraction-layer strategies should be considered where long-term portability matters.
Google Cloud’s acquisition of Cornerstone Technology signals serious intent to compete for enterprise mainframe migration budgets. However, as Gartner’s guidance underscores, the decision to migrate should be driven by rigorous analysis rather than vendor momentum — regardless of how compelling the automation tooling appears.