Legacy System Modernisation

Signs your old system is holding you back

• The person who built it has left, and nobody wants to touch it
• It runs on an old Windows Server, such as 2008 or 2012, that is out of Microsoft support
• Every Windows or SQL Server update breaks something
• It can't connect to the tools you use now, like Xero or Stripe
• Your insurer or auditor wants access logs or encryption it can't provide
• Staff keep side spreadsheets because adding a field is too hard

How we replace it, one piece at a time

Switching an old system for a new one in a single day is risky. If something is wrong on launch day, everything is wrong at once.

So we work in steps. We rebuild one part, such as quoting, and move staff onto the new version while everything else stays on the old system. Then we do the next part. The old system shrinks until nothing is left. Developers call this the strangler-fig approach.

For you, it means you use new parts early, problems stay small and easy to undo, and staff learn the new system bit by bit.

Common migration paths

MS Access to a web app

Data moves to SQL Server or PostgreSQL. The screens are rebuilt as a web app, and reports become dashboards or PDF exports. Most small and medium databases cost AU$25,000 to $80,000.

Access 2021 support ends on 13 October 2026. See your options on our MS Access database replacement page.

Classic ASP, Web Forms or older .NET Framework to modern .NET

Often the SQL Server database can stay, and we replace the application around it with ASP.NET Core or Next.js. Typical cost: AU$40,000 to $150,000.

VB6, FoxPro or Delphi desktop programs to a web app

Data moves to a modern database and the program is rebuilt as a web app that works on any device. Typical cost: AU$50,000 to $200,000, depending on how complex the work is.

Free legacy system review

Book a free 30-minute call. We look at your system over screen share and tell you the realistic options and rough costs. That includes leaving it alone if it is stable and doing its job.

For your IT person

New systems are usually ASP.NET Core or Blazor on current .NET, or Next.js, with SQL Server, Azure SQL or PostgreSQL, hosted on Azure or AWS. For a step-by-step replacement we put a routing layer in front of the old app, so new pages take over one route at a time, and sync data between old and new where both need it. Migration scripts are rerun into a test environment until record counts match, and source IDs are kept so every record can be traced.