Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Mini Page Layout entry
How-to guide

Migrate Mini Page Layouts to Compact Layouts

Migration is a one-time pass per object. Plan a fresh field-set design rather than copying the Mini Page Layout directly.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 21, 2026

Migration is a one-time pass per object. Plan a fresh field-set design rather than copying the Mini Page Layout directly.

  1. Inventory existing Mini Page Layouts

    Setup, Object Manager, each object, Page Layouts, find the Mini Page Layout configuration. Document the field sets per record type.

  2. Identify the per-object Compact Layout

    Setup, Object Manager, the object, Compact Layouts. Open or create the layout.

  3. Pick the right field set for Lightning

    The Compact Layout drives Highlights Panel, mobile, search, and hover. Pick fields that work across all these surfaces, not just the hover popup.

  4. Assign per record type

    Use Compact Layout Record Type Assignments to map each record type to the appropriate Compact Layout.

  5. Verify in Lightning

    Switch to Lightning Experience. Verify the Highlights Panel, hover preview, and search results all show the expected fields.

  6. Skip Mini Page Layout updates going forward

    Once Lightning is the active UX, Mini Page Layout edits do nothing. Update Compact Layouts only.

Gotchas
  • Mini Page Layouts are Classic-only. They do nothing in Lightning Experience.
  • Compact Layout drives more surfaces than Mini Page Layout did. Picking the wrong field set affects mobile and search, not just hover.
  • Migration is a one-time pass per object. Plan a fresh design rather than copying field sets blindly.
  • Documentation drift is severe. Treat any Salesforce article older than 2018 referencing Mini Page Layouts as historical context.

See the full Mini Page Layout entry

Mini Page Layout includes the definition, worked example, deep dive, related terms, and a quiz.