Isatis Software Solutions is a nearshore software development company in Nijmegen and Sarajevo with over 30 years of experience. We modernise business-critical legacy software in phases, keeping business logic, data and daily operations intact.
Get in touch
Projects Delivered
100+
Legacy modernization is moving an ageing application to current technology in phases, while the business logic, data and daily operations it supports stay intact. Isatis does this for organisations whose business-critical software has become hard to maintain, extend or secure, often in healthcare, education, manufacturing, government, energy and utilities. We start with a short assessment with the people who use the system and the engineers who will modernise it: what still works well, what costs you time and risk, and where modernisation will have the most impact.
The assessment results in a phased plan, prioritised by business risk and technical debt, with no big-bang rewrite. We then work in short iterations with live demos, so every step delivers working software you can use, and you can adjust course along the way.
At ST Engineering, our assessment showed that the existing business logic was limited and only partly reusable. So instead of a straight migration, we kept what still had value, rewrote the software around a modern architecture and then added a lot of new functionality. The software was faster right away, and it is now easier to keep developing. The project is still running.
Your operations keep running during an incremental migration. We migrate component by component, so old and new run side by side and every stage can be rolled back. A component switches over once tests against the legacy behaviour pass, and your teams keep working with familiar tools while we replace the technology underneath.
We worked this way for ST Engineering, rebuilding an MRO platform for aircraft nacelle repairs in .NET and Angular while the repair process kept running.
We extract the rules from the old system, document them and carry them into the new architecture, then prove with automated tests against the legacy behaviour that the new system does what the old one did. Your domain experts validate each rule with our engineers before anything switches over.
Legacy systems often hold years of undocumented business logic. For Ignite Group we rebuilt the Subsidie Administratie Systeem, originally built by another party, on a modern technology stack. Dashboards, document storage, task flows, reporting and authentication were carried over with the core functionality intact, and the new version connects to the surrounding systems.
The goal is a system that will not become legacy again in five years. We use proven technologies such as .NET and Angular, a clean architecture and clear documentation, so your own team can keep developing it too. Security, performance and compliance are part of the modernisation itself, and our work is covered by ISO 9001 and ISO 27001, both externally audited. After go-live the same engineers keep improving the system.
AI-supported analysis helps us understand undocumented behaviour in legacy code faster and speeds up parts of the implementation work, as it did in the Ignite Group rebuild. Our engineers stay in control of architecture, validation and delivery quality, and nothing AI produces reaches production unchecked.
In a 15-minute call we look at whether your system needs a refactor or a rebuild. You get an honest answer, even if Isatis is not the right partner. We reply within 24 hours.
Schedule a callLegacy systems get harder to maintain, extend and secure every year: frameworks stop receiving security updates, the people who know the code leave, and every new feature takes more effort than it should. The assessment puts those risks in order, so you fix the most expensive one first.
Rehosting moves the application as it is to new infrastructure, refactoring improves the code without changing what it does, rearchitecting changes the structure and replacing rebuilds the application on a new stack. Most modernizations combine several of these. Isatis makes that choice per component in the assessment, based on business risk and technical debt. In our two published cases the answer was a rebuild on a new stack that kept the proven domain logic.
It depends on the size of the system and how many components can move independently. A focused first release typically takes 2 to 3 months, a full enterprise system 6 to 12 months. We always start with a short discovery and assessment, and after that you see progress in short iterations with live demos.
The cost depends on the size of the system, how many components can move independently, the state of code and documentation, and the number of integrations. After the assessment, Isatis gives you an estimate based on the phased plan. Because the same team maintains the system after go-live, total cost of ownership stays predictable.
Yes, we regularly step into existing projects that need to be stabilised. Both published modernization cases involved software built by another party. We start with a review of the code and architecture, then propose a phased plan, and where documentation is missing we reconstruct the rules from the code.