HQ
United States
North America
Version Upgrade
PowerBuilder Version Upgrade Done Right.
A phased, intelligence-driven upgrade — not a runtime swap.
Any Version → PB 2025 · CodeScan AI Audit · Zero Production Disruption
Upgrade Path
PB 5.0, 8.0, 10.5, 12.5, 2017, 2019 → PB 2025 · AI-structural analysis with CodeScan
What You Gain
TLS, OAuth, cloud deployment, 64-bit performance · Foundation for UI/UX and cloud modernization
- PB 5.0+
- CodeScan AI
- PB 2025
- Phased Migration
- 30-Day Hypercare
Challenges
Why Upgrades Are Complex
PowerBuilder applications accumulate technical debt over decades. Understanding the root challenges is the first step to a successful upgrade.
Security & Compliance
Older versions lack TLS, OAuth, and modern compliance capabilities — creating regulatory exposure.
Modern Deployment
Cloud, containers, and Windows 11 require versions unavailable to legacy PB builds.
Performance Gains
Faster DataWindow rendering, reduced memory footprint, and improved startup times.
Vendor Support
Appeon only supports recent versions — EOL software receives no bug fixes or patches.
Talent Retention
Modern tooling improves developer productivity and recruitment of experienced PB talent.
Future Modernization
Version upgrade is the prerequisite for cloud migration, REST APIs, and UI/UX refresh.
Methodology
Our Upgrade Process
A disciplined, phase-gated approach that ensures stability at every intermediate version before advancing to the next.
1
Architectural Assessment
CodeScan audits version compatibility, DLL bitness conflicts, deprecated APIs, and produces Green/Amber/Red risk report.
2
Controlled Remediation
High-risk components addressed first; DLL and API compatibility validated per version stage.
3
Progressive Stabilization
Full stabilization required at each intermediate version before advancing.
4
Environment Setup
Target environment configured and baseline testing completed before code changes begin.
5
Regression & UAT
Full regression testing followed by structured UAT with business users at each milestone.
6
Cutover & Hypercare
Production cutover with tested rollback plan; 30-day hypercare with priority support included.
Reference
PowerBuilder Version Support Matrix
A complete view of every PB version — current support status, capability flags, and the recommended action for your estate.
| Version | Status | Cloud Deploy | 64-bit | REST / OAuth | Appeon Support | Action |
|---|---|---|---|---|---|---|
| PB 5.0–6.5 | End of Life | ✕ | ✕ | ✕ | ✕ | Upgrade now |
| PB 7.0–8.0 | End of Life | ✕ | ✕ | ✕ | ✕ | Upgrade now |
| PB 9.0–10.5 | End of Life | ✕ | ✕ | ✕ | ✕ | Upgrade now |
| PB 11.x–12.6 | End of Life | ✕ | ✕ | ✕ | ✕ | Upgrade now |
| PB 2017 | Legacy | ✕ | ✕ | Partial | ✕ | Plan upgrade |
| PB 2019 | Legacy | Partial | ✕ | ✓ | Limited | Plan upgrade |
| PB 2021 | Supported | ✓ | ✓ | ✓ | ✓ | Consider latest |
| PB 2022 | Supported | ✓ | ✓ | ✓ | ✓ | Stable choice |
| PB 2025 | Latest | ✓ | ✓ | ✓ | ✓ | Target version |
CodeScan AI
Know What You're Upgrading Before You Begin
Intelligence-driven pre-upgrade analysis that eliminates surprises and accelerates your planning timeline.
Before you plan the upgrade, you need to know exactly what you're upgrading.
PowerBuilder applications built over 10–20 years accumulate invisible complexity — DLLs with undocumented bitness conflicts, deprecated API calls, and tightly coupled modules. CodeScan is our mandatory pre-requisite for every version upgrade.
~70%
Reduction in discovery time
100%
Codebase coverage
Days
Not weeks for assessment
Free
As part of initial assessment
FAQ
Common Questions
Answers to the questions we hear most often from teams planning a PB version upgrade.
Which PB versions do you support upgrading from?
Any version (PB 5.0+) to PB 2025. CodeScan runs as a mandatory pre-requisite to audit compatibility and design the optimal upgrade path specific to your codebase.
How long does a PB version upgrade typically take?
Mid-size applications (100–300 objects) typically take 8–14 weeks. Smaller applications: 4–6 weeks. A free CodeScan assessment provides precise, codebase-specific estimates for your project.
Will our business logic be preserved?
Yes. Version upgrades move to newer runtimes while preserving all business logic intact. A full regression baseline is established before starting any upgrade work.
Do you handle third-party component upgrades?
Yes. CodeScan's External Dependencies module inventories all DLLs, validating bitness and compatibility with the target PB version before any upgrade work begins.
What does the free assessment include?
A CodeScan AI run on a representative portion of your codebase, a risk classification report, an effort estimate, and a 30-minute consultation with a senior PB architect.
Can the upgrade be done without disrupting production?
Yes. All upgrade work is performed in a parallel environment; production remains completely untouched. Cutover only occurs after full regression and UAT completion, with a tested rollback plan ready.
Case Studies
Version Upgrades, Real Outcomes
Two recent PowerBuilder version upgrade engagements — phased migrations delivered without production disruption.
No case studies found.
