[object Object]

You’re staring at a Deals module with 140 fields, three sales motions, and reps complaining the page is unusable. The fix is one of three things — pick the right one.

Use Sections When the Same Process, Different Sub-Steps

If every deal goes through the same lifecycle but different stages need different fields visible, use Sections + conditional visibility. One layout, multiple section blocks that show or hide based on Stage. Reports stay simple, forecasts stay coherent.

Use Multi-Page Layouts When the Process Is Truly Different

Multi-page layouts are right when:

  • Different sales teams have non-overlapping fields (60%+ different).
  • Different products require different validation rules.
  • Different motions have different blueprints.

Each layout gets its own field set, its own blueprint, its own validation rules. Reports can still aggregate across layouts on shared core fields like Amount and Close_Date.

Use a Custom Module When the Object Is Different

If the only reason you’re considering a separate layout is “this isn’t really a Deal,” it’s a custom module. Renewals are not Deals. Subscriptions are not Deals. Bookings are not Deals. Forcing them into the Deals module corrupts pipeline reporting.

The Hidden Cost of Multi-Page

Each additional layout multiplies admin work:

3 layouts x 4 picklist field updates per quarter = 12 changes
+ 3 blueprint reviews = 15 things to coordinate

Don’t add a layout per region. Add a layout per fundamentally different process.

Layout Assignment Rules

Set assignment rules so reps don’t pick a layout from a dropdown. Drive it from a stable field — Product_Family or Sales_Motion — set on creation. Picklist-driven layout assignment is the cleanest pattern.

Migrating Existing Records to a New Layout

When you split an existing layout, write a one-time Deluge script to assign records to the new layout based on your criteria. The UI’s bulk reassignment misses records currently locked by blueprint, and you’ll spend a week tracking down which records weren’t migrated.

What to Do This Week

  1. Count your fields per module. Anything over 80 is a smell.
  2. Decide: same process (sections), different process (layout), different object (custom module).
  3. Wire layout assignment to a stable field, not user choice.
  4. If splitting an existing layout, write the migration script before going live.
[object Object]
Share