A manufacturing client we worked with last year had 150 Oracle Forms modules and exactly two developers who could safely modify them. One was 58. The other was 62. They’d been maintaining the same codebase for 18 years. Nobody else in the organization could read the PL/SQL triggers or explain why the invoice validation behaved the way it did.
Then the 62-year-old took a consulting offer that paid double. The company suddenly had a mission-critical system nobody could touch.
Why the replacements aren’t there
The Oracle Forms talent pipeline dried up over a decade ago. Universities stopped teaching it. New developers have no interest in a desktop framework from the 1990s. The specialists still active in the market know exactly what they’re worth and price accordingly.
We ran a hiring experiment in 2025. We posted an Oracle Forms developer role at $140K in New York. Three applications arrived in six weeks. One was qualified. A TypeScript role at the same salary collected over 200 applications in the first week.
The pipeline isn’t shrinking. It’s gone.
The knowledge isn’t in the code
The retiring developer’s value isn’t the code they wrote. It’s the context they hold. They know module 17 has a workaround for an Oracle 9i quirk introduced in 2007. They know the fiscal year calculation has a special case for the Australian subsidiary. They know that changing the customer-form sequence breaks the downstream commission report in a way that won’t surface for two weeks.
None of this is documented. It never was. When that person walks out, the context walks with them.
What to do before the crisis
The answer isn’t another Oracle Forms hire. It’s extracting the knowledge from the system itself before the human carrier leaves the building.
Automated analysis can parse every .fmb file and produce a complete inventory: every trigger, every validation, every dependency, every business rule. That inventory becomes the documentation that should have existed for the past 20 years. From there, the codebase converts into modern TypeScript that any standard developer can read, extend, and maintain. The bus factor goes from 2 to “anyone on the team.”
The uncomfortable framing
If the lead Oracle Forms developer is over 55, the modernization project isn’t a technology initiative. It’s a business continuity risk that belongs in the same category as cyber insurance and data backup. Every month of delay makes the extraction harder, because the one person who can explain the edge cases is one month closer to leaving.
The good news is that the extraction itself is now mechanical. The bad news is that it only works while the human context is still available to verify the output.