Your software has been running reliably for years. But the technology behind it is ageing. Developers retire, vendors discontinue support, and since the Cyber Resilience Act you must be able to deliver security updates for your products. We modernise your software step by step, without your operations coming to a standstill.
Important now: the Cyber Resilience Act
Since 11 September 2026, manufacturers have had to report actively exploited vulnerabilities in their products within 24 hours. From 11 December 2027, the EU regulation applies in full. Products with software will then need a software bill of materials, a defined process for handling vulnerabilities and security updates throughout the entire support period, usually at least five years.
Legacy software in particular struggles with this. Libraries with no vendor behind them, no automated build pipeline, no secure route for updates. That is why modernisation and the CRA belong together. If you are rebuilding anyway, build it so that it meets the requirements from the start.
Read about the Cyber Resilience Act Request a CRA Check
When modernisation pays off
- Only one person really knows the code.
- The technology is no longer supported, such as Visual Basic 6 or .NET 8, whose support ends on 10 November 2026.
- Every new feature takes weeks, and every change introduces new bugs.
- The software only runs as a 32-bit program or causes problems under Windows 11.
- Your customers ask about security updates, a software bill of materials or CE marking under the CRA.
- The user interface looks outdated and puts off new customers.
What we modernise
- Cyber Resilience Act. We review your product against the requirements of the CRA and implement the measures.
- Delphi Migration. Delphi applications to C# and .NET or to a current Delphi version.
- VBA Migration. Excel and Access solutions with VBA become a stable application with a database.
- VB6 Migration. Visual Basic 6 programs to C# and .NET.
- MFC Migration. Replace MFC user interfaces and keep the proven C++ core.
- .NET Migration. From .NET Framework, .NET 8 or .NET 9 to .NET 10.
- Porting Between Programming Languages. C++, C#, Java, Visual Basic and more.
- Porting to Operating Systems. Windows 11, Linux, macOS and mobile systems.
Our approach
Rewriting everything takes years and only delivers value at the very end. That is why we proceed step by step. New code grows around the old code until the old code can be switched off. Every step goes into production.
- Inventory. We record modules, database, interfaces and dependencies and measure the code.
- Capture behaviour. We record what the old software delivers with real inputs. We measure every new line against this.
- Target architecture. Together with you, we choose the language, user interface and database and decide what may stay.
- Module by module. We start where it hurts most and put each module into production individually.
- Handover. Documentation, automated tests and, if you wish, training for your team.
We work remotely or on site at your premises. Your day-to-day business carries on, and the old software remains usable until the new one replaces it.
What you gain
- Code that new developers can also understand and extend.
- Security updates that you deliver quickly and verifiably.
- A modern user interface that your users enjoy working with.
- Fewer bugs and shorter paths to new features.
Getting started: the Modernisation Check
In the Modernisation Check, we analyse the code and architecture of your software, propose a target architecture and calculate when the port will pay off. You receive an analysis report with target architecture, cost-benefit analysis and phased plan. The Modernisation Check costs a fixed price of €3,490 plus VAT. If you then commission the follow-up project, we credit 50% of the package price.
Request package Book in the shop
Examples from our projects
- Measuring Device Software: Delphi Ported to C#
- AutoCAD Add-in for Civil Engineering: ObjectARX to .NET
- Porting an Image Processing Library
More from our expertise
- Modernising legacy software: moving Delphi, VB6 and MFC to .NET step by step
- Cyber Resilience Act: what software manufacturers must have done by the end of 2027
- Creating an SBOM: the software bill of materials for the Cyber Resilience Act
- Porting an AutoCAD add-in to BricsCAD: what stays the same and what doesn’t
Frequently asked questions about software modernisation
Port or rewrite?
A step-by-step conversion is usually cheaper and safer. The old software contains years of knowledge that is not written down in any requirements specification. A rewrite pays off when the processes are also changing fundamentally. We clarify this in the Modernisation Check.
What does a port cost?
That depends on the size and condition of the code. After the Modernisation Check, you know the effort for each phase and when the conversion will pay off.
Can we keep working during the modernisation?
Yes. The old software stays in operation until the new one replaces it completely. Your team can continue fixing bugs in parallel.
Do you also work with our team?
Gladly. Many customers modernise together with us. If you wish, we train your team in the new technologies.
Get in touch
Briefly describe your software and your goal. We will get back to you quickly and advise you without obligation. Call +49 761 28522110 or use the contact form.
