Your Oracle Forms system still works. That's exactly the problem.

No one enjoys migrating a system that runs fine. But "fine" is temporary. Oracle's Premier Support for Forms 12c ends in December 2026. Extended Support follows in December 2027. After that, there are no new security patches, no bug fixes, and no compliance cover, which for any regulated business is not a technical debt issue. It's an audit finding waiting to happen.

Meanwhile, three other pressures are compounding daily:

01. Escalating costs

Oracle Forms doesn't run on its own. It requires WebLogic middleware with a separate license, Extended Support surcharges on top of standard fees, and custom infrastructure to keep a Java applet-based architecture alive in a modern browser. Every year you stay adds costs that have nothing to do with business value.

02. A shrinking talent pool

Oracle Forms developers are retiring faster than new ones are trained. It's a technology from the 1990s — no new developer chooses to learn it. Finding someone who understands your specific Forms codebase, often built over decades by people who have long since left, is becoming nearly impossible and increasingly expensive.

03. A system that can't evolve

Mobile access? Real-time API integrations? AI-powered features? Modern analytics? None of these work with a client-server architecture launched via Java applets. Every new business initiative your organization wants to pursue runs into the same wall.

The decision is no longer whether to migrate. It's how – and to what.

We don't sell you a destination. We help you find the right one.

Pretius AI Semantic Search with LLMs - cover photo

The standard approach to Oracle Forms migration goes like this: a vendor shows you their preferred platform, builds a business case around it, and starts a project. The analysis happens after the technology decision.

We do it the other way around.

Before recommending anything, we use an AI-driven discovery process to understand exactly what your system does today — which screens are actively used, which haven't been touched in years, how the business logic connects across your database, and what a realistic migration scope actually looks like. That analysis is the first deliverable, not a free pre-sales step. It takes days, not months.

Only then do we recommend a path. And the path depends on your strategic intent – not on which platform we happen to know best.

Three migration paths. One right answer for your situation

After the discovery phase, the technical migration follows one of three scenarios. Each addresses a different organizational need. We work across all three.

Path #1

Stay Oracle, move to APEX

If your organization is committed to the Oracle ecosystem — your team knows PL/SQL, your database holds decades of business logic you can't afford to lose, and you want a migration path with zero license cost increase — Oracle APEX is the right destination.

APEX is a free feature of your existing Oracle Database license. It eliminates WebLogic middleware entirely, runs natively in any browser, and allows developers to build applications 10–20× faster than traditional code. Because both Forms and APEX are built around PL/SQL, your core business logic — the procedures, functions, and calculation packages your operations depend on — migrates cleanly without rewriting.

Best for: Organizations with Oracle-centric IT strategies, strong PL/SQL investment, and teams that want to stay in the Oracle world while eliminating the legacy Forms overhead.

Note: We have proven expertise with Forms-to-APEX migrations and tools, such as the Pretius AI Forms to APEX Assistant, that help accelerate the process. When a client is committed to APEX, we do it right.

Path #2

Stay on Oracle DB, modernize the frontend

Your PL/SQL business logic is valuable. Your Forms frontend is not. If you want a modern, AI-compatible, mobile-ready front end without touching the database layer, this path delivers exactly that.

We rebuild the presentation layer in the technology that fits your team and technology strategy — Java, React, or another framework of your choice. Your Oracle database, your stored procedures, your business rules: all preserved. What changes is everything the user sees and interacts with.

This path makes particular sense for organizations that have already standardized on Java or modern web stacks elsewhere in their estate, and want consistency rather than introducing a new Oracle-specific platform.

Best for: Organizations with mixed technology environments where Oracle coexists with modern stacks, or where AI integration and mobile access are primary drivers of the migration.

Path #3

Full exit from Oracle

If your Oracle Forms application is the last reason you're paying Oracle license fees, this path eliminates the relationship entirely. We migrate both the frontend (as in Path 02) and the database — typically Oracle to PostgreSQL, a production-ready, enterprise-grade open-source database with zero licensing cost.

This is not a theoretical scenario. Pretius has tooling and processes to handle the Oracle-to-PostgreSQL migration in a structured, semi-automated way. The result is a fully open-source stack with no vendor lock-in, predictable infrastructure costs, and an architecture that integrates cleanly with modern cloud environments.

Best for: Organizations looking to eliminate Oracle licensing costs entirely, reduce vendor dependency, or align with a cloud-native or open-source infrastructure strategy.

The hardest part of any Forms migration isn't the code. It's knowing what the code actually does

Ask any IT director who has attempted an Oracle Forms migration before, and you'll hear the same story. The analysis phase – understanding what the system does, which parts are used, what the business logic actually means – consumed more time and resources than the development itself. Months of analyst work. Meetings where business users couldn't articulate what they needed because they'd simply clicked the same screens for fifteen years. Modules discovered mid-project that nobody knew existed. Dead code that looked live.

We've built a process that solves this structurally.

Our AI-driven discovery ingests everything available about your system:

Input

What it tells us

FMB files (Oracle Forms XML source).

Complete map of screens, triggers, and program logic.

Oracle database schema.

Table relationships, stored procedures, dependencies.

Existing documentation.

Business context, intended behavior, known edge cases.

Historical support tickets.

What actually breaks, what users actually use.

Test cases and process descriptions.

Behavioral coverage and exception scenarios.

AI agent running against the live system.

Real usage paths discovered autonomously.

The output is a structured specification of your system as it actually functions — including a dependency graph that maps how every button, procedure, and function connects. For the first time, you have documentation of something that was previously only understood by people who may no longer work at your company.

This specification delivers three things before you commit a budget to development:

A precise scope for the migration (what needs to move, what can be retired, what is dead code).
A realistic timeline and cost estimate grounded in what's actually there.
A risk register: gaps in logic, undocumented dependencies, and complexity hotspots.

The discovery phase takes days, instead of months. Moreover, the quality of output is incomparable.

We are a top-rated software development company for a reason

+ years

Powering market leaders with expert software development for two decades.

+ Specialists

Your dedicated team: over 300 highly-skilled software professionals at your service.

+ projects

Successfully delivered over 1000 diverse and impactful software projects.

% stay with us

Clients trust our work, with 93% becoming long-term partners.

+ years together

Cultivating lasting partnerships, some flourishing for over 18 years.

+ conference talks

Actively contributing to the global tech conversation with 30+ annual international presentations.

We keep your data safe: ISO certified

We operate in accordance with the ISO 27001 standard, ensuring the highest level of security for your data.

Why Pretius

We know Forms from the inside

We've executed Oracle Forms migrations for financial institutions, logistics companies, and industrial enterprises across Europe. We know how Forms applications are structured, where the complexity hides, and what "migrating the PL/SQL logic" actually means in practice. This isn't theoretical expertise — it's project-tested.

Technology-agnostic recommendation

We are Oracle experts. We are also Java developers, React engineers, and PostgreSQL architects. That breadth means we have no structural reason to push any one path. Our recommendation follows your data, your team, and your strategy — not our commercial preferences.

The analysis is a deliverable, not a sales step

Our discovery phase produces a specification you own. Whether or not you proceed with Pretius for the development, you leave with a clear, AI-generated map of your system that you did not have before. That has value on its own.

We've solved the hard UX problems

The biggest reason past Forms migrations failed wasn't the code — it was the users. Power users who had worked keyboard-only for fifteen years refused to adopt mouse-driven web interfaces. We've built custom solutions for multi-session isolation (each browser tab maintains its own independent state), keyboard shortcut preservation, and high-density data entry screens. User acceptance isn't an afterthought in our process. It's engineered.

Gradual migration, no big bang

We don't turn off the old system and turn on the new one over a weekend. Our parallel-running approach allows the old Forms system and the new application to operate simultaneously on the same database. Users migrate module by module. If something in the new system causes a problem, they return to Forms while we fix it. Business continuity is not at risk.

Scale and long-term partnership

300+ specialists. Offices in Warsaw and London. 93% of clients continue working with us after the first project. We are built for the scale of the projects Oracle Forms modernization requires — and we're here for what comes after the migration, too.

Our process

01

Discovery & scoping

We begin with our AI-driven discovery phase. We ingest your FMB files, database schema, available documentation, and any other system artifacts. An automated agent explores the live application, maps real usage paths, and correlates everything into a structured specification. Output: a precise scope, a dependency graph, a risk register, and a preliminary cost and timeline estimate. This takes days, not months.

02

Path recommendation

Based on the discovery output, we present a clear recommendation: APEX, custom frontend on Oracle, or full Oracle exit. We walk through the rationale, the tradeoffs, and the five-year cost-of-ownership comparison across the options. You choose with full information, not sales pressure.

03

Proof of Concept (optional but recommended)

If the scope is large or the organizational risk is high, we start with the most complex module — not the simplest. If we can migrate your hardest screen successfully, everything else follows. A PoC takes 4–8 weeks and eliminates the uncertainty that derails big-bang migrations later.

04

Phased migration

We execute the migration module by module, in two-week sprints with regular stakeholder demos. The new system and the old system run in parallel on the same database. Users switch to new modules gradually, building confidence and familiarity rather than facing a forced cutover.

05

User acceptance & handover

We don't treat user acceptance as testing — we treat it as a design constraint. Key workflows, keyboard shortcuts, and session management behaviors are validated with actual power users before any module goes live. When the project closes, your team has either been trained or — if you chose the co-creation model — has developed the skills to maintain and extend the new system independently.

Flexible project approaches

01 Co-creation

Our preferred model for complex, business-critical migrations. Our engineers work alongside your in-house team from day one. Knowledge transfers continuously. When the project ends, your team understands the new system deeply enough to own it — not just use it. This model was central to the Santander Leasing migration, where Pretius developers and the bank's internal team formed a single unit.

03

02 Dedicated development teams

You have a clear scope and a clear destination. We provide a cross-functional team — developers, analyst, QA, DevOps — that operates as an extension of your organization. You maintain strategic control; we bring the execution capacity.

02

03 Full project delivery

You hand us the project, we deliver the outcome. Defined scope, defined timeline, defined budget. Minimal internal overhead for your team. Optional maintenance SLA after go-live.

04 Team augmentation

You have an internal team running the migration but need specific expertise — Oracle database architecture, Java backend, React frontend, or PostgreSQL migration. We slot specialists into your team for as long as you need them.

What our clients say

Bilal Ramadan

Chief Executive Officer at Munich Re HealthTech

The solution is secure, scalable, and compatible with most technologies used by Munich Re HealthTech’s clients. It’s also much cheaper to maintain which was an important success criteria factor. Application licensing costs were largely reduced.

Radosław Olkiewicz

CEO at Profitowi

Thanks to the new client needs analysis system, our sales process is much easier and standardized. It helps our Experts better tailor insurance or financial solutions to the needs of the client. This results in increased sales to new clients and smooth upselling to existing ones.

Przemysław Wilary

IT Project Manager at Play

We were impressed with Pretius' experience in the telecom industry. They proposed a few unique solutions that enabled our employees to configure individual offers faster than ever before.

Marek Samujłło

CIO of Emitel

What I like the most, as the CIO, is that the people at Pretius care not only about technology itself but rather about how this technology can help your company achieve business goals.

Zuzanna Świętorzecka

Head of Bancassurance at BNP Paribas

The communication throughout the project was very good as Pretius provided us with a Project Manager who always addressed our needs. The most impressive thing was how quickly the team developed a fully working, market-ready software solution for us.

Konrad Gałecki

Digital Manager at Philip Morris Distribution

Usually, you can either get a high-quality software solution or have it developed fast. However, thanks to choosing the right technology, the Pretius team was able to provide us with a fully working platform in a relatively short time.

Artur Męcina

IT Manager at T-Mobile Poland

The most important thing about Pretius is that they care to understand your business goals. And, having a bunch of enterprise-grade and SME-grade projects under their belt, they’re very good at it.

Renata Kania

Senior Security Awareness Specialist at T-Mobile

Pretius has quite a few huge, enterprise-grade projects in their portfolio. I believe the reason for this is that they go the extra mile to understand the partner’s business goals and do what they can to provide a software solution that meets these goals.

Piotr Blaszczyk

Executive Director of EBS

Pretius has a lot of experience in dealing with big, enterprise-grade companies like ours. They’ve proved they have a keen understanding of our needs and business goals.

Adam Kasperowicz

CIO at VAN group

The new e-VAN system has become an innovative tool and work environment. The development team allows us to use the potential of the latest trends and technological solutions: web & mobile development, responsiveness, integrations, low-code, and cloud computing.

Graem Lourens

Co-Founder & CTO at Lourens Systems

They’ve garnered our confidence and loyalty through their technical skills and the deep involvement.

Marijn van den Berg

Team Manager of Obsurv Software at Sweco

Thanks to our collaboration with Pretius, we've made it easier for our clients to utilize Obsurv. Customizing the application modules to their specific needs is now much quicker and more efficient. For us, this means shorter customer onboarding times and lower costs.

Gordian Ratajczak

Product Owner at Neuroflash

They effectively assess a project and allocate the matching resources, which gives confidence that you are in good hands. Issues and tasks are handled proactively and communication stands on a firm ground of mutual understanding and goals. You are not hiring an external resource, but you are gaining a team member.

Esteban Michalowski

CTO at AltaPay

I’ve always found interactions with Pretius (previous IN Team) to be both streamlined, light, and effective. Pretius always seeks ways to improve, and have a process for ensuring the collaboration is going according to expectations.

Richard Coombes

Head of Engineering at Equals Money

They allowed us to deliver against our 20/21 roadmaps, launching new products to market and increasing company revenue by over 70%.

FAQ - Legacy Modernization

Most failed migrations share the same root cause: the scope wasn't properly defined before development started. Analysts interviewed users, who said what they thought they used — not what they actually used. Months later, modules were discovered mid-project that hadn't been mentioned. Our AI-driven discovery phase exists specifically to solve this. We map what's actually in the system, not what people remember about it.

No. APEX is one of three paths we offer, and we will only recommend it if it genuinely fits your situation. If your organization is moving away from Oracle or has already standardized on Java or modern web stacks, we have structured processes for both the Oracle-DB-with-modern-frontend path and the full Oracle exit to PostgreSQL. We are not an APEX-only shop — we are an Oracle-fluent shop that also builds with Java, React, and open-source databases.

Yes — this is exactly the scenario the process was designed for. The discovery is built on what's in the system itself (FMB files, database schemas, live application behavior) rather than what's in a specification document. Lack of documentation is the norm in legacy Oracle Forms environments. We treat the system as the primary source of truth.

Significantly more accurate than estimates produced without structured discovery. Our AI-assisted scope analysis has a proven accuracy rate in the range of 90% for project effort estimation. The dependency graph also reveals complexity and risk concentrations that traditional estimating methods miss entirely.

Yes. Because both Forms and the target system operate against the same Oracle database, the data layer is shared. Users can be on the old Forms screen for one module and the new APEX (or Java) screen for another, simultaneously. This is not a theoretical claim — it was exactly how the Santander Leasing migration was executed.

Regulated industries are among the most important candidates for migration — and among the most common clients we serve. For financial sector clients, the end of Oracle Forms Premier Support in December 2026 is not a preference issue; it's a regulatory one. Operating on unpatched software under KNF, DORA, MiFID II, or similar frameworks is an active compliance liability. We understand these regulatory environments and build the migration process around them, including audit trail requirements, change management documentation, and phased rollouts that minimize systemic risk.

The discovery phase takes days to a few weeks, depending on system size. The migration itself depends entirely on the actual scope revealed by discovery — not on our pre-sales estimate. A system with 20–30 actively used Forms modules typically migrates in 3–6 months. A system with hundreds of active screens takes longer, but our phased approach means you're running new modules in production long before the full project completes.

Oracle Forms migration on your terms: Choose based on analysis, not vendor preferences

Most migration partners sell you a technology before they understand your system. We start by understanding what you actually have – then we tell you where to go next.