Legacy system assessment
Inventory of forms, reports, libraries, procedures and dependencies, with the complexity of each module and the recommended modernization path.
We bring your desktop and client-server systems to the web and the cloud while keeping what matters most: the business rules, the data and the years of investment you have already put into them.
Many companies still run critical processes —accounting, payroll, logistics, invoicing— on systems built with Oracle Forms and Reports, PowerBuilder or Windows Forms. They work, but every year it gets harder to find specialists, install them on new machines, integrate them with tax authorities, banks or mobile apps, and keep them secure.
Rewriting everything from scratch is expensive and risky: years of business logic live in the code, in PL/SQL procedures and in the heads of a few people. That's why we modernize in stages: we inventory and document that logic, reuse it —in the database or exposed as APIs— and migrate the screens to a modern web interface, module by module, without stopping operations.
Inventory of forms, reports, libraries, procedures and dependencies, with the complexity of each module and the recommended modernization path.
Upgrade to supported versions or migration to the web with Oracle APEX, Java or Angular, reusing existing PL/SQL packages and procedures.
Upgrade to current Appeon PowerBuilder versions or migration to web applications and APIs in .NET or Java, preserving DataWindows and business logic.
Migration from .NET Framework to modern .NET and evolution to the web, separating logic from the UI so it can be reused in APIs.
We wrap existing rules in REST services so the old and new systems can coexist and integrate with other applications.
Migration of reports to modern tools and data validation through side-by-side tests between the old and new systems.
We reuse the business logic, procedures and data that already work.
Module-by-module migration, with both systems running side by side until the transition is complete.
Side-by-side tests that verify the new system calculates the same results as the old one.
Web access, cloud, APIs and integration with new tools, including artificial intelligence.
We analyze your architecture, processes and business goals to identify risks and opportunities.
We design an architecture and technical roadmap aligned with your goals and budget.
We build the solution with engineering best practices and constant communication.
We validate quality, performance and security before a controlled production rollout.
We support operations with monitoring and evolutionary improvements to the solution.
Challenge: A legacy ERP had to meet SUNAT electronic obligations (SIRE, CPE and GRE) and validate identities with RENIEC, without rewriting the existing system.
Solution: Integration layer connecting the ERP with SUNAT services for electronic registers (SIRE), electronic payment vouchers (CPE) and electronic remittance guides (GRE), plus RENIEC queries for identity verification.
Challenge: Critical applications on WebLogic, JBoss, Apache HTTP Server and Apache Tomcat faced version migration risk, downtime from insufficient maintenance and production performance degradation.
Solution: Controlled migration across versions and environments, preventive and corrective middleware maintenance, and JVM, pool, connector and Apache/Tomcat/WebLogic/JBoss configuration tuning to stabilize and optimize operations.
No. The first step is to inventory and document the business rules. Much of it usually lives in database procedures and packages that are reused as is; logic in the screens is moved to services or APIs and validated with side-by-side tests against the current system.
Not necessarily. Depending on the system's condition, we recommend upgrading to a supported version, migrating it to the web module by module, or wrapping it with APIs. A full rewrite only makes sense when the code no longer adds value.
The main ones are upgrading to a supported Oracle Forms version, migrating the screens to Oracle APEX while reusing the existing PL/SQL, or building a web application in Java or Angular on the same database. We choose based on your budget, your team and your future plans.
Yes. PowerBuilder applications can be upgraded to current Appeon versions and taken to the web, or migrated to .NET or Java. For Windows Forms, we first migrate from .NET Framework to modern .NET and then separate the logic into APIs to build a web interface.
It depends on the number of forms, reports and modules. The assessment takes a few weeks and the migration is planned in stages, delivering the highest-value modules first so the business sees results from the start.
Tell us what you need and we'll propose a solution with clear scope, timeline and budget.