Oracle is retiring classic ADF pages in favor of Redwood across every Fusion Cloud pillar, on Oracle's release schedule, not yours. Doyensys assesses what breaks, migrates what matters, and rebuilds what's worth rebuilding, in Visual Builder Studio, so your teams open a page they already know how to use.
Every Fusion Cloud customer receives the same quarterly update, on Oracle's schedule. Redwood is not a theme you opt into and skip later, it is a different rendering technology, built on Visual Builder Studio and Oracle JET rather than the ADF framework your classic pages run on. The longer a customization sits untouched on the classic side, the more expensive it gets to carry forward.
Take something as ordinary as creating a sales order. The classic page puts every field in front of the user at once. Redwood shows what matters first and tucks the rest behind a drawer, and even closing the page moves from a visible Cancel button to a "More Actions" menu. Small differences individually, real retraining and re-testing at scale.
We've walked enough ADF-to-Redwood migrations to know exactly where the surprises hide. Here's what tends to bite teams who go in without a plan.
We've seen a five-row comments field reduce to one row after migration, and rules that reference fields no longer exposed in Redwood at all. Every rule needs a side-by-side compatibility check before go-live, not after.
Common business math, like a combined total from two amount fields on a Purchase Agreement, often isn't available out of the box in Redwood and has to be rebuilt as a custom field in Visual Builder Studio.
Lightweight ADF extensions for things like supplier onboarding don't have a direct Redwood equivalent. They need to be re-architected as standalone Redwood-themed pages, not patched.
We inventory every ADF personalization, Page Composer rule, and custom extension across your environment, and flag exactly what will and won't carry forward.
Using Oracle's export and helper-tooling path, we migrate compatible rules into Redwood, verify the result in a live environment, and document anything that had to be rebuilt by hand.
Missing calculated fields, custom pages, and lightweight standalone apps get rebuilt natively in Redwood using VB Studio, styled to match Oracle's own design system.
Once you're stable on Redwood, we layer in what it unlocks: AI agent-enabled guided journeys, natural-language assistance, and Oracle Analytics dashboards built on the same design language.
A practical look at what Redwood changes, where legacy ADF customizations run into trouble, and how to sequence a modernization so it doesn't collide with your next quarterly update. Written by the same team that runs these migrations.
Not theory. Field notes from Doyensys engineers who have done this work inside live Oracle Fusion Cloud environments.
Oracle applies Fusion Cloud updates quarterly to every customer, and it is steadily retiring classic ADF pages module by module in favor of Redwood. You can delay individual page transitions for a time, but the direction is set by Oracle's release calendar, not a preference you can opt out of indefinitely.
Some will, many need rework. Page Composer rules and layout personalizations have to be individually evaluated against Redwood's component model. In our experience, straightforward field-level rules usually migrate cleanly; anything touching layout, comment fields, or conditional visibility often needs manual review before it behaves the same way it did on classic.
No. Redwood is a page-rendering and extensibility layer. Your chart of accounts, ledgers, item masters, approval hierarchies, and REST/SOAP integrations are untouched. This is a UI and customization migration, not a re-implementation of your Oracle environment.
It depends on how many modules and personalizations are in scope, but most assessments are structured to deliver a clear inventory and risk map within a few weeks, fast enough to inform planning for your next quarterly update rather than react to it.
Not to start the assessment. If custom extensions are needed, VB Studio access is required, and if your organization doesn't already have it enabled, we can help you request it from your Fusion administrator as part of the engagement.
A Doyensys Redwood readiness assessment gives you a clear inventory of what migrates cleanly, what needs rework, and what to rebuild, with real timelines attached.