What is the difference between Oracle Forms and Oracle APEX?

Oracle Forms is a desktop-style form builder in which triggers control most behaviour. Oracle APEX is a low-code platform that builds browser applications inside the Oracle Database, where behaviour is set through validations, computations, dynamic actions and processes (Oracle solution playbook). APEX is included with Oracle Database; ask your Oracle contact to confirm what applies to your licence.

Can Oracle Forms be converted to APEX automatically?

No. Oracle desupported the APEX Migration Project feature as of APEX 21.1, and its FAQ recommends rebuilding the applications in APEX rather than converting them. Screens are therefore rebuilt, while the database logic can be reused.

What should I inventory first?

Count the forms, reports, PL/SQL libraries, menus and object libraries, then record where the business logic lives, the integrations, the Forms, Reports and database versions, any WebUtil, Java bean, PJC or OLE use, batch jobs, roles and users. The table above lists each item and why it matters, and the template covers it in a spreadsheet.

How do I choose a migration partner?

Ask for references you may call, a sample assessment of two or three of your real forms before a contract, named APEX and PL/SQL leads, and a clear testing and sign-off method. Be wary of promises of full automatic conversion or estimates made without seeing your code.

Should business logic be moved to PL/SQL first?

Usually yes. Oracle's solution playbook notes that stored procedures and PL/SQL packages work natively in APEX, so logic held in database packages is reused rather than rewritten. Logic that sits only in Forms triggers has to be found and either moved or rewritten.

What happens to Oracle Reports?

Reports are not part of the screen rebuild and are assessed on their own. For each report, record where it is called from, its parameters and output format, then agree how it will be rebuilt and how the output will be compared with the original.

How is parity tested between Forms and APEX?

Run the same agreed test data through the old form and the new page, compare results side by side, and have a named business owner sign off each module. Reports and printed output are compared the same way.

What support is there after go-live?

It depends on the vendor and must be agreed before you sign: what is covered, for how long, how defects found after release are handled and who answers when something breaks. ROSTAN can discuss support as part of an assessment.

Can Forms and APEX run side by side?

Yes, both work against the same Oracle Database, so an estate can move module by module while the remaining forms keep running. Plan shared security and navigation so users are not confused between the two.

Download the inventory template, fill in the Forms, Reports, Libraries and Integrations sheets, and pick two or three representative forms. Then ask any vendor, including ROSTAN, for a sample assessment of those forms.

Trusted Digital Transformation Partner

Oracle Forms to APEX Migration Checklist: How to Choose a Partner and Inventory Your Forms

What to count in your Forms estate, how to compare migration partners, and when to rebuild, keep or run both.

Get the inventory template Book a meeting

In short

Oracle Forms screens cannot be converted to Oracle APEX automatically: Oracle desupported the APEX Migration Project as of APEX 21.1, so screens are rebuilt in APEX. The safest start is to inventory your Forms estate (forms, reports, libraries, integrations, versions, where the business logic lives), then ask each vendor for a sample assessment of two or three of your real forms before you sign. Below: what to count, how to compare partners, red flags, your options, and a free spreadsheet template. For ROSTAN’s own service see APEX application migration.

Part A: Inventory Your Oracle Forms Estate

Count these before you talk to any vendor. Every item changes the size and risk of the work.

Item	What to record	Why it matters
Forms modules (.fmb)	Name, business area, Forms version, number of blocks and canvases, last used.	Forms are the units of rebuild work. Unused forms may not need rebuilding at all.
Oracle Reports (.rdf)	Name, called from which form or batch job, parameters, output format (PDF, Excel, HTML, printer).	Reports and printing are a separate piece of work from screens and need their own plan.
PL/SQL libraries (.pll)	Name, which forms attach it, whether it holds business rules.	Shared logic sits here. It is reused by many forms and is the first candidate to move into the database.
Menus (.mmb) and object libraries (.olb)	Menu structure per role, shared objects and standard look.	Menus map to APEX navigation and roles; object libraries show how consistent the screens are.
Database triggers and program units	Triggers, packages, procedures, functions that the forms call.	Logic already in the database can be reused by APEX as it is.
Where business logic lives	For each important rule: Forms trigger, library or database package.	Rules held only in Forms triggers have to be found, documented and moved or rewritten.
Integrations	Web services, file in/out, Oracle E-Business Suite interfaces, database links, email. Direction, frequency, owner.	Every integration needs its own test and an owner who can confirm it still works.
Forms and Reports versions	6i, 10g, 11g or 12c, and the patch level.	The version tells you which features and customisations may be in use.
Database versions	Version and edition of each database the forms use.	The target APEX release has its own database requirements.
Custom UI features	WebUtil, Java beans, pluggable Java components (PJCs), OLE, host calls, custom colours or key mappings.	These have no direct browser equivalent and need a design decision each.
Batch jobs and schedules	Jobs that run forms or reports unattended, timing, who is told when they fail.	Easily forgotten, and the business notices only when a job stops.
Security and roles	Roles, who can open which form, how users log in, row-level rules.	The access model must be rebuilt and tested, not assumed.
Users	Number of named users, concurrent peaks, locations.	Drives rollout, training and performance testing.
Data volumes	Largest tables, growth, archival rules.	Large tables change how screens and reports must be designed and tested.
Report output formats	PDF layouts, Excel exports, pre-printed stationery, barcodes, bursting.	Printed output is often the part users compare line by line.

Keep the inventory in one place. The spreadsheet template below has these items ready as sheets.

Part B: How to Choose a Migration Partner

Criteria you can check, in the order most buyers find useful.

Verifiable references, with permission to call them. Ask for Forms-to-APEX projects of similar size, and speak to the client yourself.
A sample complexity assessment on 2-3 of your real forms, before any contract. Pick one simple, one typical and one difficult form. The vendor should show what they would rebuild and what they would ask you.
How business logic is treated. A sound approach finds the rules and moves PL/SQL into database packages first, so the logic is separate from the screens.
APEX and PL/SQL depth, with named leads. Ask who will actually do the work, their APEX and PL/SQL experience, and whether they stay on the project.
How parity is tested. Side-by-side tests of old and new, agreed test data, and a business sign-off per module.
Handling of Reports, PDF and printing. Ask how each report type will be rebuilt and how output is compared with the original.
Security and access model. How roles, logins and row-level rules are carried over and tested.
Project governance and change control. Who reports progress, how often, and how a change request is raised and decided.
What happens after go-live. Support arrangements, bug fixing for defects found after release, and who answers when something breaks.
Fixed scope or time-and-materials. Ask how each is defined and how scope changes are priced. Agree this in writing before work starts.
Exit, hand-over and code ownership. You should own the code and receive documentation so another team can take over.

Questions to ask any vendor (including ROSTAN)

Can we speak to two clients who had a similar Forms estate rebuilt in APEX?
Will you assess two or three of our real forms before we sign anything, and what will we receive from it?
Which parts of our logic would you move into database packages first, and how would you find them?
Who are the named people doing the work, and what is their APEX and PL/SQL experience?
How will you prove the new screens give the same results as the old forms?
How will you rebuild our Oracle Reports and printed output?
How are roles and access carried over and tested?
How are changes to scope raised, priced and approved?
What support do we get after go-live, and for how long is it included?
What documentation and code do we own at the end?

Red flags

Promises of full automatic conversion with no manual rebuild.
No sample assessment of your real forms before a commitment is asked for.
No reference customers, or references you are not allowed to call.
An estimate given without seeing any of your code.
No named team members or APEX and PL/SQL experience on show.
No plan for testing that old and new behave the same.
Reports and printing treated as an afterthought.
Vague answers on who owns the code and what is handed over.

Part C: Rebuild or Lift? Your Options

Oracle retired the APEX Migration Project feature (the Forms conversion tooling) as of APEX 21.1, so Forms screens are rebuilt in APEX rather than auto-converted. Oracle’s own FAQ recommends rebuilding. The current APEX release is 26.1, and Oracle’s solution playbook notes that stored procedures and PL/SQL packages work natively in APEX, which is why logic held in the database is reused.

Keep Forms for now

Fits when the application is stable, the Forms and database versions are supported in your setup, and the business has no pressing change request. Use the time to complete the inventory and move logic into database packages.

Rebuild Forms screens in APEX

Fits when you want a browser application, are changing the process anyway, and the logic is (or can be) in the database. Screens are rebuilt in APEX, not converted.

Hybrid: APEX alongside Forms

Fits large estates. New and most-changed modules go to APEX while the rest stay in Forms against the same database, and retire later in stages.

Redesign

Fits when the process itself no longer matches the business. Rebuilding the old screen one-for-one would copy the problem, so the work starts from what users need now.

Sources: Oracle APEX blog, FAQ about Oracle Forms to APEX modernization; Oracle solution playbook, move Oracle Forms applications to Oracle APEX; Oracle APEX 26.1 release notes (read 14 Nov 2026).

Download the Forms Inventory Template

A spreadsheet with Forms, Reports, Libraries, Integrations and Summary sheets. The checklist above is complete without it. Enter your name and email and the download link appears on this page.

What ROSTAN Does

Our APEX migration work, described plainly.

Assessment

We review your inventory and a sample of real forms, and tell you what we would rebuild and what we would ask you.

Rebuild in APEX

Screens are rebuilt in Oracle APEX, with business logic moved into the database where that makes sense.

Testing

Old and new are compared on agreed test data, with sign-off from your business owner.

Support

Ongoing help after go-live, including Oracle DBA support.

Ask for a sample assessment of two or three of your forms, with no commitment. See APEX application migration and Oracle APEX development.

Book a meeting Ask for a sample assessment

Oracle Forms to APEX Migration Checklist: How to Choose a Partner and Inventory Your Forms

Part A: Inventory Your Oracle Forms Estate

Part B: How to Choose a Migration Partner

Questions to ask any vendor (including ROSTAN)

Red flags

Part C: Rebuild or Lift? Your Options

Keep Forms for now

Rebuild Forms screens in APEX

Hybrid: APEX alongside Forms

Redesign

Download the Forms Inventory Template

What ROSTAN Does

Assessment

Rebuild in APEX

Testing

Support

Oracle Forms to APEX: Frequently Asked Questions

Get a Free Consultation

Let's Connects

Startup Support Program

Rostan Assistant

Oracle Forms to APEX Migration Checklist: How to Choose a Partner and Inventory Your Forms

Part A: Inventory Your Oracle Forms Estate

Part B: How to Choose a Migration Partner

Questions to ask any vendor (including ROSTAN)

Red flags

Part C: Rebuild or Lift? Your Options

Keep Forms for now

Rebuild Forms screens in APEX

Hybrid: APEX alongside Forms

Redesign

Download the Forms Inventory Template

What ROSTAN Does

Assessment

Rebuild in APEX

Testing

Support

Oracle Forms to APEX: Frequently Asked Questions

Get a Free Consultation

Let's Connects

Wait! Before you go…