PowerBuilder Modernization Service
PowerScript assets to .NET, with AI and our own support library.
Choose Windows Forms or Blazor as the target.
It’s your version that ends, not the product
Appeon continues to develop PowerBuilder, but support ends per version — PB 2019 and earlier are already out of support.
Conversion, testing and security fixes automated
AI improves the conversion tool and RPA runs tests repeatedly. Our ODO support library absorbs DataWindow and OCX compatibility.
No big-bang cutover
Convert, test and release by business domain. A Phase 0 PoC fixes the approach and narrows the estimate to within ±10%.
PowerBuilder support ends per version
| Version | End of mainstream | End of support | Status |
|---|---|---|---|
| PB 2017 / 2017 R2 | 30 Jun 2022 | 30 Jun 2023 | Ended |
| PB 2017 R3 | — | 31 Jul 2025 | Ended |
| PB 2019 / 2019 R2 | 6 Aug 2022 | 6 Aug 2023 | Ended |
| PB 2021 | 4 Sep 2023 | 4 Sep 2024 | Ended |
| PB 2019 R3 (LTS) | 22 Jan 2026 | 22 Jan 2028 | Mainstream ended |
| PB 2022 / 2022 R2 | 7 May 2026 | 7 May 2027 | Mainstream ended |
| PB 2022 R3 (LTS) | 8 Jan 2029 or later | — | Supported |
Source: Appeon End of Life Policy and per-version notices (as of September 2026). Older versions such as PowerBuilder 5 / 6 / 7 are all out of support.
Common misconceptions
“PowerBuilder is a dead product.”
Appeon continues development: PB 2025 shipped in May 2025 and PB 2025 R2 in June 2026.
“We have a support contract, so we’re safe.”
Deadlines apply per version. Using PowerBuilder and being in support are two different things.
“Migrating means a full rebuild.”
Our conversion tool carries the current specification to .NET — without updated design documents — faster and cheaper than rebuilding.
Four reasons to migrate
Support deadlines
Once mainstream support ends, bug fixes and security updates stop.
Runtime constraints
Old OCX / DLLs and legacy DB clients are not guaranteed to run on the latest Windows.
Integration with systems and AI
.NET offers far more options for REST APIs, cloud and AI services — and faster implementation.
Future maintenance
Once on .NET / C#, changes are ordinary .NET work, and you can hire from the .NET talent pool.
Windows Forms or Blazor
Windows Forms (desktop)
When you want to keep today’s usability
- Maps naturally to PowerBuilder screens
- Straightforward printing and local devices
- Minimal change for users
- Windows clients still need deployment
- Browser or external use needs separate work
Blazor Server (web)
When you want the same source in the browser (see the architecture below)
- Runs in the browser from the same source as WinForms
- Forms run on the server; only their appearance goes to the browser
- Nothing to deploy to PCs; works remotely and across sites
- Responsiveness and traffic depend on the network
- Requires a Windows server, since rendering uses GDI+
Both run on .NET LTS (the current LTS is .NET 10, released November 2025 with three years of support). Because the web version uses the same source as the WinForms version, you can migrate to Windows Forms first and add the web version later.
Desktop migration vs. web
| Item | Desktop (Windows Forms) | Web (Blazor Server) |
|---|---|---|
| Environment | Installed on Windows PCs | Used in a browser (Edge, Chrome, etc.); the server must be Windows |
| Deployment | Deployed to each PC (auto-update possible with ClickOnce) | Placed on the server only; nothing to deploy to PCs |
| Screens and feel | Close to the PowerBuilder screen structure; little change in feel | The same screens as WinForms, drawn on the server; input fields are the browser’s own |
| Printing | Directly to printers | Basically PDF output printed from the browser |
| Files and devices | Local files and devices used directly | Browser restrictions; handling needs review |
| Where it is used | Mainly the internal network | Easy to use remotely and across sites; responsiveness depends on the network |
| Effort and risk | Low (no extra server; current operations continue) | No screen rebuild (same source as WinForms); session management must be added |
| Best for | Core systems with many screens, data entry | Systems used externally or across sites, inquiry-centric work |
Phased migration: because the web version uses the same source as WinForms, you can migrate to Windows Forms first and extend browser use to the business areas that need it.
Web (Blazor Server) architecture
Converted forms run only inside the server, and the browser receives their appearance. The converted code is not rewritten — it runs from the same source as the WinForms version.
A WinForms-compatible model runs on the server
Events fire in the same order as WinForms on our library’s compatible model. MessageBox and similar calls stay synchronous.
Appearance is sent as images and HTML
Controls are rendered to PNG with GDI+ and only changes are sent. Input fields are real browser inputs, so Japanese input works as is.
User actions return as window messages
Clicks and keystrokes flow on the server as window messages, so the app reacts just like the WinForms version. Fast typing never drops characters.
One process per user
The converted app holds global variables and SQLCA statically, so a worker process is started for each browser — one user per process.
Benefit：Run in the browser from the same source as the WinForms version, without rewriting the converted code.
Caution：Most of the screen is images drawn on the server, so traffic and responsiveness depend on the network. Rendering uses GDI+, so a Windows server is required.
Conversion — AI builds the converter
The conversion tool converts PB source; AI develops and improves that tool. Even if the current source changes during the project, you can re-convert at the same quality any number of times.
More on AI-driven modernization →What our support library takes on
DataWindow compatibility
Retrieval, update and dynamic changes via Describe / Modify are reproduced in .NET — the biggest migration issue is contained in the library.
OCX and external DLLs
Old components, including 16-bit ones, are replaced, wrapped or moved out-of-process — whichever fits best.
Business frameworks
Equivalents of PB base classes and common functions. Components from past projects can be reused to lower cost.
String and date handling
SJIS byte-based string functions, Japanese era dates and other behaviour specific to Japanese business systems.
The converted code is left untouched. Differences live in the library, so re-conversion causes no rework.
UI, reports and database
Screen UI
Built from standard .NET controls such as DataGridView, TextBox and ComboBox — no commercial component licences.
Reports
DataWindow reports (Freeform / Group / N-Up …) are reproduced with our own report editor — no commercial report product needed (editor offered by subscription).
Database
First standardize on a supported version. SJIS → UTF-8, database consolidation and PostgreSQL are evaluated in Phase 0.
Phased migration by business domain
Preparation and PoC
Trial conversion of representative screens; DataWindow approach, legacy components and DB risks identified; estimate narrowed to ±10%.
Foundation
Database migration, DataWindow compatibility and report engine.
Domain-by-domain migration
Convert → unit test → scenario test per business domain, avoiding a big-bang cutover.
Batch and standalone modules
Batch jobs become .NET services, in parallel with the domain phases.
Service levels
Up to compile-error removal
If you will own testing. Asset analysis, conversion rules, and source that compiles on the specified .NET version.
Up to runtime-error removal
If you want it running. RPA tests confirm screens match your current screenshots, and we fix until normal operation raises no runtime errors.
Optional services
How we estimate
Share your PowerBuilder assets
We statically analyze PBLs and source to count PBLs, screens, DataWindows and components, then present an approach and rough estimate (±25%). NDA first.
If source cannot leave your company
Send us the PBL list, number of screens and the report products / external components used. We will outline the approach and a rough figure.
After a Phase 0 PoC (trial conversion of representative screens), we resubmit a firm estimate within ±10%.
Tell us your PowerBuilder version and number of screens to start
Tell us the platform version and the number of screens, and we will send an initial answer. We are happy to sign an NDA first.
TEL +81-3-5962-3776