Is PowerBuilder Really Legacy Technology in 2026? | by Kumaran Systems | May, 2026 | MediumSitemapOpen in appSign up<br>Sign in

Medium Logo

Get app<br>Write

Search

Sign up<br>Sign in

Is PowerBuilder Really Legacy Technology in 2026?

Kumaran Systems

4 min read·<br>2 days ago

Listen

Share

Press enter or click to view image in full size

Yes. By every objective measure, PowerBuilder is legacy technology in 2026. It does not appear in the TIOBE top 20, universities stopped teaching it years ago, and its market share sits at 0.03% of the software development tools category. But “legacy” and “dead” are not the same thing.<br>Thousands of enterprises are still running it in production, Appeon shipped PowerBuilder 2025 in May 2025, and a 2025 R2 beta is currently in testing. So the more useful question is not whether PowerBuilder is a legacy? But what does that mean for the organizations still running it?<br>SAP Left in 2016. Appeon Owns It Now.<br>This is worth clarifying because the market is genuinely confused. SAP exited PowerBuilder in July 2016, transferring all development and support responsibilities to Appeon.<br>SAP’s final version, PowerBuilder 12.6, reached end of life on January 31, 2018. Everything since then, from PB 2017 through the current PowerBuilder 2022 R3 LTS, is an Appeon product.<br>Appeon has been releasing updates on roughly a 10–12 month cycle. PB 2025 introduced a revamped IDE, a significantly faster compiler, automatic REST API generation from DataWindows, and plain-text source files for proper Git integration. PB 2025 R2 adds .NET 10, PostgreSQL 17, and Windows Server 2025 support.<br>There is no announced end-of-life for the product line. Appeon’s EOL policy (updated March 2026) gives LTS releases at least 60 months of standard support. PB 2022 R3 is the current LTS. If you are planning a migration timeline, you have runway, but not unlimited runway.<br>Who Still Uses PowerBuilder, and Why<br>Enlyft tracks around 9,877 companies using Sybase PowerBuilder.<br>Oregon’s Department of Human Services still runs PowerBuilder as the foundation for its ACCESS, TRACS, and TWIST applications, as confirmed in a 2023 sole-source notice: “The service is the foundation for the Oregon ACCESS, TRACS, and TWIST applications and could not be replaced without a rewrite of the applications.”<br>The US Defense Finance and Accounting Service renewed its PowerBuilder licenses in 2023. New York State’s Workers’ Compensation Board is mid-migration off EAServer/PowerBuilder right now.<br>The reason these organizations have not migrated is not nostalgia. It is the DataWindow. PowerBuilder’s DataWindow object bundles SQL, UI rendering, validation rules, computed fields, and update logic into a single construct.<br>There is no direct equivalent in any modern framework. A complex DataWindow can take an experienced developer two to three days to convert manually. An enterprise PowerBuilder portfolio often contains hundreds or thousands of them.<br>The second problem is documentation. In most cases, the DataWindows are the documentation. The developers who built them have retired or moved on, and the business rules encoded in 20-year-old PowerScript exist nowhere else.<br>The Real Risk: The Talent Cliff<br>Features in PB 2025 are not the problem. The developer pool is. Universities stopped teaching PowerBuilder years ago. The cohort with deep expertise is approaching or past retirement age.<br>A 2025 survey of 504 US IT professionals by Saritasa found that 50% of organizations cite “the current system still works” as the primary reason they have not modernized. That is fine until a key maintainer leaves and there is no one to replace them.<br>McKinsey has noted that as much as 70% of the software used by Fortune 500 companies was developed more than 20 years ago. PowerBuilder is one instance of a much broader pattern.<br>The US Government Accountability Office reported in 2025 that 11 critical federal legacy systems now cost approximately $754 million a year collectively just to operate and maintain. The cost of deferring modernization compounds.<br>Modernization Options That Actually Work<br>There is no single right answer, but there are four approaches worth considering:<br>Upgrade to PB 2022 R3 or PB 2025. If you are still on PB 12.6 or PB 2017, you are outside standard support. Moving to the current LTS is the cheapest and fastest risk reduction available. It buys time and does not require re-engineering anything.<br>Cloud deployment via PowerServer. Appeon’s PowerServer converts existing client/server apps into cloud-deployable web applications without a full rewrite. It is not a modern architecture, but it extends viability while you plan a fuller migration.<br>Incremental rewrite using a strangler-fig approach. Wrap the PowerBuilder app in REST APIs using PB 2025’s automatic API generation, then build new functionality in a modern stack against the same data layer. Replace screens one at a time. This reduces risk significantly compared to a big-bang rewrite.<br>Automated code...