PowerBuilder Modernization Without a Risky Rewrite
Phased, reversible upgrades for long-running PowerBuilder applications. We modernize the parts that pay back — and leave alone the parts that don't. Production stays running throughout.
Concrete deliverables in a Modernization engagement
Modernization is a sequence of small, reversible decisions — not a single big bang. Each artefact below is a real work product you receive, with rollback options for every step.
Codebase, architecture and risk assessment
Dependency map, third-party DLL inventory, runtime-version exposure, business-critical workflows. The written input that informs every later decision.
PowerBuilder version upgrade plan
Concrete steps from your current PB version (often 9, 10.5, 11.5 or 12.6) to a chosen Appeon target (2017, 2019, 2022 or 2025). With rollback gates between each stage.
Appeon migration path (Sybase → Appeon)
Compatibility audit, deprecated-feature replacement plan, runtime distribution change, licensing reconciliation. Specific to your codebase, not a generic checklist.
PowerBuilder Sybase to Appeon migration: 9 surprises and the workaround for eachPowerServer / PowerClient readiness report
Honest assessment of whether the application is a good candidate for PowerServer (installable cloud apps) or PowerClient — and what would need to change first.
UI modernization without redesign
Visual refresh that respects user habits: cleaner DataWindow presentation, modern fonts, improved accessibility — without retraining users on a new flow.
Build, deployment and installer refresh
Modernized build chain, signed installers, certificate management, runtime distribution strategy that matches your IT environment in 2026, not 2008.
Database compatibility plan
Oracle 19c / 23ai, SQL Server 2022, PostgreSQL 16 — the database side of any PB upgrade. We map character-set, ANSI/ODBC and SQL-dialect risk before the upgrade starts.
Executive-ready summary
A 4–8 page document the CTO can hand to the board: what is happening, what it costs, what the risks are, what 'done' looks like.
Typical situations behind a Modernization call
Modernization rarely starts because someone wakes up wanting it. It starts when something external forces the conversation. These are the four most common triggers.
Someone is pushing 'rewrite in .NET / Java / web'. The number scares you. You need a sober, costed alternative on the table before the decision is made.
On PB 11.5 or 12.6, no upgrade path agreed, getting nervous about runtime support, security and the talent market. We map the route to a current Appeon release.
Database or platform EOL is on the calendar. PB compatibility risk is now the project bottleneck. Modernization aligns the application with the new platform.
Build is fragile, installer broken, runtime drift across machines. The application still runs but you can't ship a fix without praying. Modernization rebuilds that foundation.
Four phases: Assess → Decide → Modernize → Evolve
Each phase produces a written artefact you can act on independently. You can stop after Assess or Decide — most engagements continue, but the option is real.
2–4 weeks · fixed fee
Assess
2–4 week scan: codebase, architecture, database, dependencies, business-critical workflows. Output: written risk and readiness report.
1 week · written
Decide
Three modernization options ranked by cost, risk and timeline. We strongly recommend one — but the choice is yours, and we document the trade-offs.
phased · scoped
Modernize
Phased upgrade. Every milestone is reversible: if a stage fails, we roll back without losing the others. No 'big bang go-live'.
long-term · optional
Evolve
Post-modernization: documentation handover, optional retainer to keep the gains. The system runs better and stays that way.
Fixed-fee assessment, then phased implementation
Modernization almost always starts with a fixed-fee assessment — the cheapest way to find out whether the bigger investment makes sense. Implementation comes after, scoped to the chosen path.
| Engagement | Best for | Timeline | You get | Price |
|---|---|---|---|---|
| Modernization assessment | Finding out whether the bigger investment makes sense | 3–6 weeks | Risk and dependency report, three implementation options, executive summary | Fixed fee |
| Phased modernization program | Implementing the chosen path while production stays live | 6–18 months | Reversible milestones, regression suite, joint delivery with your team | Monthly, scoped to phase |
| Targeted modernization | One slice: PowerServer pilot, installer refresh, Appeon-only migration | 4–12 weeks | A single workstream and hand-off documentation | Fixed fee, scope-dependent |
What teams ask before they call
Not on the list? Ask us directly — we usually reply within one business day.
Should we modernize or rewrite?
Rewrites of mature PowerBuilder applications fail more often than they succeed — typically because the business logic encoded in the DataWindows and event chains is far more valuable than anyone realizes. Modernization is almost always cheaper, lower-risk and preserves what works. We will tell you honestly if your case is the exception.
How long does PB 12.6 → 2025 actually take?
For a typical 200–500 DataWindow enterprise application: assessment 3–4 weeks, phased implementation 4–9 months. The variance comes from third-party DLLs, custom controls and database-side coupling — which is exactly what the assessment phase quantifies before you commit.
Can we modernize while the system is in production?
Yes — and we strongly prefer it. Each phase ships a reversible change that can be deployed or rolled back independently. There is no 'modernized branch' running for months in parallel with production. That model breaks more often than it works.
Do we have to move to PowerServer?
No. PowerServer is a good fit for some applications and a bad fit for others. Our readiness report tells you honestly which category yours is in — and what would need to change first. Plenty of modernized applications stay as thick clients and that's fine.
What does this typically cost?
Assessment: fixed-fee, similar to a typical management-consulting engagement. Implementation: scoped per phase, billed monthly, sized to your codebase. We deliberately avoid quoting a number publicly because PowerBuilder application sizes vary by two orders of magnitude — but we will quote a fixed price after the assessment.
Considering modernization?
Send a short description of your PowerBuilder system — current version, database, deployment, top concern. We'll reply within one business day with a practical next step. Most engagements start with a fixed-fee assessment.