Forms Converter

Oracle Forms has served enterprises well for decades, but it's a technology born in the 1990s. While it's still the backbone of many critical systems, the tech landscape has moved on. 

Modernisation is a matter of staying competitive. According to recent surveys, 92% of companies are already in the process of modernising or have it on their radar. Even more telling, 87% of business leaders believe that modernisation is key to future growth.

So where does Oracle ADF fit into this picture? Is it the natural evolution for Forms-based applications or should you look elsewhere?

Why Bother Modernising at All?

A shrinking talent pool is driving up costs. Oracle Forms developers are becoming a rare breed. As seasoned professionals retire, it’s becoming harder and more expensive to find the right talent. The fewer experts available, the higher the cost of maintenance and the greater the risk of knowledge gaps.

The architecture is outdated. Forms relies heavily on a database-centric model, which makes it tough to scale, adapt, or integrate with modern tools. It also limits how much you can improve the user experience. If you’re looking to compete with sleek web and mobile apps, Forms will hold you back.

Vendor lock-in and licensing issues. Continuing with Forms means you’re tied to Oracle’s ecosystem, its licenses, its platforms, and its timelines. This makes long-term planning tricky and expensive.

There are real financial gains. Organisations that modernise their legacy applications report up to 50% savings on maintenance, 35% lower infrastructure costs, and a 14% boost in revenue. The payoff is significant.

What Is Oracle ADF?

Oracle Application Development Framework (ADF) is a Java-based platform designed for building enterprise-level web and mobile apps. It’s part of Oracle’s ecosystem and comes with a rich library of UI components, integration capabilities, and tools for building scalable applications.

Key features include:

• Java EE foundation with support for service-oriented architecture.

• Over 150 pre-built UI components.

• Seamless integration with Oracle Fusion middleware.

• Built-in security features.

Why Some Teams Choose ADF

1. Business logic isn’t wasted. ADF allows for partial automation of migration from Oracle Forms. Some third party tools can convert 50–90% of existing modules, depending on complexity. This means you don’t have to rebuild everything from scratch.

2. It brings a modern UI. With a large component library and responsive design capabilities, ADF enables the creation of user-friendly dashboards, workflows, and mobile-ready interfaces.

3. It’s a familiar space for Oracle shops. If your systems are already running on Oracle technologies, ADF may seem like a comfortable next step. It integrates well with Oracle’s middleware, SOA, and security frameworks.

4. Scalability and security are built in. Running on Java EE servers like WebLogic, ADF can support large-scale deployments and offers advanced authentication, authorization, and integration with identity providers.

Where ADF Falls Short

1. Cost is a major hurdle. ADF typically requires Oracle WebLogic and Oracle Database licenses. These don’t come cheap. Add development and maintenance costs, and the total cost of ownership can be high.

2. There’s a steep learning curve. ADF development is not beginner-friendly. It involves Java EE, JSF, and Oracle-specific tools. For teams coming from Forms, the transition will require significant upskilling.

3. You’re still tied to Oracle. Migrating to ADF doesn’t solve the vendor lock-in problem, it extends it. If you’re thinking about a multi-cloud or open-source future, ADF could limit your flexibility.

4. Not everything can be automated. While automation tools help, expect to manually rework 20–50% of your complex modules. Business logic, validations, and UI nuances often require hands-on effort.

5. Ongoing maintenance is still complex. WebLogic patches, Java updates, and Oracle-specific quirks require constant attention. For organisations aiming to simplify their tech stack, this might not align with their goals.

Exploring Better Alternatives

Oracle Redwood UX 

Redwood is Oracle’s new design system across its Fusion applications. It’s modern, responsive, and includes consistent UI components. Projects that use Redwood report up to 80% savings on time and cost thanks to automation and standardisation. It’s also Oracle’s future default, so early adoption helps ensure compatibility.

Oracle Visual Builder (VBCS) 

A low-code, cloud-native platform using JavaScript and Oracle JET. It offers a drag-and-drop interface for rapid development of responsive web and mobile apps. VBCS eliminates the need for WebLogic and reduces infrastructure costs.

Oracle APEX 

If your apps are data-heavy, APEX is worth a look. It’s a declarative development platform embedded in the Oracle Database. Using PL/SQL and SQL, it supports rapid prototyping and responsive design. Best of all, it comes included with your Oracle Database license.

Open Frameworks (Java + React/Angular) 

For full independence from Oracle, modern frameworks like React or Angular offer complete flexibility, reduced licensing costs, and access to a larger developer community. Automated tools like Kumaran Systems’ Forms Converter can help convert forms to web platforms on JEE/.NET without proprietary frameworks.

Lessons from the Field

• Even with automation, plan for manual effort, especially for complex modules.

• Most modernisation projects take 16 months or more. Go with phased rollouts to manage risk.

• Cost is a real factor. ADF is expensive. Low-code options like APEX and VBCS are more budget-friendly.

• ADF demands Java skills. Redwood, VBCS, and APEX are more accessible for teams without deep Java experience.

• Oracle’s future lies in Redwood and cloud-native solutions. Aligning with this vision means fewer surprises down the line.

Planning for Success

1. Inventory your Oracle Forms modules. Categorise them by complexity and function such as CRUD, business logic-heavy, or highly interactive.

2. Run a pilot migration. Use tools like PITSS.CON to evaluate what can be automated and what needs manual work.

3. Choose the right platform.

• APEX for internal, data-driven apps with minimal licensing costs

• VBCS for interactive UIs and fast deployment

• Open-source stacks for long-term flexibility

• Redwood for staying aligned with Oracle’s Fusion applications

4. Upskill your team. Whether it's Java for ADF, JavaScript for VBCS, or PL/SQL for APEX. Training is essential. Involve users early through prototypes and feedback sessions.

5. Don’t go all in at once. Keep critical Forms apps running while gradually migrating functionality. Use APIs and microservices to let old and new systems coexist.

6. Be smart about costs. Use Oracle cloud services strategically. Consider free APEX hosting or subscription-based VBCS to avoid large upfront investments.

Is ADF Still the Right Move?

For some organisations, ADF provides a robust, modern environment with solid Oracle integration and strong tooling support. But it's not the only path forward, and in many cases, it's not the best one.

Low-code platforms like APEX and VBCS, Redwood UX, or open-source JavaScript frameworks offer leaner, more flexible, and often more affordable alternatives. The key is matching the right tech to your team’s skills, your business goals, and your long-term strategy.

Modernising Oracle Forms isn’t about picking the flashiest new platform. It’s about choosing the one that keeps your business moving forward, without breaking the bank or boxing you in.

Oracle Forms, introduced in the 1980s, rapidly gained popularity thanks to its intuitive user interface and impressive capabilities. It's fascinating to know that its creation stemmed from a simple need: a user-friendly way to input data into databases. Bill Friend, Oracle's second employee, was tasked with this very challenge, and his work ultimately led to the birth of Oracle Forms.

Over the years, Oracle Forms has become a cornerstone in crucial industries like banking, insurance, and government agencies. These sectors, often relying on extensive legacy systems, have found Oracle Forms to be remarkably resilient and well-suited to their user interface needs. It's a testament to its original design that even today, these organizations depend on it.

While Oracle Forms has evolved to incorporate modern technologies and adapt to changing user expectations, its core functionality has largely remained consistent. This stability is a key reason why many businesses, despite the availability of newer alternatives, continue to rely on it. There's a certain comfort in the familiar, isn't there?

However, the landscape is shifting. Oracle has announced the end of Premier Support for Oracle Forms 12.2.1.4 in December 2026, with Extended Support lasting only until December 2027. After that, businesses will have to rely on Sustaining Support, which unfortunately excludes crucial updates and security patches. This looming deadline presents significant risks for organizations still dependent on Oracle Forms, especially concerning security vulnerabilities, compliance requirements, and the urgent need for modernization. It's a daunting prospect for many.

At Kumaran Systems, we understand these challenges. That's why we've developed a Forms converter that can refactor code and migrate applications to Java or C# with HTML5 and Angular. This innovative approach eliminates the need for a complete rewrite, saving significant time and resources. Our tool-based conversion automates the process, minimizing manual effort and drastically reducing development time. Because it doesn't involve any proprietary frameworks, it's a low-risk development project with the benefits of automation. We believe this offers a secure and efficient pathway to modernization for businesses facing the end-of-support deadline.