1. Home
  2. Services
  3. Legacy app modernisation

Legacy app modernisation: rebuild old internal systems in stages, without stopping work

We document what the old system does, rebuild it as a modern web app in stages and keep data in sync between old and new. Teams move across one group at a time, typically over ten to twenty weeks.

Typical timeline
10–20 weeks
Your quote
Fixed, in writing
Good for
VB6, Lotus Notes, Delphi and old custom systems that still run part of the business.

Who it’s for, and who it isn’t

A good fit
  • VB6, Lotus Notes, Delphi and old custom systems that still run part of the business.
  • Only one person really understands it
  • It only runs on an old version of Windows
Probably not for you
  • Systems with a supported off-the-shelf replacement that fits
  • Rebuilds that must finish in a single big-bang weekend

What changes

✕BeforeAn internal system in VB6, Lotus Notes or Delphi that one person still understands.
✓AfterA modern web app, rebuilt in stages while the old system keeps running.
For the people using it
  • A browser app that works on any device
  • Familiar workflows, without the workarounds
For your business
  • Knowledge out of one person’s head and into documentation
  • Old and new run side by side until you switch
The guide

Replacing legacy internal systems in stages

Old internal systems built in VB6, Lotus Notes or Delphi often still run important parts of the business. The risk grows every year: fewer people understand them and the platforms they run on are out of support.

We document what the system does, rebuild it as a modern web app in stages and keep data in sync between old and new. Teams move across one group at a time, and the old system is retired only when nothing depends on it.

Signs you need this

  • Only one person really understands it
  • It only runs on an old version of Windows
  • It can’t be used remotely
  • Its data is re-keyed into other systems
Try it · Legacy risk

How risky is your legacy system?

Tick what’s true for the system you’re thinking of replacing.

How risky is your legacy system?
0 / 5
risk factors
Low
business risk
Within 12 mo
when to start planning
Manageable, for now

Document it now while the knowledge is available, and plan a staged replacement over the next year.

What’s included

Scope, price and timeline are fixed in writing before work starts.

  1. 01Process and feature inventory
  2. 02Staged rebuild plan
  3. 03Data migration and sync
  4. 04User acceptance testing
  5. 05Decommissioning the old system

How it works

  1. Weeks 1–2

    Audit

    Inventory of content, data, integrations and every live URL.

  2. Weeks 2–3

    Map

    Every page, field and redirect mapped to the new platform.

  3. Build

    Rehearse

    Full trial migrations on staging until the numbers reconcile.

  4. Cutover

    Switch over

    A planned window with a tested rollback, agreed in advance.

  5. 30 days

    Hypercare

    Daily checks on traffic, errors and data after launch.

Risks we remove

What usually goes wrong with legacy app modernisation projects, and what we do about it.

01

Hidden rules lost in the rebuild

Interviews, code review and report analysis before design starts.

02

Teams stuck between two systems

Data stays in sync until each team has moved across.

03

Knowledge in one person’s head

Everything is documented as we go.

Worked example

A typical staged rebuild

A distributor runs order handling in a VB6 application that only two people understand. Weeks one to three document every screen, report and batch job with the people who use them.

The web replacement is built module by module, with data synced both ways. The sales team moves first, then the warehouse, then finance. The old system is retired when nothing depends on it.

An illustrative example of how we would run this kind of project, not a client case study.

Technology we use
VB6Lotus NotesDelphiReact.NET 10PostgreSQL
Have a project like this?

Options for an ageing internal system

Keep runningBuy a packageStaged rebuild
Fits your processYesPartlyYes
Risk over timeRisingLowLow
Works remotelyRarelyYesYes
Free quote · no obligation

Talk to a Legacy app modernisation specialist this week.

Leave your email and a line about what you need. We reply with questions or a price range. Prefer to talk? Book a free 30-minute call.

No spam. One reply from a real person.

Legacy app modernisation: questions, answered

How do you work out what the old system does?
Interviews with the people who use it, plus a review of the code and data. Hidden rules often live in reports and batch jobs.
Can we keep using the old system during the rebuild?
Yes. Old and new run side by side with data in sync until the switch.
What happens to historical data?
It is migrated and reconciled, or archived in a searchable format if it is no longer needed day to day.
How does pricing work?
After a free scoping call you get a written proposal setting out the scope, the cost and a planned timeline, so you know what you are agreeing to before work starts.
Do I own what you build?
Yes. Code, designs, content and accounts are yours from day one, in accounts you control.

Another question? Email us or book a free call.

Often paired with

All services →