The migration redesigns the right-side panel from scratch. Plan a Lightning Service Console rollout that takes advantage of the component model rather than porting the Classic configuration.
- Inventory current Mini View configuration
Setup, Object Manager, each object in the Console, Page Layouts, Mini Page Layout. Document the field sets per object.
- Design the Lightning Service Console
Plan the layout: Highlights Panel content, related-record components, custom Lightning Web Components for specialized agent needs.
- Configure Compact Layouts
Setup, Object Manager, each Console object, Compact Layouts. Pick the field set that drives the Highlights Panel and related Lightning surfaces.
- Build the Lightning Record Pages
Use Lightning App Builder to assemble the Console layout: drop components into the right regions, configure properties, save.
- Activate the Lightning Service Console
Make Lightning Experience the default UX. Train agents on the new layout; expect a brief productivity dip during the transition.
- Retire Mini Page Layouts
Once Lightning is active, Mini Page Layout edits do nothing. Stop maintaining them; remove from internal documentation.
- Mini Views are Classic-only. They do nothing in Lightning Service Console.
- The Lightning architecture is more flexible but also more configuration. Plan a fresh design rather than direct migration.
- Agent training matters. The Lightning layout differs enough from Classic that veteran agents need a few weeks to adjust.
- Documentation drift is severe. Treat any Salesforce article older than 2018 referencing Mini Views as historical context.