Four paths for an old Delphi application
| Path | Suits | Watch for |
|---|---|---|
| Upgrade to current Delphi | Sound business logic, a Windows desktop app, a team that knows Delphi | Components without source code; database access through the BDE |
| Upgrade, then add a web or mobile front end | Users who need access outside the office | Business logic tangled into the screens |
| Move to another stack, module by module | Hiring difficulty, or a product that must become web-first | Running old and new side by side for a while |
| Rewrite in one go | Rarely the right choice | Everything the old system quietly did that nobody wrote down |
What drives the cost
Embarcadero’s own migration guidance names the usual issues (Embarcadero, migration roadmap, 12 October 2020):
| Driver | What Embarcadero says | Why it costs |
|---|---|---|
| Unicode strings | “Unicode support was added to RAD Studio, Delphi and C++Builder starting with the 2009 version.” | Code written before 2009 that treats text as bytes needs checking line by line |
| The Borland Database Engine | “The Borland Database Engine (BDE) has been deprecated, and beginning with version XE8 the BDE has been removed from the Delphi installation.” | Every screen and report that reads data through it has to move to a modern data access layer |
| Third-party components | “The 3rd party plug-ins (libraries) need to be rebuilt in the current Delphi version. Having the source code makes this easier.” | Missing source code means replacing, not rebuilding |
| 64-bit | “Ever since Delphi XE2, it has been possible to generate Delphi 64bit applications from the same code base as your traditional Windows 32bit Delphi code.” | Code that assumes 32-bit pointers or integers needs changes |
Checked 5 October 2026. Delphi itself is current: Embarcadero released RAD Studio 13.2 Florence on 17 September 2026.
Beyond these four, the familiar legacy drivers apply: reports and the report engine, how much business logic lives inside the screens, missing tests, and developers who have left.
Why Delphi is different from most legacy stacks
With VB6 or AngularJS, the platform itself is finished and leaving is the only long-term option. Delphi is still being developed, so staying is a legitimate choice. The question is not “how do we escape Delphi?” but “what does this application need to do in five years, and who will maintain it?”
What to have ready before you ask for a quote
- Which Delphi version it was last built with
- Which third-party components it uses — and whether you have their source code
- How it reaches its database, and which reports it produces
- Who uses it, and which parts can never go down
How Pricient quotes a modernization
Modernization starts with a Legacy System Specification Assessment. It produces a written specification, a risk register, a keep-vs-replace cost comparison and a staged replacement plan, and its fee is credited in full against the first build stage if it starts within 90 days of the report. You can start with a conversation about the system; we ask for read-only code access only when the assessment begins. Tell us what you are running and you get a fixed quote for the assessment.