Many established insurers pride themselves on longevity, tradition and security for their customers. That is why many of them still use so-called legacy systems. Such systems have been fine-tuned over years or even decades, enriched with more and more know-how, and therefore have great economic potential. Due to their longevity, however, updating them often involves major expense. So the question of how to properly deal with legacy systems remains a difficult one for many insurance managers. ERGO Germany CIO Mario Krause analyses these challenges for our industry here on //next.
In addition to its positive meaning, the word “legacy” can also have negative connotations, in the sense of an ongoing problem or inherited burden. Legacy systems can be challenging for three reasons:
Let’s be honest: given the challenges, every insurance manager would rather get rid of legacy systems sooner than later, since they are hindrances on the path towards a digital transformation.
The reality, however, is that legacy environments will continue to provide key back-end technology – and thus keep many insurers busy – for years to come. So insurers need a strategic perspective in dealing with them, in order to avoid serious maintenance and further development problems.
Like any other IT platform, the issue also requires active management depending on the situation and day-to-day business, in particular budgeting and resource utilisation in the context of the workload for upcoming projects.
At the same time, the systems still have to be kept up-to-date on a regular basis, because they will neither improve nor grow per se.
The most effective way to revamp a legacy environment is to prepare a new system or systems and replace the old ones after the data migration. Though that is of course not as simple as it sounds. The work involved extends from choosing among the options, deciding whether to “make-or-buy”, all the way to planning and implementing a modernisation project that can last years. The result is often a parallel environment that enables both systems to be checked. Two kinds of mistakes must be avoided in the overall process: functional errors and data losses. The project has to be conceived and set up as an evolutionary process.
Today’s managers have to ensure that the current situation with legacy systems is not repeated in the future. Though no one can say with certainty which of today’s technologies will become legacies tomorrow. New problems can certainly not be 100% avoided, but they need to be managed as well as possible.
Text: Mario Krause, CIO ERGO Deutschland
Part 1 of the series by ERGO Germany CIO Mario Krause on the technological challenges facing the insurance industry is available here: