Leading Low Cost PowerBuilder Developers Sydney, Melbourne, Brisbane, Perth, Adelaide
The product is still developed. Your version may not be.
For businesses running an application built in PowerBuilder, on a Sybase, SAP or Appeon version. We assess the code and its DataWindows, keep it supported, upgrade it where that is the better answer, and modernise or replace it in stages.
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 supported, but try hiring someone who writes it
PowerBuilder built serious line of business applications through the 1990s and 2000s, especially in finance, insurance and logistics. The DataWindow is the reason those applications were quick to build and the reason they are hard to replace. It holds the query, the layout and the update rules in one object, so behaviour is not where a developer new to it would look.
Read more
The product itself is alive. Appeon took over development from SAP in 2016 and still releases new versions. What has thinned out is the pool of people, and many applications sit on Sybase or SAP versions that stopped being maintained years ago. So the first question is not whether to leave PowerBuilder. It is which version you are on, and what an upgrade would take.
Our PowerBuilder 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 PowerBuilder application
The second is the one most often overlooked.
-
Keep it and support it
The application stays on its current version. We maintain the code, document the DataWindows and remove the known risks. This suits a system that works and mainly needs to stop depending on one or two people.
-
Upgrade to a current PowerBuilder
The application is migrated to a version Appeon still maintains. The code and the DataWindows are kept, and the application runs on current Windows and database versions again. This is usually much less work than a rewrite.
-
Replace it in stages
Modules are rebuilt as a web application against the same database, one at a time, with both applications live during the change. This suits a business that cannot hire PowerBuilder skills and does not expect to.
What we do with PowerBuilder systems
Six kinds of work. Most engagements are two or three of them.
-
PowerBuilder maintenance
Faults fixed and changes made in existing PowerScript and DataWindows.
-
Version upgrades
Applications moved from Sybase and SAP releases to a version Appeon maintains, then tested screen by screen.
-
DataWindow inventory
Every DataWindow listed with its query, its update rules and where it is used, so nothing depends on memory.
-
Database moves
Back ends moved from SQL Anywhere or Sybase ASE to SQL Server or PostgreSQL, with the SQL inside the DataWindows checked against the new database.
-
APIs and integrations
An API over the same database, so other systems and new web screens can use the data without going through the client.
-
Staged replacement
Modules rebuilt as a web application one at a time, with grid behaviour and speed tested early.
Staying, upgrading and rebuilding are different projects
Each trades cost against how much the business still depends on PowerBuilder afterwards.
-
Stay on your current version
Lowest cost in the short term. The application is documented and supported by us. If the version is a Sybase or SAP one, it remains on software its maker no longer maintains.
-
Upgrade within PowerBuilder
Most of the code is reused and staff keep the screens they know. The business continues to depend on PowerBuilder, on the licence terms Appeon sets, and on a small market for the skills.
-
Rebuild on a current stack
The rules are read out of the PowerScript and the DataWindows and written again as a web application. Nothing depends on PowerBuilder afterwards. It takes longest, and the risk is in behaviour hidden inside DataWindows.
What a PowerBuilder assessment looks at
PowerBuilder the product is healthy. The risk is in the version, the source and the DataWindows. The version facts are from Appeon and SAP notices.
-
Which version you are on
SAP PowerBuilder 12.6 was the last SAP release, and SAP ended mainstream maintenance on 30 June 2018. Appeon has released its own versions since, most recently PowerBuilder 2025 R2 in June 2026, and publishes an end of maintenance date for each. Versions 2022 and 2022 R2 reached theirs on 7 May 2026.
-
Whether the source is complete
Source lives in library files (.pbl). A compiled application is an .exe with .pbd or .dll files. A site that holds only the compiled files can run the application but cannot change or upgrade it.
-
The DataWindows
How many there are, which hold business rules in computed fields, validation rules and update settings, and which build their SQL while the program runs. Reading them is most of the analysis in any PowerBuilder project.
-
The database behind it
Sybase ASE, SQL Anywhere, Oracle or SQL Server, its version, and how the application connects to it. Old database drivers are a common obstacle on new machines.
-
External pieces
Calls to Windows, external libraries, automation of Word and Excel, and frameworks such as the PowerBuilder Foundation Class library. Each needs a decision in an upgrade.
-
How it is deployed
A client installed on every desk, a terminal server, or a web deployment. This decides what an upgrade has to deliver before users notice it.
-
Reports and printing
DataWindow reports, InfoMaker reports and anything exported to files. Users notice changes to reports first.
On an old PowerBuilder version and not sure whether to upgrade?
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 PowerBuilder version and build, and the Windows versions the application runs on.
-
The source
Whether you hold the library files for every part of the application, and whether they are in source control.
-
Size
A rough count of windows and DataWindows, and how many libraries there are.
-
The database
Product, version and size, and whether stored procedures hold business rules.
-
Users and deployment
How many people use it and how it reaches their computers.
-
Integrations
Files in and out, other systems that share the database, automation of Office.
-
Reports
The reports the business relies on, and how they are produced.
-
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 system
By video call and screen share, at meeting times agreed to suit you.
-
Technical assessment
We establish the version, what source you hold, how many DataWindows there are and what they contain, and what the application connects to. You get a written list of options with the risks of each and a staged estimate.
-
Proof of concept
One representative piece, usually a trial upgrade of a copy or a handful of screens rebuilt for the web, is taken end to end on your data.
-
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.
-
Regression and user testing
Screens, grids and reports are compared between the old and new, and your staff test the work they do every day.
-
Monitored cutover
The switch is planned with a way back. We watch the first days of live use for anything the tests did not show.
-
Support
Ongoing maintenance of the application and the database, for as long as it stays in service.
What people ask us about PowerBuilder
Is PowerBuilder still supported?
Yes, by Appeon, for the versions it maintains. SAP ended mainstream maintenance of its last release, PowerBuilder 12.6, on 30 June 2018. An application on a Sybase or SAP version is running on software nobody maintains, even though the product itself is alive.
Should we upgrade PowerBuilder or replace it?
It depends on what is hurting. If the problem is an unmaintained version, Windows compatibility or the database, an upgrade keeps the code and fixes those. If the problem is that nobody can be hired to change it, an upgrade does not solve that, and staged replacement might.
What makes DataWindows difficult to migrate?
They combine the query, the presentation and the update rules in one object, so behaviour a developer expects to find in code lives inside a control. Reading them properly is most of the analysis work.
Can we keep our database?
Usually, yes, at least at first. Upgrading or replacing the application first and moving the database later keeps each step checkable.
We only have the compiled application. Can it be upgraded?
Not properly. An upgrade needs the library source. Without it, the options are to keep the application running as it is, or to rebuild from its behaviour and its database. The assessment starts by establishing exactly what source you hold.
Our grids are heavily used. Will a web version be slower?
That is the right question for PowerBuilder, because DataWindow grids are fast and users notice at once. Grid behaviour and data volume are tested in the proof of concept, not at the end.
Do you provide PowerBuilder developers in Sydney, Melbourne, Brisbane, Perth and Adelaide?
Yes. We are an Australian team and we take on PowerBuilder 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 PowerBuilder system
The PowerBuilder version, the database behind it, 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.