Legacy software modernization services that replace old systems without stopping the business

Our legacy software modernization services move the old PHP application, desktop program or Access database your business depends on to modern, supported software, in planned phases, with your data intact and your team working throughout.

  • Free system review call
  • Custom quotation, never a fixed package
Machine shop with a restored lathe and red paint details
  • System audit
  • Phased rebuild
  • Data migration

Worked with

  • Fortune Group
  • Classify-X
  • Aim Campus
  • Ullas
  • Signum Academy

Problems we solve

Is your business running on software nobody can safely change?

Old systems often hold years of business rules that work. The trouble is everything around them: the technology, the people who understand it and the risk of touching it.

  1. 01

    One person understands it

    The original developer has left, or one staff member knows the workarounds, and nothing is written down.

  2. 02

    Tied to one computer

    A desktop program or Access file runs on an office PC, so nobody can use it from a phone or another branch.

  3. 03

    Out of support

    Old PHP, Windows or database versions no longer get security fixes, and hosts are dropping them.

  4. 04

    Every change is a gamble

    Small updates break unrelated screens, so the team stops asking for improvements.

Our solution

Modernise in steps, not in one risky leap

We start by understanding what the old system really does, then replace it piece by piece while it keeps running.

  • Know before you change

    A written audit of features, data, rules and integrations, including the ones nobody remembers.

  • Replace in phases

    New modules take over one area at a time, so value arrives early and risk stays small.

  • Move data with proof

    Rehearsed migrations with record counts and checks, so you can trust the new system on day one.

What's included

What legacy application modernization covers

Every system is different. These are the parts most modernization projects include.

Not sure where to start?

We'll help you pick what to build first and phase the rest.

01 / 066 included

Legacy system audit

We read the code, the database and the way people actually use the system, then write down what it does, what is risky and what is worth keeping. You get a clear report even if you decide not to go further.

  • Feature and screen inventory
  • Business rules written down
  • Database and data quality review
  • Integrations and file exports
  • Security and support risks
  • Options with trade-offs
02 / 066 included

Choosing the path: rehost, refactor or rebuild

Not every system needs a rewrite. Some only need moving to supported hosting, some need their code cleaned up and upgraded, and some are best rebuilt. We recommend per module, not one answer for everything.

  • Rehost on supported servers
  • Upgrade language and framework versions
  • Refactor risky modules
  • Rebuild where it pays off
  • Retire unused features
  • Phase plan and order
03 / 066 included

Phased rebuild with the strangler pattern

New modules are built beside the old system and take over one area at a time: first reports, then orders, then billing, for example. The old system shrinks until it can be switched off.

  • Module-by-module replacement
  • Shared data during transition
  • Routing between old and new
  • Early value from first modules
  • Rollback for each step
  • Old system retired at the end
04 / 066 included

Desktop, MS Access and VB to web

Access databases, Visual Basic programs, FoxPro tools and Excel workbooks with macros rebuilt as secure web applications that work in any browser, on phones and across branches, with proper user roles.

  • MS Access to web app
  • VB and desktop rewrites
  • Excel macro workflows
  • Multi-branch access
  • Roles and audit trails
  • Printable reports kept
05 / 066 included

Old PHP application upgrades

Custom PHP applications on unsupported versions or abandoned frameworks, either upgraded and cleaned up, or moved module by module to a modern stack such as Next.js with Node.js or Django.

  • PHP version upgrades
  • Framework migration
  • Security fixes
  • Tests around key flows
  • API layer for new apps
  • Step-by-step rewrite
06 / 066 included

Data migration and cut-over

Cleaning, mapping and moving years of records, rehearsed on copies until the numbers match, then a cut-over planned to keep downtime to zero or a short, agreed window.

  • Data cleaning and mapping
  • Repeatable migration scripts
  • Record counts and totals checked
  • Parallel running where needed
  • Cut-over plan and rollback
  • Old data archived and searchable

What you get

What changes after modernization

The same business rules, on software you can rely on and improve.

  • Supported and secure

    Current languages, frameworks and security fixes.

  • Use it anywhere

    Browser access across branches, phones and home.

  • Knowledge written down

    Rules and processes documented, not in one head.

  • Ready to connect

    APIs for apps, portals and other systems.

  • Data you can trust

    Cleaned, migrated and checked records.

  • Yours to own

    Code, data and accounts in your name.

Why us

Why businesses choose Zero One Creation

  • We build and run software

    Classify-X, Social Sphere CRM, ZOC Link and ZeroVault are designed, built and run by our team.

  • Audit first, always

    You get a written assessment before we recommend any rebuild.

  • Business systems are our core

    We build ERPs, CRMs and portals, so we understand the rules inside old systems.

  • Clear written scope

    A phase plan, risks and a customised quotation for each stage.

Tell us about the old system your business can't do without. We'll tell you honestly whether to upgrade it, rebuild it or leave it alone for now.

A free system review call, then a written proposal with a customised quotation.

Our approach

How we modernise a legacy system

Open each step to see what it covers.

  1. 01.Audit

    Code, data, integrations and real usage, written up with risks and options.

  2. 02.Plan

    Path per module, phase order, data plan and cut-over approach, agreed in writing.

  3. 03.Build the first slice

    One area replaced end to end, so the approach is proven early.

  4. 04.Migrate and run alongside

    Data moved and checked, with old and new running in parallel where needed.

  5. 05.Cut over

    Planned switch with a rollback route, then the next phase begins.

  6. 06.Retire and support

    Old system archived and switched off, with support for the new one.

Common situations

Where modernization projects usually start

Most of the old systems we are asked about fall into one of these.

  • An Access database that grew into a business system

    What you notice
    Several people open the same file, it corrupts now and then, and only office PCs can reach it.
    How we fix it
    A web application on a proper database, with the same screens and reports your team knows, available anywhere.
  • A PHP app the hosting company won't support

    What you notice
    The host is retiring the old PHP version and the app breaks on anything newer.
    How we fix it
    A version upgrade with fixes, or a phased move to a modern stack if the code is beyond saving.
  • A desktop program from a vendor that has gone

    What you notice
    No updates, no support, and it only runs on an old Windows machine kept alive for it.
    How we fix it
    Rebuild the features you use, migrate the data out of its database, and retire the machine.
  • A system that works but blocks growth

    What you notice
    It runs the core process fine, but can't connect to apps, portals or new branches.
    How we fix it
    Add an API layer first, then replace modules one by one as the business needs them.

Technology

Where we modernise from, and to

We read the old stack and build on a modern, well-supported one.

Systems we modernise
Old PHP appsMS AccessVisual BasicFoxProExcel with macros
Front end
Next.jsReactTypeScript
Back end
Node.jsDjango RESTREST APIsBackground jobs
Data
PostgreSQLMySQLMigration scriptsData validation
Hosting
AWSDockerAutomated backups
Safe delivery
Automated testsFeature flagsStaging environmentsRollback plans

Options

Phased modernization, a big-bang rewrite or keep patching?

Three common ways to deal with an old system, and what each really involves.

Phased modernization, a big-bang rewrite or keep patching?
CriteriaPhased modernizationBig-bang rewriteKeep patching
Risk to daily workLow, one area at a timeHigh, everything switches at onceLow today, rising
When value arrivesAfter the first phaseOnly at the endNever really
Ability to change courseBetween every phaseHard once startedNot applicable
Security and supportFixed phase by phaseFixed at launchGets worse
Best forSystems the business runs on every daySmall systems with few usersSystems due to be retired soon

For small, simple systems a single rebuild can be the sensible choice. We'll say so.

Who we modernise for

Legacy systems across industries

Old software tends to sit at the heart of operations.

  • Manufacturing

    Production, stock and dispatch tools built decades ago.

    See the work
  • Education

    Fee, admission and result systems on office PCs.

    See the work
  • Distribution and dealers

    Order and scheme tracking in Access or Excel.

    See the work
  • Healthcare

    Clinic and billing software that only runs locally.

    See the work
  • Professional firms

    Case, job and billing records in ageing tools.

    See the work
  • Retail

    Billing and inventory systems that can't connect online.

    See the work

How we work together

Three ways to work with us

Every engagement starts with a written proposal and a customised quotation.

  • System audit

    A written assessment of the old system with options and a phase plan.

    Best for: Deciding what to do before committing

  • Phased modernization

    Rebuild, migration and cut-over, one agreed phase at a time.

    Best for: Systems the business depends on

  • Upgrade and stabilise

    Version upgrades, security fixes and tests on the existing code.

    Best for: Sound systems on outdated technology

Guide

Legacy software modernization: a practical guide

Signs it is time to modernise

Common signs include software that runs on unsupported versions, only works on specific office computers, depends on one person's knowledge, can't connect to other systems, or breaks in unexpected places when changed.

None of these alone means you must rebuild. Together, they usually mean the risk of waiting is higher than the risk of acting. Our post on technical debt audits explains how to judge that.

The main modernization paths

Rehosting moves the system to supported servers without changing the code. Refactoring cleans up and upgrades the code while keeping its structure. Rebuilding writes a new system that replaces the old one. Retiring removes features nobody uses.

Most real projects mix these. Reports might be rebuilt, the core billing logic refactored and an unused module retired.

Why big-bang rewrites go wrong

A full rewrite that switches over on one day has to match every feature and quirk of the old system before anyone benefits. Requirements change during the long build, hidden rules surface late and the launch day carries all the risk.

A phased approach delivers working modules early, lets you learn as you go and keeps a way back at every step.

The strangler pattern

Named after a vine that slowly grows around a tree, the strangler pattern builds the new system around the old one. Requests for one area, say reports, are routed to the new module while everything else still goes to the old system.

Area by area, the new system takes over until the old one has nothing left to do and can be switched off.

Finding the hidden business rules

Old systems carry rules nobody wrote down: a discount that applies only on certain days, a report that excludes a type of customer, a rounding rule the accountant depends on. Missing these is the most common cause of a failed modernization.

We find them by reading the code, comparing old and new outputs on real data, and asking the people who use the system every day.

Moving the data safely

Data migration deserves its own plan. Clean duplicates and broken records, map every old field to the new structure, write migration scripts that can be run repeatedly and rehearse on copies until record counts and totals match.

Our data migration checklist for a new software system lists the steps in order.

Cutting over without downtime

Where the system allows it, we plan cut-overs for zero downtime: syncing data continuously, switching traffic to the new module and keeping the old one ready to take back. When a short pause is unavoidable, we agree a quiet window in advance and rehearse it.

Our post on zero-downtime deployment explains the techniques in more detail.

Modernising the application vs moving to the cloud

Moving an old system to cloud servers can improve backups and access, but it does not fix outdated code. Modernising the application changes the software itself.

Sometimes the first step is a straightforward move to the cloud, followed by modernization in phases. Our cloud migration service covers that move.

Bringing your team along

People who have used a system for years have habits built around it. Keep familiar reports and screen layouts where they work, involve key users in testing each phase and train them before cut-over.

A new system that the team trusts gets used. One that surprises them gets worked around.

What affects the cost of modernization

Cost depends on the size and condition of the old system, how well it is understood, the amount and quality of data, integrations, the path chosen for each module and how much parallel running is needed.

We don't publish fixed prices or packages. After a system review call, we send a written proposal with a customised quotation, usually starting with an audit.

Before you talk to us

Frequently asked questions

Do we have to rebuild everything?

No. Some parts may only need upgrading or rehosting. We recommend a path per module after an audit.

Can our team keep working during the project?

Yes. In a phased project the old system keeps running while new modules take over one area at a time.

Will there be downtime at cut-over?

We plan for zero downtime where the system allows it. If a short pause is unavoidable, we agree the window with you and rehearse it first.

Can you convert our MS Access database to a web app?

Yes. We move the data to a proper database and rebuild the forms and reports as a secure web application your team can use anywhere.

Our original developer has left. Can you still help?

Yes. That is a common starting point. We read the code and database, talk to your users and document what the system does.

Will we lose any data?

Migrations are rehearsed on copies with record counts and totals checked. The old data is also archived so it stays searchable.

How long does modernization take?

It depends on the system's size and condition. The audit gives a phase plan with realistic timelines for each phase.

Can the new system look like the old one?

Where your team relies on familiar screens and reports, yes. We keep what works and improve what doesn't.

Do you upgrade old PHP applications?

Yes. We upgrade PHP versions and frameworks where the code is sound, or move it module by module to a modern stack where it isn't.

Is moving to the cloud the same as modernising?

No. Moving to the cloud changes where the software runs. Modernising changes the software itself. Many projects do both.

Who owns the new system?

You do. Code, data, servers and accounts are set up in your name.

How much does legacy software modernization cost?

It depends on the system, data and chosen path. We do not publish fixed prices; we send a customised quotation after a system review call.

Contact us

Tell us about your old system.

Share what it runs on, who uses it and what worries you about it. An engineer reviews every enquiry and gets back to you to set up a call.

We use your details only to reply to this enquiry. See our privacy policy.