Oracle Forms and Oracle Reports were the standard for building enterprise database front-ends through the 1990s and 2000s. Complex, data-intensive applications — financial processing, HR systems, inventory management — were built on Forms. Migrating them is one of the most technically demanding legacy challenges an organisation can face.

The Oracle Forms problem

Oracle Forms applications are built around tight integration with Oracle Database. The Forms themselves contain PL/SQL triggers, business logic, and validation rules that aren’t visible in the database schema — they live in the form definition files.

The problems this creates:

• Oracle Forms is effectively end-of-life for new development
• The developers who built and maintained these systems are senior and retiring
• Business logic is distributed across database triggers, stored procedures, and form triggers — making it extremely difficult to understand the full system
• Oracle’s own migration path is complex and expensive
• The application may depend on versions of Oracle Database that are themselves approaching end-of-life

What I do

• Audit and documentation of Forms and Reports applications
• PL/SQL trigger and business logic extraction and documentation
• Database schema and stored procedure documentation
• Functional specification of each form — screens, validations, workflows
• Migration options analysis — Oracle APEX, web rebuild, commercial replacement
• Phased migration plan with realistic effort and risk assessment

What I need

• Access to the Forms/Reports source files (.fmb, .rdf)
• Database access or a schema export
• A list of forms and reports that are business-critical
• Context on the business processes the system supports

---