Service · Web development

Modernising legacy software without disrupting your business.

An Access file that keeps the company running. A VB6 application nobody dares touch. A WordPress site from 2009 that breaks again every month. We help you replace or upgrade old software pragmatically, while preserving the business logic that has crept into it over the years.

Web app rebuildBusiness software upgradeData migrationStrangler fig

Old software is rarely just a tech problem.

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.

Three common modernisation routes.

Not every old application needs to be rebuilt entirely. Together we choose which route fits your situation, based on business risk, user base and how deeply the software is woven into other processes.

Compact project · fixed sprint budget

Upgrade while preserving the logic

For applications that functionally do what they need to, but run on an outdated stack. Think of a PHP 5 web application brought up to PHP 8 and a modern framework, or a WordPress 3.x site that moves on headless with the same editorial flow. The business logic stays, the foundation is renewed. This is closely related to resolving technical debt, which we also offer as a standalone service.

RefactoringFramework upgradeSecurity patchingTest safety net
Mid-sized project · fixed sprint budget

Web rebuild on a modern stack

For desktop applications or heavily outdated web software where the stack itself is no longer sustainable. We rebuild the core functionality in React, Vue or Astro with a REST or GraphQL backend, and migrate the data from the old system. Often using a strangler fig approach: replacing modules one by one while the old system keeps running.

React / VueREST APIData migrationSide-by-side run
Advisory engagement · scope-dependent

Replacement with SaaS or a platform

Sometimes rebuilding is not the right route. If an existing SaaS package covers 80 per cent of the functionality perfectly well, we will help you establish that honestly, select the package and guide the transition. We only build the parts that genuinely set you apart — an integration, a dashboard, a specific workflow component.

SaaS selectionImplementationIntegrationsData conversion

What you get at the end of a modernisation project.

Besides working software, we want your organisation to be able to maintain the new environment itself — or have another agency maintain it without lock-in.

  • The modernised applicationProduction and acceptance environments on a stack that will stay maintainable for years to come. Cloud (GCP, AWS, Azure) or on-premise — your choice.
  • Clean codebase plus documentationSource code in a Git repository, build and deployment instructions, and an architecture overview that gets a new developer up to speed within a day.
  • Migrated data with an audit trailA validated data migration including a reconciliation report: what was transferred, what was deliberately left behind, and how discrepancies were handled.
  • Test safety netAutomated tests on the critical flows so that a future change does not quietly break something. We write these tests during the project, not afterwards.
  • Knowledge transfer and trainingSessions for key users and administrators, plus a recording that new employees can watch later. No knowledge stuck in our heads.
  • Support contract (optional)Ongoing monitoring, security updates and further development for a fixed monthly price. You can also place it with another agency — no vendor lock-in.

When modernisation is a sensible investment.

Four patterns we often see in organisations that approach us. If you recognise one or more of them, it is worth having a conversation.

Knowledge risk

The original developer has left

The software still works, but nobody in the organisation knows exactly how any more. Every change brings the fear that something will quietly break. It is no longer running a business, it is a balancing act.

Security

The stack no longer receives updates

PHP 5, old .NET versions, Windows Server 2008, Flash, Silverlight, Java applets. The runtime is no longer maintained, security patches no longer arrive, and your IT supplier refuses to host it.

Scalability

The system does not scale with the company

What worked for 20 users in 2008 now creaks under 200. Reports take an hour. Opening a new branch requires a manual database copy. Growth is held back by technology.

Acquisition

After an acquisition you are left with a patchwork

Three applications, three technology stacks, three versions of the truth about the same customer. Modernisation is then often also consolidation: fewer systems, better aligned with one another. This often continues into a broader project for enterprise software that serves multiple departments at once.

Concrete modernisations we have carried out more than once.

A few recognisable scenarios that illustrate our pragmatic approach. We don't invent client names — instead we describe patterns we encounter time and again, so you can judge whether your situation is a variant of one of them.

Office application

Access database becomes a web application with an audit log

An MS Access file once created by an internal employee grows into the beating heart of a department. Backups consist of copied files on a network drive. We migrate the data to PostgreSQL, build a web interface on top of it with role-based access, and make sure every change is traceable via an audit log. We extract the business logic from the existing forms and macros, validated with the users.

MS AccessPostgreSQLAudit logRole-based access
Desktop application

VB6 desktop app becomes a web app on a REST API

A Visual Basic 6 application the entire back office uses every day. Installing it on new workstations is getting harder, working from home is difficult, and the supplier of the old database has stopped supporting it. We build a React or Vue frontend on a REST API, replace the old database with a modern one, and connect the existing integrations through clearly documented interfaces. The user interface follows the old flow as closely as possible, so training stays short.

VB6React / VueREST APIBrowser-only
Website

WordPress 3.x goes headless with Astro or Next.js

A company website from the early 2010s running on an old version of WordPress. The editorial team is used to the admin panel, but the site is slow, hard to keep secure and struggles to meet modern SEO requirements. We use WordPress as a headless CMS behind an Astro or Next.js frontend, keep the editorial workflow, and gain in speed, security and build quality. Content moves across one-to-one.

Headless WordPressAstro / Next.jsCore Web VitalsSEO retention
Excel legacy

Excel macros become a web form with validation

An Excel file with VBA macros that production or administration relies on. A single wrong cell or a forgotten column can disrupt the whole chain. We convert the logic into a web form with server-side validation, connect the output to your existing systems, and keep every version that is entered. Excel remains available for the one-off calculations where it makes sense, but your business process no longer runs on a single file.

Excel VBAWeb formValidationAudit trail

Compliance and risk management in modernisation.

Beyond the pure technology, every modernisation runs through your organisation's policies and your sector's regulations. We help you think these through, not as lawyers, but as builders who know how to translate them into practice.

GDPR / privacy

Personal data during data migration

Modernisation often reveals that the old application holds more personal data than strictly necessary. We help with a privacy check on the data, decide together what needs to be carried over and what can be cleaned up, and document how data is processed and stored in the new environment.

BIO / NIS2

Government and critical sectors

Government organisations (the Baseline Informatiebeveiliging Overheid, BIO) and companies in critical sectors (NIS2) face stricter requirements for logging, access management and incident response. We build those requirements into the design and deliver documentation that fits your own ISMS.

NEN 7510

Healthcare

When modernising healthcare software, we work in line with NEN 7510. Patient data stays within Dutch or European hosting, audit logs are standard, and authorisations can be demonstrated at the level of the individual user.

ISO 27001

Fitting into your management system

If your organisation is ISO 27001-certified, we deliver documentation and processes that fit within your existing management system. No separate security silos, but an extension of what is already in place.

How we approach a modernisation project.

1

Inventory and user interviews

We map out what the application does, who uses it every day and which hidden business rules are built into it. A few conversations with the people who really know the software save a lot of surprises later.

2

TCO and risk analysis

We lay out what it costs to keep the current application running for years to come (licences, hosting, external suppliers, security risks, lost productivity) versus the investment in modernisation. That turns it into a business decision rather than a gut feeling.

3

Decision matrix: rebuild, refactor, rehost, replace or retire

For each module, we determine the best route. Not everything needs to be torn down. Sometimes a module is perfectly fine and only needs a hosting migration; sometimes it has to be rebuilt entirely; and sometimes it can simply go because nobody uses it any more.

4

Pilot on a well-defined core flow

We start with a module that is manageable, but where success is clearly felt across the organisation. That builds confidence, delivers a working example and brings unknown risks to the surface early.

5

Full modernisation in sprints

We build the rest module by module while the old system keeps running. Users experience a gradual transition instead of a big-bang weekend. The strangler fig pattern in practice, with validation after every release.

6

Data migration and user transition

The data is cleaned, validated and migrated. Users receive training and a short run-out period in which the old and new systems run side by side, so they can get used to the new environment safely.

7

Handover to maintenance

A runbook for incidents, monitoring with clear thresholds, and clear agreements on who does what. Whether we continue to handle maintenance ourselves or you take it on in-house, both work, as long as ownership is clearly assigned.

Frequently asked questions.

What clients usually want to know first in a conversation about modernisation.

What do you actually mean by "legacy software"?
Anything where the technology stack is no longer actively maintained, or where the knowledge needed to maintain the software is no longer available. In practice, we often come across Visual Basic 6, Delphi, Classic ASP, PHP 5, WordPress 3.x, Microsoft Access with VBA, Oracle Forms and Java applets, plus discontinued technologies such as Flash and Silverlight. Even modern stacks can be functionally "legacy" if they have not been updated for years, if the original developer left long ago, or if the architecture no longer suits current requirements. Age in years matters less than how maintainable the software is right now.
What is the difference between modernisation and replacement?
With modernisation, we keep the business logic and renew the stack around it: same rules, different foundation. With replacement, we build from scratch, often with an adjusted scope because we take the opportunity to do things differently. Modernisation is safer and faster if the current logic works well; replacement is wiser if your requirements have changed significantly or if the old implementation causes so many problems that peeling it apart takes longer than starting over.
Should I replace or upgrade?
That depends on how deeply the business logic is intertwined, how outdated the stack is, and how much your requirements have changed since the original build. A PHP 5 application that works well functionally can often be upgraded to PHP 8 with a framework. A VB6 desktop application or an MS Access database almost always calls for a rebuild on a modern web stack. We advise what fits, because not everything has to start from scratch.
Big-bang or phased migration?
Preferably phased, using a strangler fig approach. We put a modern layer around the old system and replace modules within it. Users barely notice the transition, the risk per release stays limited, and you can pull the plug at any point without losing an entire migration. We only go big-bang if the old software truly cannot be broken up.
How long does a project like this take?
Too variable to give a general answer. A pilot on a well-defined core flow is sometimes live after just a few sprints. A full modernisation of a business-critical system takes several sprints, sometimes longer if there are many modules and integrations. We work with fixed sprint budgets so you can choose at any point to continue, pause or adjust the scope.
What determines the investment?
The scale of the business logic, the number of integrations with other systems, the complexity of the data migration, and how much is unknown in the old system. An Access database with a few tables is a different conversation from an Oracle Forms application with hundreds of screens. In the first conversation we give a range, and only after the inventory a concrete quote. We work without surprise costs.
What are the biggest risks of modernisation?
Losing implicit business logic is the biggest risk, which is why we spend a lot of time on discovery and user interviews. Beyond that: user resistance to change, data conversion errors, and temporarily maintaining two parallel systems during the transition. We mitigate this with side-by-side runs, validation reports, training and a phased rollout — never a cut-and-paste migration.
The original developer is gone. What now?
That is the rule rather than the exception with old software. We work from the code itself, ask around among users and reverse-engineer the business rules from the application's behaviour. Sometimes we find documentation in unexpected places — a Word document on a network drive, scripts in a mailbox. Whatever we cannot reconstruct, we validate with you before it ends up in the new version.
Can the new application go straight to the cloud?
Almost always, and it is usually a good idea. We work with Google Cloud, AWS and Azure, and can also deliver on-premise if your industry requires it. For compliance-sensitive domains — healthcare with NEN 7510, government with BIO, critical sectors under NIS2 — we deliberately choose regionally hosted infrastructure. Our page on platform migration goes deeper into the hosting side.

Talk to us about your legacy software.

A no-obligation introductory call of half an hour. We listen to what is running now, what headaches it causes, and which direction makes sense. No sales pitch, just an honest picture of what is realistic. After that, you can decide for yourself whether it is worth talking further.

Edit content