Your Delphi application has been running for years and is full of domain knowledge. But the components are ageing, and Delphi developers are becoming rare. We port your software to C# and .NET. Step by step, with a modern user interface and without your operations coming to a standstill.
Why Delphi applications should move now
- Developers are scarce. New colleagues learn C#, Java or Python, hardly ever Delphi. The people who know the code will often retire soon.
- Components without a vendor. Many applications depend on add-on components for tables, reports or databases that nobody maintains any more.
- Old database access. The Borland Database Engine (BDE) has not been developed further for many years. Older applications still use it nevertheless.
- Unicode and 64-bit. Applications from before Delphi 2009 work with ANSI strings and only run as 32-bit programs.
- Security and the CRA. For products that you sell, the Cyber Resilience Act requires security updates and a software bill of materials. That is difficult with old components.
Port or update Delphi?
Not every Delphi application has to move to .NET. Delphi is still being maintained. If your team has Delphi expertise and is to keep it, upgrading to a current Delphi version can be the more economical route. If developers are lacking or the software is to grow together with other .NET systems, C# pays off. We tell you openly what suits your case.
What becomes of your Delphi application
- Forms. VCL forms become a new user interface with WPF or WinForms, or a web application if you wish.
- Database access. BDE, dbExpress or FireDAC become Entity Framework or ADO.NET. Your database stays or moves to SQL Server, MariaDB or PostgreSQL.
- Reports. We rebuild reports from QuickReport or FastReport with a current reporting tool.
- Business logic. We transfer it to C# and safeguard it with automated tests.
- Transition. While both worlds are running, we call existing Delphi DLLs from C#. This way the changeover works module by module.
Our approach
- Inventory. Record units, forms, components, database and interfaces.
- Capture behaviour. Record the results of the old application with real data, as a benchmark for the new one.
- Prototype. Port one module first so that you see the user interface and technology early on.
- Module by module. Each module goes into production individually.
- Training. If you wish, we train your team in C# and .NET.
Example: measuring device software from Delphi to C#
A measuring device manufacturer had been using its own Delphi software for decades. After consulting, planning and on-site training, we are porting it to C#, WPF, MariaDB and Entity Framework in an agile team of ten people. The new software is already in use internally. View the project
Getting started: the Modernisation Check
In the Modernisation Check, we analyse your Delphi code, 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
Frequently asked questions about Delphi migration
Can it be done automatically?
Partly. Tools translate simple code, but not the user interface and not the components. We use them where they save time and check the result with tests.
How long does a Delphi migration take?
That depends on the scope. Small applications move in weeks, large systems in phases over months. You receive the schedule with the phased plan from the Modernisation Check.
Can our customers continue to use the old version?
Yes. The Delphi version stays in operation until the new one has all the functions.
- Modernising legacy software: moving Delphi, VB6 and MFC to .NET step by step
- Software modernisation and porting
Get in touch
Briefly describe your Delphi application. We will get back to you quickly and advise you without obligation. Call +49 761 28522110 or use the contact form.
kununu