What setups for custom objects do we have to redo when we transition from classic Sales to the Redwood User Experience?

Most of the work involves recreating custom layouts. The Redwood UX is a completely new user experience, not just a new theme.

The layouts you created in Application Composer for classic Sales remain for use in the classic Sales pages, but you must create new layouts for the Redwood UX using CX Extension Generator and Oracle Visual Builder Studio.

The transition doesn't delete any data. All custom objects and fields, along with data interfaces, remain and are consumed in the Redwood UX.

All custom Groovy scripts remain in place and will run. Field validations triggers that run on tab out of a field in classic Sales, now run on the save operation, when data is sent from the browser to the server.

Email templates, which are mostly used in classic Sales workflows, continue to work as expected in Redwood. Sales in the Redwood UX includes some new features for interactive email authoring that don't exist in classic, so there are more options to use message templates in Sales flows.

For more information on recreating your layouts, see the How do I create an application extension for custom objects? playbook.