How to identify legacy software?

How to identify there is an issue with your legacy software system? There are many factors that can determine whether you should take an action and create the roadmap for the new.

The system is slow and not perform as expected

In case the system is slow, standard activities take hours to perform and the overall system is becoming cumbersome, the lack of performance is clear – the reason might be that the software or technology is out to date or the quality is low. Consequences can be huge. Can you imagine 200 users spending 20% of their time waiting for the system to deliver information or perform the task?

Device-dependent and no mobile-device support

Nowadays, most of the software is created as a web-based application because of two reasons: one is that updates are simple (all users got access immediately to the new version), and second, that users can work on almost any device. Modern applications are designed to be responsive (Responsive Web Design) and more and more organizations, move to the online world or to cloud solutions. Working remotely, from laptop, tablet or smartphone requires the software to be device-independent and available typically on-line. Even native application (e.g. written on Apple iOS or Google Android needs internet connection to perform, in order to connect to database).


The software is not able to integrate with other solutions or is not supported by modern operating systems or web browsers. In the near future, it will require replacement or redevelopment.

Software is not user-friendly and hard to learn

There is a lot of solutions that requires additional training for users (e.g. engineering or design software), but when we talk about day-to-day business solutions, platforms should be created as low-touch solutions and easily accessible for any type of user.

Technology is obsolete and/or not supported

Technology world is rapidly changing from month to month. Having the software developed few years ago, you might face outdated technology (no longer supported) on many levels from the code, to server and user-interface. Great examples are old frameworks that contains deprecated functions or integration interfaces no longer supported by 3rd parties.

The software is no longer functional

All the functions and features that have been useful years ago, might be not needed anymore today. Your current software system that has not been developed by the years to map current processes or needs of users, might not only be legacy but also create frustration because of workarounds that people have to make.

You can’t add new features or integrated with new 3rd party solutions

In case the maintenance of the software is so hard that you can’t add any new feature or the risk of crushing the system is to high, you should consider your software as legacy and this is really critical issue. Expanding the functionality and following business change should be one of the main assumption in rapidly changing world, so instead of creating limitation and barriers, the software should be flexible enough to support organizations and people.

And finally… maybe this is also relevant