IBM MQ → RabbitMQ
Phased migration with legacy code refactoring
Legacy messaging replaced in phases while the applications calling it were refactored. No big-bang cutover; each phase reviewed before the next.
PowerBuilder logic lives in DataWindows and event scripts. We map them first, then move the application in phases.
w_invoice.srwremovedd_invoice.srdremovedInvoiceService.cs+84−0InvoiceGrid.tsx+63−0Stacks we work in
A PowerBuilder migration moves PowerBuilder applications to .NET or Java by mapping DataWindows, event scripts and database access, then migrating in phases. Ace8 does the assessment and plan, and a vetted specialist partner delivers. Ace8 claims no past PowerBuilder projects. PowerBuilder is still sold and updated by Appeon, so staying is also an option.
Facts
Yes. PowerBuilder is sold by Appeon, whose current release is PowerBuilder 2025 R2, made generally available on 3 June 2026 and adding .NET 10 support. Appeon says it releases updates every 10 to 12 months, so a migration is a business decision, not a forced one. Check Appeon's product page for current terms.
Fits when: The app works, the team knows it, the issue is age of the version
Move to a current release, possibly with Appeon's own deployment options
Watch out for: Skills pool and vendor dependency remain
Fits when: The organization is standardizing on Microsoft
DataWindows and scripts rebuilt in C# with a web or desktop UI
Watch out for: Large UI rebuild; reporting logic in DataWindows
Fits when: Java is your standard or integrations are wide
Logic rebuilt as Java services with a web UI
Watch out for: Same rebuild effort, different skills
Mapping
A DataWindow combines a data source, a presentation and update logic, so each one is split into a query, a UI component and a save routine in the new application. Appeon describes the DataWindow as the basis of PowerBuilder's productivity, which is why it is the biggest part of the inventory.
SQL and stored procedures become repository or service calls.
Grids, forms and reports become UI components or a reporting tool.
Validation, computed fields and update properties move into services.
ItemChanged, Clicked and similar events become explicit handlers.
Plan
Each phase moves a group of windows and the DataWindows behind them, while the rest stays in PowerBuilder. Users and data stay shared until the last group moves, in line with the Ace8 method.
List libraries, windows, DataWindows, user objects, database connections and external calls.
Record real inputs and outputs for calculations, reports and updates.
Rebuild one module at a time with engineer review. AI-assisted tools can draft code and tests; they do not replace comparison on real data.
Compare old and new on the same data before each cutover.
Remove the runtime when the last module is live.
How it runs
Ace8 scopes and delivers the move. AceMQ engineers support the new stack 24/7 from day one.
Scope, cost and AI readiness, before any migration starts. Characterization tests and a baseline before we touch a line.
AI-assisted, engineer-verified, one capability at a time. Tools draft the rewrite and a senior engineer signs every change.
Tested, reversible cutover. AceMQ engineers support the new stack from day one. Supported after migration →
Delivery
Ace8 assessment plus a vetted specialist partner.
Ace8 owns the plan, test approach, review gates and any Java build, and the partner brings PowerBuilder and .NET depth. The proposal names who does what before you sign.
AceMQ supports the result 24/7 after go-live; see supported after migration. The same partner model applies to mainframe modernization and .NET modernization.
Evidence
Ace8 has no published PowerBuilder project or sample run.
Results will read Pending until there is one, and this page claims no durations or savings.
Next step
Book a fixed-price assessment.
It returns the window and DataWindow inventory, a target per module and a fixed price for phase one. See also legacy application modernization.
Broadcom Expert Advantage Tanzu Services Partner of the Year, AMER, 2025 · awarded to the AceMQ engineering team
Proof
The engineers behind Ace8 are the AceMQ team, and this is work they delivered. Ace8 is the new name for that practice, not a new team.
IBM MQ → RabbitMQ
Legacy messaging replaced in phases while the applications calling it were refactored. No big-bang cutover; each phase reviewed before the next.
FAQ
Short answers to what buyers ask first. Something else on your mind? Ask an engineer.
PowerBuilder is sold and updated by Appeon, with PowerBuilder 2025 R2 generally available on 3 June 2026. Check Appeon's support policy for the version you run.
DataWindows, because each combines data access, presentation and update logic. They are the centre of the inventory.
Pick the stack your organization already staffs and integrates with. The assessment recommends one per module.
No. Ace8 does the assessment and plan and a vetted specialist partner delivers. The proposal names who does what.
Start here
A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.
Get in touch
Tell us what you run today. An engineer, not a sales script, replies within one business day.