**Oracle Forms is still the backbone of the IT infrastructure of many companies. However, the technology is quite old and it seems like Oracle itself is cutting off some of its support, focusing on other solutions. Thus, it’s time to consider migrating to something else – and, in my opinion, Oracle APEX seems to be one of the most reasonable choices.**

\
What is the matter with Forms’ support? Why migrate to APEX? What are the benefits? In this article, I’ll provide you with answers to these questions – based on more than 10 years of experience with both of these technologies.

## **Oracle Forms and APEX – what are they**

Let’s start with the basics. I’ll describe each of the solutions briefly and tell you what they’re all about.

### **Oracle Forms**

Oracle Forms is a Rapid Application Development (RAD) platform and a component of the Oracle Fusion Middleware. It was first introduced in 1981, albeit it was known by a different name back then – Interactive Application Facility. You can use it to create data entry systems that use the Oracle Database as a basis.

\
Oracle Forms’ main advantage was its ease of use. Creating simple applications didn’t require advanced coding skills – just some SQL and PL/SQL basics. In a way, it was a precursor to the solutions we now call [low-code](https://hackernoon.com/low-code-software-engineering-7-things-to-know) and [no-code](https://hackernoon.com/low-code-vs-no-code-a-buzzword-battle-for-the-ages) platforms, such as Mendix, OutSystems, and (of course) the other main protagonist of this article – Oracle APEX.

\
The current version of Oracle Forms is 12c, and the software is [still supported](https://www.oracle.com/a/tech/docs/oracleformssod.pdf) by its creators. However, with the end of 2023, Fusion Middleware (and Forms along with it) will lose its Premier Support status. Extended Support will only last less than two years longer – until August 2025.

### **Oracle APEX**

Oracle APEX (Application Express) is a much newer solution, even though it’s not exactly brand new either, with a history that reaches back to 1999 (when it was named Oracle HTML DB). In fact, that’s one of APEX’s strengths – it’s mature enough to be considered a stable and safe choice for enterprise-grade businesses, but also new enough to be very actively developed, and fully supported for years to come.

\
APEX’s concept is more or less the same as the idea behind Oracle Forms. The platform exists to offer people a way to create data-driven apps easily, without the help of expert software developers. That’s not to say you can use APEX without any technical knowledge, because some coding skills and database knowhow come very handy. However, with a little bit of training, many things – such as creating a layout, designing interface or application logic – can be done without writing a single line of code. You simply use the specialized Wizard provided by the platform’s developers.

\
APEX is cloud-based, which is the biggest advantage over Forms. Outside of that, though, it offers many of the same benefits Forms does – it also uses Oracle DB, so it's safe, stable, very scalable, and feature-rich (you get Spatial, ML/AI modules, and so on). What’s more, most Forms modules have their __[APEX counterparts](https://docs.oracle.com/en/database/oracle/application-express/19.2/aemig/understanding-Oracle-forms-modules.html#GUID-5B18910F-0F3B-4833-A19B-A3D0FFBA61D2)__, so migration is relatively easy.

\
The newest version of Oracle Application Express is 22.1. The platform is still actively developed and supported.

## **What you can gain by migrating to APEX**

Oracle Forms to Oracle APEX migration has many advantages:

\

1. APEX is even easier to use than Forms. It means you don’t need to hire so many software developers because some of the work can be done by other people.
2. Java Development Kit or Java Runtime Environment aren’t required to run APEX apps because everything works online. It results in easier access. You just need a computer with a supported web browser: Chrome, Firefox, Safari, or Edge. Or a mobile device.
3. Oracle APEX works with the cloud and doesn’t even require an on-premise database to work (you can use AWS, Azure, or Oracle’s own Autonomous Database). Also,  developers don’t need to install dev environments (Forms Builder, Developer) – once again, web browser is everything you need for development in APEX.
4. It has easier and more robust customization, including more options for layouts, themes, interface elements, etc.
5. If you’re using Oracle DB (any version, all are compatible with some iteration of APEX), Application Express is free and you can use it anytime.
6. You stay in the Oracle tech stack, which means you probably already have the competencies and skills you need in your team, as well as the required licenses.

## **Problems that can arise**

If you want to migrate from Oracle Forms to Oracle APEX, there are some possible problems you should know about.

\
First of all, change isn’t always easy for employees, and Forms is an old tech. Some people – both programmers and so-called citizen developers (Forms users that are not tech-savvy) – have used it for decades. Literally. They may not necessarily like the idea of migration, because they don’t want to learn everything from scratch. It’s an understandable problem, and you should address it somehow, to dispel these fears.

\
Show your people that the new technology is similar, but even better, and easier to use. Tell them how it can make their work more efficient. Invest in APEX developers who  not only can create apps but also talk with the non-tech people (citizen developers) and show them how to use APEX. If you can convince a few people of the benefits, they’ll help you reach the others.

\
Also, despite all the similarities and sharing the Oracle tech stack, a Forms-APEX migration can still be quite complex, which means it can be expensive and time-consuming. It all depends on the size of your current software.

## **The story of a Forms-to-APEX migration**

But enough with the theory. Time for a little case study – I would like to present you a real-life __[story of Oracle Forms migration](https://pretius.com/blog/oracle-forms-migration/)__.

\
The task was to migrate the IT infrastructure of a European TSL (transport-shipping-logistics) company. They’ve used Forms for many years, but it started to show its age. As they wanted to invest in a brand new, machine-learning-powered freight management system, it seemed like a good time to perform a tech stack upgrade.

\
It was me and my low-code team who helped them migrate to Oracle APEX. Several parts of the system had to be rewritten in APEX – from scratch – and then adapted to work in the company’s existing infrastructure. But that’s not all: we worked closely with the in-house developers of the client, sharing with them our know-how, and while in the beginning they were quite reluctant, by the end of the migration they turned to new-born APEX believers.

\
The new system is cloud-based and runs in a web browser – which means it can be used from anywhere and on pretty much any device. It can also use ML (machine learning) for predicting the costs of freight transportation, speeding up the whole process of freight management. Last but not least, the new solution turned out very cost-efficient, as the number of required licenses was reduced significantly.

\
In the end, abandoning Forms in favour of APEX proved to be very beneficial for that company. Of course, I won’t advise such a migration in 100% of the cases. But if your company’s software is based on Oracle Forms, at least get to know APEX (or consult someone who does) – it’s a high chance that you can benefit from it too. Easier development, better user experience, lower costs, better scalability – sounds pretty good, doesn’t it?

The writer is smart, but don't just like, take their word for it. #DoYourOwnResearch

The writer was physically present in relevant location(s) to this story.

Read My Stories

Too Long; Didn't Read

Cassandra Forward a free Cassandra-focused community event

Migrating From Oracle Forms to APEX? I’ve Done it and Here’s Why I Think You Should Too

Too Long; Didn't Read

@pstaniszewski

Credibility

RELATED STORIES