1. Homepage
  2. -
  3. Insights
  4. -
  5. How to Replace a Legacy...
How to Replace a Legacy Core System in a Big Insurance Company?
Sollers , Case study , Digital, Innovations

About the Customer

The Customer was one of the largest Polish insurers with life, non-life and investment products in its portfolio, present for over 20 years on the Polish market. This insurer is part of a global insurance group with impressive 185 years of history.

Their products are sold through multiple distribution channels, including direct, agent, phone and, e.g. white labels via motorbike dealers.


What was the goal of the project

Increasing costs of maintaining the old legacy core system prompted the client to transform their core application architecture. The goal was to migrate existing policies from three legacy core systems to the INSIS v10 solution.

The client also wanted to improve their sales front-end, which had its own product definition before the project. Afterwards, the target was to have the product only in the implemented core system while the front-end should read the product definition through web services.


What solution was implemented

The INSIS v10 core system was implemented by a mixed team. During our work on the project, four products were introduced. Then the Customer’s team continued to add more products to the new core system. We created a new Webservice layer for INSIS, which enables the front-end to read the product configuration directly from the core. This means that after a new product version is implemented in the core, it is ready to be used without any development of the sales front-end.

During the project, a minor version upgrade of INSIS was also supported by Sollers.

The Customer decided to migrate policies on a renewal basis, which we are also taking part in.

What is more, a good CI/CD process had already been defined for the whole company. In cooperation with the Customer’s admin team, Sollers admins created a fully automated code deployment with a QA process which made the release cycle significantly faster. During the project we maintained over 10 environments apart from the Production one, all on-premise.

See other case studies