Services
Software modernisation
Software modernisation and legacy system replacement: step by step, with data migration and without downtime.
We modernise or replace old software: PHP applications, FileMaker and Access databases, spreadsheet solutions that have grown over the years and outdated online shops. First we check whether an update is enough. If not, we replace the legacy system area by area, migrate your data and keep your business running throughout.
Typical triggers
Typical triggers
Clients get in touch when one of these situations arises.
- 01Your PHP application runs on PHP 8.2 or older and will receive no security updates from 2027.
- 02The developer who built the solution is no longer available, and nobody dares to touch the code.
- 03A FileMaker, Access or Excel solution carries a core process but depends on a single person.
- 04Your online shop runs on a system without updates, and every extension becomes more expensive and riskier.
Software modernisation
What you get
Assessment with a clear recommendation
We review code, data and interfaces and tell you whether an update is enough, a standard product fits or a step-by-step replacement costs less.
Immediate security measures
The old application is secured so that it keeps running safely until it is replaced, for example with an update to a supported PHP version.
Replacement in stages
The area with the greatest benefit comes first. Your team works with the new solution early, while the old system handles the rest in the meantime.
Data migration with a trial run
Duplicates and gaps are cleaned up according to fixed rules. The migration runs at least once as a trial before the switch-over.
Integration with ERP and accounting
The new solution is connected to your systems, so nothing is entered twice or transferred by hand any more.
Documentation and source code in your hands
You receive the repository, architecture description and operations manual, so your software never again depends on a single person.
Four routes for old software
| Route | Fits when | Price range |
|---|---|---|
| Update | the code is maintainable and the application still reflects your process well | own application on a current framework around CHF 2,500 to 10,000 |
| Modernise step by step | the application has grown over the years and is business-critical | CHF 40,000 to 150,000, spread over stages |
| Replace with standard software | an off-the-shelf product covers around 80 per cent of your process | licence and rollout, CHF 3,000 to 15,000 per integration |
| Rebuild | the code cannot be saved and your process is changing significantly | CHF 25,000 to 100,000, larger platforms more |
In practice: Bandex replaces technology from 2012
The Bandex website and B2B shop ran on a PHP application with a framework from 2012 that has not received security updates for years. Instead of patching on, we are rebuilding the platform: products, prices and stock levels come automatically from SAP, every business customer sees their own prices and can order from a mobile phone too.
Similarly at Extremprint: the online print shop is moving from a WordPress shop with WooCommerce to an open shop platform where customers design business cards and flyers directly in the browser.
- 795 products with prices from SAP in the new shop
- technology more than ten years old replaced
- ERP integration built so that a later ERP switch does not affect the shop
Software modernisation
Approach
01
Intro call
20 minutes, free of charge. We establish which application is affected, how urgent it is and whether an update might be enough.
02
Assessment
Review of code, data, interfaces and security, plus interviews with users. Result: recommendation, immediate measures, stage plan and cost ceiling.
03
Secure
The old application is brought to a supported version or shielded so that it runs safely until it is replaced.
04
Replacement in stages
The area with the greatest benefit first. The first stage is live after six to ten weeks, the rest keeps running in the old system.
05
Data migration and switch-over
Clean up data, migrate it in a trial run, train the team. Finally the old system is switched off and archived.
Effort
Price range
- Price range
- CHF 40'000 to 150'000
- Duration
- 3 to 8 months
Non-binding estimate, excl. VAT.
What drives the effort
The range applies to step-by-step modernisation or replacement in stages. The effort is driven by the scope of functions, the quality of the data and the number of integrations. A plain update of your own application on a current framework costs around CHF 2,500 to 10,000. It all starts with the assessment as a discovery phase at a fixed price of CHF 4,000 to 9,000.
Technologies
- C# / .NET
- Next.js
- TypeScript
- PostgreSQL
- Docker
Software modernisation
Frequently asked questions
What does it cost to modernise old software?
It depends on the route. Updating your own application on a current framework costs around CHF 2,500 to 10,000, a step-by-step modernisation or replacement in stages CHF 40,000 to 150,000. The price becomes binding with the assessment, a discovery phase at a fixed price of CHF 4,000 to 9,000. All amounts are guide values excluding VAT.
Can we keep working normally during the modernisation?
Yes. The old application keeps running while one area after another is replaced by the new solution. The first stage is usually live after six to ten weeks, the switch-over happens stage by stage and with parallel running if you wish. Until the replacement is complete, we keep the old system secured.
Is modernisation also worthwhile for an outdated online shop?
Yes, as soon as the shop system no longer receives security updates or every extension costs more than a rebuild. Shopware 5, for example, has not received security fixes since the end of July 2024, according to the vendor. For Bandex we are replacing a B2B shop built on a framework from 2012 with a new platform connected to SAP.
Is it worth simply updating an old PHP application?
Yes, if the code is maintainable and the application still fits the way you work. In that case an update is the cheapest option and removes the immediate security risk. If the code has no tests, no documentation and depends on one person, an update only postpones the problem. A short code review shows which case applies.
How long can we keep running an old PHP application securely?
Only as long as its PHP version receives security updates and someone can still change the code safely. PHP 8.2 receives no security updates from 1 January 2027, and PHP 8.1 and older already received no regular updates for the critical vulnerabilities of October 2026. Depending on the state of the application, the next step is to update it, modernise it step by step or replace it.
Can we switch over gradually?
Yes, and we recommend it. The area causing the most pain is replaced first, while the old solution carries on for the rest. The benefit shows early and the risk per step stays small.
What happens to the data in Excel or FileMaker?
It is cleaned up and migrated. Migration is a stage in its own right: we analyse the existing data, define rules for duplicates and gaps, and carry out at least one trial run before the switch.
What should we do with an old Access database?
First check which Office version it runs on. Access 2016 and 2019 have received no security updates since 14 October 2025, and Access 2021 since 13 October 2026. If several people rely on the database for an important process, a web application with a central database is usually the more sustainable option. Tables and queries can be carried over.
Let us talk about your case.
20 minutes are enough to find out whether a custom solution is worth it for you.