The tool still ships. The people who wield it are retiring — and every year the maintenance quote goes up while the candidate pool goes down. Marcus — Kinetech's AI Mendix developer — reads your PBL exports directly, DataWindow by DataWindow, and rebuilds each app in Mendix from a specification you approve, with evidence at every gate.
01 · The clock
Let's be accurate about the problem: Appeon actively develops PowerBuilder — PB 2025 is shipping, with a regular release cadence. Your platform isn't abandoned. What's disappearing is the labor market around it: a developer pool that skews toward retirement, with few juniors entering — a concern voiced openly on Appeon's own community forum and corroborated by anyone who has tried to hire for it lately.
That's a different kind of deadline than an end-of-support date — it doesn't arrive on a schedule, it arrives when your one remaining PowerBuilder developer gives notice. The organizations that handle it well are the ones that start the exit while that person is still in the building to answer questions.
02 · The unlock
PowerBuilder has the best-kept secret in legacy migration: the entire application exports to plain text. Using ORCA — Appeon's own documented library API — every object in every PBL batch-exports to readable source. No workshops to rediscover what the app does; the app says what it does.
| Your artifact | What Marcus extracts | Where it lands in Mendix |
|---|---|---|
| PBL libraries via ORCA/PBORCA batch export |
Every window (.srw), DataWindow (.srd), user object (.sru), and menu (.srm) as plain text | The complete screen inventory, navigation, and module structure |
| DataWindow .srd the crown jewel |
The full SQL select, every column, validation expressions, display formats, computed fields, layout | Entity + Data Grid 2 page + datasource microflow + validation microflows — a DataWindow is effectively a machine-readable spec |
| PowerScript events & functions | Readable procedural business logic, window by window | Microflows and nanoflows |
| Database schema & stored procedures | Tables, constraints, procedure logic | The domain model; existing procedures stay callable during transition |
One honest flag: apps built on PFC-style frameworks carry layers of inherited behavior that raise rebuild complexity. The assessment identifies framework usage per app and prices it in — before you commit, not after.
03 · How a migration runs
Four gates are held by you throughout — the same governed discipline Kinetech applies to its regulated-industry delivery:
Each app's extracted specification — screens, SQL, validations, roles — restated in plain English and approved before the model is touched.
Who can see and do what, restated as Mendix roles and entity access for your sign-off — not silently inferred from old code.
Styled design directions derived from your brand before pages are generated. You pick; Marcus builds to it.
A rebuilt app reaches you only after all quality gates pass — and cuts over only when you accept it, evidence in hand.
04 · The date
Here is the commitment we will put in writing. The assessment does not end with a range — it ends with a date, sized from your actual extracted complexity. Miss that date and the assessment fee comes back. We can promise a date because we never quote a calendar before reading your source.
The assessment names the date. Miss it, and the assessment fee comes back.
That is a real term, not a slide. It is affordable to us for one reason: the clock below starts only when a complete artifact pack is in our hands, and it pauses only for your own approval gates.
| One PowerBuilder target and its libraries | Complete artifact pack → UAT-ready |
|---|---|
| Compact — ≤40 windows, ≤60 DataWindows, single target | 2–3 weeks |
| Departmental — 40–100 windows, 60–200 DataWindows, 2–4 integrations | 4–6 weeks · ~30 days typical |
| Load-bearing — 100+ windows, multiple targets, PFC or in-house framework, distributed PB | 8–12 weeks |
| Each further target in the same estate | 30–40% faster |
Sizing model, not a price list — the assessment reads your actual source and returns one date. Bands assume a single rebuild boundary agreed at the scope gate.
The date is only honest if the inputs are complete, so here is the whole list up front. Nothing on it is unusual, and most of it exists already.
Three approval gates are yours: scope, permission ratification, design sign-off. We answer each within three business days. Time beyond that on your side moves the date by exactly that much — and nothing else does.
Production cutover on your change calendar. SSO and network provisioning by your IT. Third-party licenses or vendor contracts we don't control. Remediation of source-data quality problems the assessment flagged. Anything added after the scope gate.
Functional parity against the approved specification, running on your migrated data in a parallel environment, with production security enforced and tested per role, all nine quality gates green, and documentation published. Your users click through it.
DataWindows are the reason this is fast: a .srd carries the query, the layout, the formatting and the validation rules in one readable structure — the best extraction surface of any platform in this campaign. What moves the date is business logic buried in stored procedures, which has to be decided rather than translated (keep it in the database, or lift it into the model), and framework inheritance chains that need untangling before anything can be scored.
05 · The platform question
Appeon's PowerServer will put your existing PowerBuilder app in a browser quickly, and if what you need is a short-term deployment fix, it does that. We'd rather say so plainly than pretend it doesn't exist.
What PowerServer doesn't change is the thing that's actually shrinking: the codebase is still PowerScript, maintained by the same scarce people, now with a deeper dependency on a single vendor. It's more runway on the same island. The case for rebuilding on Mendix:
06 · Straight talk
07 · Quality & security
Watch real build evidence land on the live Build Console, and see the delivery lifecycle at our interactive explainer.
08 · Engagement & pricing
Send us ORCA exports of your PBLs. We return a scored inventory — retire, rebuild, defer — with framework complexity flagged per app, a per-app fixed-bid quote, and one representative app rebuilt in Mendix as proof.
Each app rebuilt from its approved specification at the price quoted in the assessment. Tested per role, documented, evidence published, accepted by you before cutover.
For estates measured in dozens of apps: Priced on what the work is, how many lanes run in parallel, and how fast you need it — always (a Kinetech engineer reviews every release, with an SLA). The instance works your migration backlog continuously.
Prefer to pay for AI usage directly? Bring your own Claude access — a direct Anthropic API key or Claude through your AWS Bedrock / Google Cloud commitment — and take roughly 15–25% of the monthly off either instance plan, with per-build costs visible on your Console.
Pilot-program pricing, subject to a signed order form; heavy build months on bundled plans may incur metered usage beyond the stated allowance.
09 · The questions you should ask
Your experience is the industry's experience — transpilers produce code shaped like PowerBuilder wearing a different syntax, and it's unmaintainable from day one. That's why Marcus doesn't transpile. The exports become a plain-English specification per app; you approve it; then Marcus builds a native Mendix model through the same blocking quality gates as any Kinetech delivery — naming standards, 100% documentation, per-role tests, a graded scorecard. Judge it on the sample app the assessment includes: open it in Studio Pro and read it.
If a browser deployment of the existing app solves your problem, PowerServer is the faster path and we'll say so. It just doesn't touch the actual risk: the code is still PowerScript, maintained by the same shrinking pool, with a deeper single-vendor dependency than before. Web-enabling is runway; a rebuild is an exit. Some clients sensibly do both — PowerServer for breathing room, Mendix migration app by app behind it.
At first, yes — and anyone who tells you otherwise hasn't migrated a heads-down data-entry team. Expect weeks, not days, to match old speeds. We mitigate deliberately: keyboard shortcuts, inline grid editing, and focused task screens designed in a UX-parity workshop with your power users before design sign-off. The upside of the trade: the app becomes reachable from a browser, a tablet, or the field — for everyone who isn't a power user too.
Printed output is rebuilt as server-generated PDF documents inside the application — and we validate fidelity against your real printouts during the assessment, side by side, before you've committed to anything. Bring your ugliest form; that's the honest test.
No, but it raises the cost, and we'll say so per app. Framework inheritance chains mean behavior lives in layers, not just in the window's own code — the analysis takes longer and the spec review matters more. The assessment flags framework usage explicitly and prices it into each fixed bid, so the complexity surfaces before you commit rather than mid-project.
The difference is direction. The PowerBuilder pool shrinks every year; the Mendix pool is growing, backed by Siemens, with training your own team can realistically complete. And the day-to-day build load doesn't ride on hiring at all — a Marcus instance carries it, with your team holding the approval gates. You end up owning standard, documented Mendix models that any Mendix shop could pick up — the opposite of where your PBLs are today.
Yes. Standard Mendix models in your Team Server repository, validated with Mendix's own checker, fully documented in-model, openable and extendable in Studio Pro. If you stop working with us, you keep everything — portability is the proof the work is real.
10 · Next step
Pick one simple app, one typical one, and the one nobody wants to touch. The assessment returns a scored inventory, per-app quotes, and one of the three rebuilt in Mendix — with the evidence — so you judge this on proof, not slides.
Marc Lehane · Solutions Architect / CTO, Kinetech · [email protected]
Kinetech Cloud · San Antonio, TX · How we deliver · Live Build Console
You are reading Your platform — deeper detail on step 4, Why now?.
That is the pressure. What it costs to answer it is not one number — three things move it.