Don't Write Off the Mainframe as a “Legacy” System

Joe McKendrick
Insurance Experts' Forum, April 21, 2010

Celent has just issued a report that observes how a majority of insurance companies still tether their information requirements to “legacy” systems, but are gradually moving toward “modern” implementations.

As the report correctly observes, “carriers realize that this abundance of legacy code is inflexible and costly to maintain, and that it has large implications for their business.” The report, which queried 30 insurance system professionals, charts a good deal of progress. For example, while the 73% to 27% split between legacy and modern systems five years ago, currently the balance is 52% legacy and 48% modern. Celent estimates that the split will be 61% to 39% in favor of modern systems five years from now.

The question is: what is a “modern” system versus a “legacy” system?  And why wouldn't a modern system put in place today be legacy five years from now?

Presumably, a “modern” system is one that runs open, portable software on commodity hardware. An application based on Windows or Linux operating systems running on Intel or AMD processors comes to mind.

Conversely, many think of “legacy” systems as proprietary, closed-system software that runs on one type of hardware. An application written in language such as COBOL, and running on a mainframe is the first thing that comes to mind.

Hmmm ... is this the right definition? The iPad and iMac are actually closed systems that run on one single type of proprietary hardware. Windows essentially only supports one type of hardware architecture. But I haven't heard anyone refer to them as “legacy” systems.

Then there's the mainframe. IBM's System z runs Linux and Unix and even Windows, via virtual partitions or through specialty processors attached to the system. But no one seems to call the mainframe an “open” system.  

Perhaps the definition of “legacy” pertains to the age of applications. So all those Linux and Windows servers deployed back in 2005 are legacy? Or, perhaps any application or system where there are no longer enough skilled professionals to provide support and maintenance?

My colleague, and INN Editor-in-Chief, Pat Speer explored these questions in an article a few months back, and perhaps Matthew Josefowicz at Novarica explains it best: “The issue is with legacy applications that are poorly documented, incompletely understood by the people responsible for maintaining them, and unable to provide new functionality.”

The key to this semantic pretzel is that the needs of the business need to come first, and executives should not rush to new systems because they're the latest-and-greatest shiny new architecture. For example, I just saw an interesting case study in which Blue Cross Blue Shield Minnesota migrated Windows and Unix applications off of 140 different servers onto Linux on a single mainframe, saving on power as well as streamlining maintenance and support costs.

With new architectural approaches, such as service-oriented architecture, virtualization and cloud, it often no longer matters what systems are running in the background.

As I've said before, in many cases, legacy shouldn't be such a bad word.

Joe McKendrick is an author, consultant, blogger and frequent INN contributor specializing in information technology.

Readers are encouraged to respond to Joe using the “Add Your Comments” box below. He can also be reached at

This blog was exclusively written for Insurance Networking News. It may not be reposted or reused without permission from Insurance Networking News.

The opinions of bloggers on do not necessarily reflect those of Insurance Networking News.

Comments (5)

Thanks for the mention Joe - here's a link to my original post about legacy apps v. legacy "systems" -

Posted by: Matt J | April 26, 2010 11:09 AM

Report this Comment

Interesting article - maybe legacy just means "we don't prefer it", ultimately being rather arbitrary. I can think of some relatively new systems/projects that are closed and not well understood throughout - so that shouldn't be it.

Posted by: RM | April 23, 2010 1:48 PM

Report this Comment

These conversations invariably argue over syntax and operating systems as being inflexible or rigid. What is clear is that IT is a profession that is practiced and evolving. It is this learning and set of better practices that make "legacy" a bad thing. Holding on to poor rigid data and programming structures (regardless of syntax) is like asking doctors to use the same operating rooms and techniques from 30 years ago. The legacy is IT's development as a discipline and the move to better practicies. This is why we don't think about a five year system as legacy even if it is performing the same basic functions. If is built to be more open and flexible then the code doesn't matter it is not the legacy it replaced.

Posted by: jim_klotz | April 23, 2010 1:16 PM

Report this Comment

In my mind, "legacy" is the software flexability. COBOL applications are mostly base code with very little room for easy modifications - i.e costly.
Modern applications such as .net or Java allow changes, such as a rate change, to be done in a database instead of a complete recode.

Posted by: Barry W | April 23, 2010 11:49 AM

Report this Comment

Interesting read.

Especially for all the Clipper, Visual Basic, C, C++, Java, PHP, Python programmers who thought their programming language was the last one we would ever need.
It's time we SERIOUSLY look at what we have. Not with the latest hype in mind.
Every "modern" application I know is a collection of undocumented (and even more unreadable) code, scripts and database definitions. It is just written in a more modern programming language..
The mainframe is the only platform where we can run 25 year old Cobol next to JAVA, and share the same data. And with the latest versions of Mainframe products, EVERYTHING (even old Assembler code) can be accessed as a SOA application. I am not saying that the a so called Legacy system as the Mainframe is better, I am just saying that it's "en vogue" to make the current look good by making "the old" look bad...
And with the latest releases of hard- and software, vendors like IBM, CA and others will proove again that the mainframe is here to stay. Try this: register for CA's Mainframe Virtual Tradeshow in May ( to see for yourself how vital and modern the Mainframe actually is.....

Posted by: Marcel d | April 23, 2010 6:43 AM

Report this Comment

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

With Google Favoring Mobile, Will The Industry Take it Seriously?

Google’s search engine will now will favor mobile friendly content over traditional website content; within the insurance industry, the greatest initial impact is likely to be felt by insurance distributors.

Why Some Technologists Get Cold Feet on Mobile

There are those who believe that favoring one channel or mode over another will lead to even more silos and dysfunction than we already have in many organizations.

Insurance IT Spending and Budgeting Benchmarks

New research from Novarica highlights areas of concern and offers insights on insurers spending and budgeting decisions.

Enterprise Mobilemania Continues Unabated

More than half of companies are spending more on developing mobile applications -- but are they more efficient?

Why Insurers Need More Than a Policy Admin System

For some insurers, not being able to handle the volume of quotes that are being submitted to them means leaving significant money on the table.

The Pitfalls of Using Assembly Line Methods to Create Software

Most of the time, when the business needs IT, it is for custom software development, just like creating a concept car.