Leading Low Cost Delphi Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
Bring it forward before you think about replacing it.
For businesses running an application written in Delphi, often Delphi 5 or 7. We assess the code and its components, keep it supported, bring it up to a current Delphi where that is the better answer, and replace it in stages where it is not.
More about this service
We are an Australian team working with businesses in the United States, the United Kingdom, New Zealand and Australia. Every engagement starts with a scoped technical assessment, so the estimate that follows is based on your code and your data.
- Assessment A scoped technical review before any estimate
- 18+ yrs Building business software
- Independent No licence commission, no reseller agenda
- US UK NZ AU Australian team, no account managers
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
Still fast, still stable, and stuck in 2002
Delphi 7 was extraordinarily popular and extraordinarily stable, which is why so much business software was built with it and why so much of it is still running. It compiled to a single fast program with nothing else to install, and that self-sufficiency is what let it survive unattended for twenty years.
Read more
The obstacles are practical, not mysterious: component sets from companies that no longer exist, database access through the Borland Database Engine, which is deprecated, and text handling that changed in 2009, so old code does not simply open in a current version. Each has a known answer.
Our Delphi developer service is for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide. It covers three kinds of work: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
Three ways forward for a Delphi application
The second is the one most often overlooked.
-
Keep it and support it
The application stays on its current Delphi version. We set up a build environment on a machine kept for the purpose, fix faults, make changes, and write down which components it needs. This suits a program that works and mainly needs somebody who can change it.
-
Bring it up to a current Delphi
The same code is migrated to a current version. Text handling is updated, components are upgraded or replaced, and the Borland Database Engine gives way to a supported data layer. It stays a fast desktop program, on tools that are still maintained.
-
Replace it in stages
Where people need to work from a browser, from other sites or from a phone, modules are rebuilt as a web application one at a time against the same database.
What we do with Delphi applications
Six kinds of work. Most engagements are two or three of them.
-
Delphi maintenance
Faults fixed and changes made in existing units and forms, from the project source.
-
Component audit
Every third-party component listed, with whether it is still sold, has a successor, or has been abandoned.
-
Version migration
Code moved from Delphi 5, 6 or 7 to a current Delphi, including the change in text handling and the option of a 64-bit build.
-
BDE replacement
Database access moved off the Borland Database Engine onto FireDAC, which is what Embarcadero recommends.
-
Database moves
Paradox and dBASE tables, or an old InterBase database, moved to SQL Server, PostgreSQL or Firebird and reconciled.
-
Staged replacement
Modules rebuilt as a web application one at a time, where a desktop program no longer suits the work.
Supporting it, migrating it and rebuilding it are different projects
Each trades cost against how much of the old program remains afterwards.
-
Stay on the old Delphi
Lowest cost. The program is documented and supported. It stays tied to old components and to a data layer nobody maintains.
-
Migrate to a current Delphi
Most of the code is reused and staff keep the screens they know. The program ends up on maintained tools. It is still a desktop program, installed on each computer.
-
Rebuild as a web application
Nothing depends on Delphi afterwards, and the application can be used from anywhere. It takes longest, and is only worth it when remote or mobile use is a real need.
What a Delphi assessment looks at
Delphi the product is current. The risk is in the version gap, the components and the data layer. The release and BDE facts are from Embarcadero.
-
Which version
Delphi 5, 6 and 7 are the usual ones. Embarcadero released RAD Studio 13 Florence in September 2025. The distance between the two is the size of the migration.
-
Whether the source is complete
Units (.pas), forms (.dfm) and a project file (.dpr), plus the source or installers for every component. A site that holds only the compiled program can run it but cannot change it.
-
Third-party components
Grids, report builders and other component sets. Abandoned components that came without source are the hard cases, and they are found first.
-
The Borland Database Engine
Embarcadero states that the BDE is deprecated and will not be enhanced, and recommends FireDAC in its place. The BDE has not been part of the Delphi installation since XE8.
-
Text handling
Delphi changed how it stores text in 2009, so that every language is supported. Code that works on text one byte at a time, and files written by the old program, need care in a migration.
-
The database
Paradox or dBASE tables, InterBase, Firebird, SQL Server or Oracle. Tables kept as files are usually moved to a database server at the same time as the BDE goes.
-
Reports
Report layouts built with the report tools of the time. They are often the largest single part of the work.
-
32-bit and Windows
Old Delphi builds 32-bit programs, which generally still run on current Windows. Drivers, printers and anything the program connects to are tested, not assumed.
A Delphi 7 application nobody can rebuild from source?
What the assessment needs from you
A fixed-scope piece of work with a written result: the options, the risks of each, and a staged estimate. No production data is sent by email. We agree a secure way to share it first.
-
Version
The Delphi version the program was built with, and the Windows versions it runs on.
-
The source
Whether the full project exists, where it is kept, and whether anybody has compiled it recently.
-
Components
Any third-party components you know of, and whether you hold their installers and licences.
-
The database
What the data is stored in, its size and where it lives.
-
Reports
How reports are produced, and which ones the business cannot do without.
-
Users and machines
How many people use it, and how it gets onto a new computer today.
-
Integrations
Files in and out, devices, and other systems that share the database.
-
What is hurting
The two or three problems that started the conversation.
-
The way back
How long the business can run on the old system if a cutover has to be reversed.
From assessment to a supported application
By video call and screen share, at meeting times agreed to suit you.
-
Technical assessment
We establish the version, what source you hold, every component the program needs and how it reaches its data. You get a written list of options with the risks of each and a staged estimate.
-
A working build
The project is made to compile on a machine kept for the purpose, and the result is compared with what you run today. Until that works, no change is safe.
-
Proof of concept
One representative piece, usually a few forms migrated to a current Delphi or the data layer replaced on a copy, is taken end to end.
-
Staged work
The work is done in stages agreed from the assessment, each with its own scope and estimate, starting with whatever is hurting the business most.
-
Comparison and user testing
Old and new are run side by side on the same data, and your staff test the work they do every day.
-
Cutover and support
Each switch is planned with a way back. We watch the first days of live use, then maintain the system for as long as it stays in service.
What people ask us about Delphi
Is Delphi still supported?
Yes. Embarcadero still develops Delphi and released RAD Studio 13 Florence in September 2025. Old versions such as Delphi 7 are long out of support, and so is the Borland Database Engine that many of them use.
Delphi is still sold. Why would we move?
Often you should not, and we will say so. The trigger is usually a component maker that no longer exists, a need for remote or browser access, or not being able to find anyone to make a change.
Can Delphi 7 code be opened in a current Delphi?
Not without work. Text handling changed, and the third-party components are usually the harder half. It is a project, not a file conversion.
What replaces the BDE?
FireDAC in a current Delphi, which is what Embarcadero recommends, or an ordinary database layer if the application is being rebuilt for the web. Either way the BDE has to go before much else is possible.
Should it become a web application?
Only if remote access, working across sites or mobile use is a real requirement. For a fast internal tool used at desks, a current Delphi build can be the cheaper and better answer.
We have lost some of the source. Is that fatal?
Not necessarily. The forms inside a Delphi program can usually be recovered, and the database survives regardless. It changes the estimate. It does not end the conversation.
Do you provide Delphi developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on Delphi work for businesses in Sydney, Melbourne, Brisbane, Perth and Adelaide, and elsewhere in Australia. The work runs by video call and screen share, with secure access to a copy of your system. The service is the same in every city: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
How does this work from the United States, the United Kingdom or New Zealand?
By video call and screen share, at meeting times agreed to suit you, from discovery to handover. Confidentiality, who can reach your systems and where your data is held are agreed in writing before work starts.
What does it cost?
The assessment is a fixed-scope piece of work with an agreed fee. The estimate for anything after it comes from what the assessment finds, in stages, so you are not asked to commit to a whole project on a guess.
Sending your details…
You can stay on this page while we send it.
Tell us about your Delphi application
What the application does, the Delphi version, whether you hold the source, and what is forcing the question. Include your country so we can suggest meeting times. Please do not send production data.
Prefer a quick chat? Call 0425 531 127. We answer it ourselves, in Australia.
Kasun Wijayamanna, founderYou deal with Kasun from scope to delivery. No account managers and no offshore handoff.