version pgrade

CodeScan-First Approach

PowerBuilder
Version Upgrade Done Right.

A PowerBuilder version upgrade is not merely a runtime swap — it is a structural transformation of an application that has evolved over decades. Our approach is phased, intelligence-driven, and architecturally disciplined.

Get a Free Assessment → See Our Process
Typical Upgrade Path
Source
Any Version
→
Target
PB 2025
Supports PB 8.0, 10.5, 12.5, 2017, 2019 and above
Phased path for complex older codebases (PB 5.0–8.0)
AI-structural analysis with CodeScan
Zero disruption to production systems
Why It Matters

What Makes Legacy PB Upgrades Complex?

Regardless of your starting version — PB 8.0, 10.5, 12.5 or older — most long-running PowerBuilder applications carry deep object inheritance hierarchies, tightly coupled modules, and complex DataWindow interdependencies. Upgrading without structural clarity introduces avoidable risk.

01
Security & Compliance

Older PB versions receive no security patches, creating regulatory exposure. Modern versions ship with TLS, OAuth, and compliance-ready capabilities built in.

02
Modern Deployment Targets

Unlock cloud deployment, containerised environments, and Windows 11 compatibility that simply don't exist in legacy PB builds.

03
Performance Gains

Newer PB runtimes deliver faster DataWindow rendering, reduced memory footprint, and significantly improved application startup times.

04
Vendor Support Continuity

Appeon only supports recent versions. Staying on EOL PB means no bug fixes, no patches, and no assisted migration from your vendor.

05
Talent Retention

Developers gravitate to modern tooling. Upgrading keeps your team productive and makes recruiting experienced PB talent significantly easier.

06
Foundation for Further Modernization

A version upgrade is the prerequisite for every next step — cloud migration, REST APIs, UI/UX refresh, and microservice integration all depend on it.

How We Work

Our Upgrade Process

We prefer a controlled, phased migration for every upgrade engagement. Direct multi-version jumps compound breaking changes from all intermediate releases at once — making failures hard to isolate and timelines unpredictable. A phased path treats each intermediate version as a validation gate: compile errors resolved, DLL and API compatibility confirmed, and a regression baseline preserved before advancing. Risk is contained, root causes are identifiable, and outcomes remain predictable — regardless of your starting version.

1
Architectural Assessment
CodeScan audits the entire application — version compatibility, DLL bitness conflicts, deprecated APIs, code complexity, and architecture maturity — producing a Green/Amber/Red risk report that drives the upgrade plan.
⚡ CodeScan AI
2
Controlled Module-Level Remediation
High-risk components are addressed first. DLL and API compatibility is validated per version stage, keeping refactoring focused and preventing cascading failures.
3
Progressive Stabilization Across Versions
At each version stage, compile errors are resolved, deprecated behaviors adjusted, and integrations retested. No stage advances without full stabilization sign-off.
Per-stage sign-off
4
Environment Setup & Baseline Testing
Target PB environment is configured and a full regression baseline is established before any code changes begin — eliminating surprises during validation.
Zero-surprise baseline
5
Regression & UAT Testing
Full regression testing against the baseline, followed by structured UAT with business users to confirm functional parity before cutover.
Functional parity guaranteed
6
Cutover & Hypercare
Production cutover with a tested rollback plan, followed by 30-day hypercare with priority support to ensure full post-upgrade stability.
30-day hypercare included
Version Reference

PowerBuilder Version Support Matrix

We cover the full spectrum — from PB 8.0 and above to PB 2025. Find where you stand and map the path forward.

Version Status Cloud Deploy 64-bit Runtime REST / OAuth Appeon Supported Recommended 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 (16) Legacy ✕ ✕ Partial ✕ Plan upgrade
PB 2019 (17) Legacy Partial ✕ ✓ Limited Plan upgrade
PB 2021 (19) Supported ✓ ✓ ✓ ✓ Consider latest
PB 2022 (22) Supported ✓ ✓ ✓ ✓ Stable choice
PB 2025 Latest ✓ ✓ ✓ ✓ ✅ Target version
Pre-Requisite Assessment

CodeScan — Know What You're Upgrading Before You Begin

CodeScan AI
An enterprise-grade health and upgrade-readiness audit — scanning the entire PB application to surface version blockers, risk areas, and remediation priorities before any migration work begins.
  • Detects PB version usage across every object and flags features, APIs, and controls that are deprecated or unsupported in the target version
  • Validates external DLL bitness (32-bit vs 64-bit conflicts), deprecated API integrations, and third-party driver compatibility against the upgrade target
  • Identifies dead code, duplicate scripts, embedded SQL, and tightly coupled modules that add complexity and risk to the upgrade
  • Assesses architecture maturity — 3-tier readiness, business logic entanglement, and modularization gaps that affect upgrade stability
  • Delivers a Green / Amber / Red risk classification per module — enabling data-driven remediation sequencing before the upgrade begins
Why it matters

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, version-specific behaviors, and tightly coupled modules. Without a structured audit, these become surprises mid-upgrade.

CodeScan is our mandatory pre-requisite for every version upgrade engagement. It gives our architects the structural clarity to design the most efficient phased migration path, prioritise high-risk components, and produce a realistic effort estimate — all before a single line of code is touched.

~70%
Reduction in discovery time
100%
Codebase coverage
Days
Not weeks for assessment
Free
As part of initial assessment
Risk Awareness

Staying vs. Upgrading

The cost of inaction grows every quarter you remain on an unsupported version.

⚠ Risks of Staying on Older PB Versions
🔴Unpatched security vulnerabilities with no vendor fix path
🔴Incompatibility with modern Windows OS and current hardware
🔴No Appeon vendor support for incidents or bugs
🔴Unable to deploy to cloud or containerised environments
🔴Compliance failures across regulated industries
🔴Developer talent pool drying up for EOL versions
✅ After Upgrading with Optisol
🟢Full Appeon vendor support and regular security patches
🟢Cloud-ready runtime and modern OS compatibility
🟢64-bit performance and improved DataWindow rendering
🟢REST, OAuth, and modern API integration capabilities
🟢Platform ready for UI/UX and architecture modernization
🟢Faster delivery via CodeScan AI-accelerated assessment
FAQ
Common Questions

Can't find what you're looking for? Reach out directly and one of our senior PB architects will respond within a business day.

We support upgrades from any PB version — including PB 5.0 and above — to PB 2025. We recommend a phased migration path for most engagements, because direct multi-version jumps compound breaking changes across intermediate releases, making failures difficult to isolate. CodeScan runs first as a mandatory pre-requisite — auditing version compatibility, DLL bitness conflicts, deprecated APIs, and code risk — so we design the most efficient phased path for your specific application before any work begins.
It depends on codebase size and complexity. A mid-size application (100–300 objects) typically takes 8–14 weeks. Very large or highly customised estates can take longer, while smaller applications can be done in 4–6 weeks. Our free CodeScan AI assessment produces a precise estimate specific to your codebase before any commitment is made.
Absolutely. A version upgrade moves your application to a newer runtime while keeping all existing business logic entirely intact. We establish a full regression baseline before starting and validate functional parity at every milestone. Business logic is never rewritten unless you specifically request enhancements alongside the upgrade.
Yes. CodeScan's External Dependencies module inventories all third-party DLLs, validating bitness (32/64-bit), digital signatures, and compatibility with the target PB version. We then either source replacement libraries, upgrade vendor components, or redevelop lightweight wrappers — all resolved before remediation begins.
Our free assessment includes a CodeScan AI run on a representative sample of your codebase, an upgrade risk classification, a high-level effort estimate, and a 30-minute consultation with a senior PB architect to walk through findings and answer your questions. No commitment required.
Yes. All upgrade work happens in a parallel environment — your production system remains untouched throughout the engagement. We only plan a cutover once full regression and UAT are complete, and we always have a tested rollback plan ready before going live.
Ready to Upgrade Your PowerBuilder Application?
Get a free, no-obligation assessment from our senior PB architects. We'll review your environment and respond within 2 business days.
solutions@optisolbusiness.com 📞 +1 412 406 9010
Or fill out the form — we respond within 1 business day.
Your Name(Required)