Legacy NHS Application Migration

Legacy NHS application migration is a service we provide for NHS teams and healthcare suppliers that need to replace ageing Microsoft Access databases, desktop tools and older line-of-business systems with maintainable applications. We recently completed a Microsoft Access to web application migration for one of our NHS customers, and the customer is happy with the result. The old system had served its time. Like many Access databases, it started life as a practical fix and slowly became a business-critical application wearing comfortable slippers.

The point of this article is simple: if your organisation depends on a legacy application that is becoming hard to support, we can help you move it to a modern platform without throwing away the business knowledge already built into it.

The original Microsoft Access application had reached its limit

The original application had been in use for many years. It handled important operational data, but it was becoming increasingly difficult to maintain, extend and support.

It was also not designed for effective multi-user access. That is a common problem with older Microsoft Access applications. They work well for small teams at first, then the organisation grows, the data grows, and suddenly everyone is sharing the same database file like it is the office biscuit tin.

In practice, the issue was not only the technology. The application contained years of business knowledge. The safest migration path was to preserve that knowledge while replacing the weak parts around it.

We did not rebuild everything from scratch

Rebuilding every feature from nothing would have taken longer and cost more. It also would have introduced avoidable risk.

Instead, we used functionality that we had already developed and successfully implemented across multiple projects. This is the main reason the migration was fast and cost-effective.

Not every legacy application needs a completely bespoke rebuild. If the hard parts already exist and have been tested in real projects, it is usually better to reuse them and focus the budget on the customer's data, workflow and business rules.

The new NHS web application uses proven components

The new web application includes the kind of core functionality most business applications need before the customer-specific work even begins.

Role-Based Security - controls what individual users and groups can access.
User Registration - provides a complete process for registering and managing users.
Password Recovery - gives users secure self-service password recovery.
Page Designer - allows configurable application pages without bespoke development for every screen.
Grid Designer - provides flexible data grids that can be configured for different requirements.
Forms Designer - supports configurable forms for entering, viewing and editing data.
Rules Engine - allows business and data-processing rules to be configured without hard-coding every requirement.
Incremental Processing - processes only new or changed data where appropriate.
Excel Import and Export - lets users continue working with familiar Excel-based processes when required.
Email Notifications - sends automated notifications triggered by application events and business rules.

These are not experimental features. We had already implemented them multiple times. That matters, because nobody wants a password recovery module to discover its personality during user acceptance testing.

The implementation work was reduced to three areas

Because the reusable application platform already existed, the main implementation work for the new NHS application was reduced to three practical areas.

Design the database tables.
Import the existing data.
Create the customer-specific data processing and business rules.

This significantly reduced both development time and cost. The customer was not funding the development of user registration, security, password recovery, grids, forms, Excel integration or notifications from the ground up.

Instead, development focused on the parts that made the application theirs: the data model, the migrated records, the screens, and the business rules.

The migration was completed and accepted

This was not a prototype, a sales demo, or a half-finished rewrite waiting for the next committee meeting. The migration was completed, the application replaced the ageing Microsoft Access system, and the NHS customer is pleased with the outcome.

That matters because legacy application migration is not only about writing code. It is about giving users a system they trust enough to use every day. If the new application looks impressive but fails to support the real workflow, it has not solved the problem. It has merely changed the wallpaper.

The application can be hosted in the cloud or locally

The new application can be hosted in the cloud or deployed locally, depending on governance, infrastructure and security requirements.

For some NHS and healthcare environments, local hosting is preferred because data stays inside controlled infrastructure. For others, cloud hosting makes support, updates and remote access easier. The right answer depends on the organisation, not on what a vendor wants to sell this quarter.

If a desktop application is necessary, we can also create one. A web application is often the best fit for multi-user access, but there are still cases where a desktop app makes sense, especially when local hardware, offline access or existing operational procedures require it.

Supported database platforms

We can build migrated applications on widely used database platforms, including:

PostgreSQL
Oracle
Microsoft SQL Server
MySQL
MariaDB
SQLite

The source system can be Microsoft Access or another legacy database. The target platform is chosen around supportability, licensing, performance, backup strategy and internal skills.

This is the legacy application migration service we provide

This NHS project is a clear example of our legacy application migration service. We take an older application, preserve the valuable data and business logic, and replace the fragile parts with a maintainable application that supports modern usage.

The result was a fast and cost-effective migration from an ageing Microsoft Access database to a maintainable, multi-user web application. The customer kept the data and business processes they depended on, while gaining a platform that is easier to support and extend.

If you have a similar Microsoft Access database, FoxPro system, old desktop application, or internal tool that people still rely on, this is exactly the kind of work we do. We can review the existing application, identify what should be migrated, and build a replacement that fits the way your team actually works.

We are also honest about when not to do this. If your Access database is used by one person, changes twice a year, and causes no support problems, migration may be unnecessary. Put the budget somewhere more useful. Possibly coffee. Possibly backups. Ideally both.

Useful related pages

For background on Microsoft Access and NHS digital guidance, see Microsoft Access support and NHS Digital services.