The developer who built it left long ago. The documentation consists of a handful of screenshots in a shared folder. A few colleagues know exactly which button not to press on a Thursday morning. And yet the business runs largely on that application: invoices, stock, customer data, or the entire primary process is in there.
That is why modernisation starts not with code, but with understanding. We want to know what the software does, who uses it, and what would become impossible if it went offline tomorrow. Only then do we look at the options: replace, upgrade, move to the cloud or perhaps even retire it. For organisations with messier IT more broadly, we tackle this together with an IT modernisation consultant who looks beyond this one application.
We mainly work on web applications and business software at the scale of Dutch SMEs and mid-sized organisations. No multi-year mainframe migrations, but concrete projects that deliver tangible results within a year or two. For the heavier end, we refer you to our page on modernising legacy software, where we go deeper into enterprise modernisation and strangler fig architecture.
The typical old software we encounter spans several generations of technology. On the desktop side we see Visual Basic 6, Delphi and older .NET versions. On the web side, Classic ASP, PHP 5, jQuery-driven sites on outdated frameworks, and WordPress installations from the early 2010s. On the office side, it is often MS Access databases and Excel VBA files that have taken on more and more weight over the years. On the business software side we see Oracle Forms, D2K and industry-specific packages on AS/400 or RPG. And sometimes there are remnants of Flash, Silverlight or Java applets that were officially retired in 2017, 2020 and 2021 but are still in everyday use. The same basic approach applies to all of these; only the migration route differs.