Map Fields is part of the Opportunity Custom Fields layout editor in Evo. It is how you place and arrange fields from your Opportunity custom field bank onto a layout or subtab so staff see the right questions in the right order on each Opportunity.
Table of Contents
What Map Fields Does
Where to Find It
How Opportunity Layouts Work
Why Some Fields Look Grayed Out
Best Uses
Related Articles
What Map Fields Does
Opportunity custom fields are stored in a shared field bank for your business. Layouts decide which of those fields appear on Opportunities, how they are grouped, and in what order.
Map Fields opens the layout-building controls for the current tab or subtab so you can:
- Add structure such as sections, groups, spacers, and splitters
- Add field types such as text, dropdown, checkbox, toggle, date/time, formula, label, and URL
- Place existing Opportunity custom fields onto the canvas
- Arrange fields for how they appear on the Opportunity record
- Use Preview Mode to review the layout before saving
Note: Creating a field definition adds it to the bank. Mapping places that field on a specific layout or subtab.
If you already built a tab by dragging elements from the left palette onto the form designer, you were already designing the layout. Map Fields is the menu action that opens that mapping view for the selected tab — including the Opportunity record chrome around your custom content.
Where to Find It
1. Go to Settings / Components / Custom Fields.
2. Open Opportunity.
3. Select the Layout scope you want to edit:
- Global default — used by pipelines that do not have their own layout
- A specific pipeline — used only for Opportunities on that pipeline
4. Select the tab or subtab you want to work on.
5. Click the More Actions menu (ellipsis) for that tab, then click Map Fields.
The same menu also includes options to rename the tab, set it inactive, or delete it.
How Opportunity Layouts Work
Opportunity layouts support:
- Layout scope — global default or pipeline-specific
- Tabs and subtabs — for example Opportunity Details plus stage-style tabs such as Needs Analysis or Discovery Results
- Field reuse — the same field definition can appear on more than one pipeline layout
On a live Opportunity, custom fields configured for the layout appear in the Opportunity side panel and on the Custom Fields tab of the Opportunity details page.
Note: If a pipeline has no custom layout, Opportunities on that pipeline use the global default layout.
Why Some Fields Look Grayed Out
When you open Map Fields, the canvas often shows more than the custom questions you added from the left palette. You may also see built-in Opportunity areas such as:
- Opportunity Name and Estimated Value
- Company / Contact summary
- Owners & Origin (for example Origin, Stage)
- Metadata (for example Created, Modified, Tags, Expected Date, Team)
- Terminal Stage (for example Win/Loss Reason and Win/Loss Note)
Those areas can appear grayed out or labeled static because they are system Opportunity fields — they ship with Evo and are part of the Opportunity record chrome. They are not unused custom fields you forgot to set up, and you do not need to recreate Tags or Terminal Stage with the left-menu field types for them to exist on Opportunities.
Your pipeline setup is complete when your stage tabs (for example Needs Analysis/Consultation) contain the custom sections and fields you designed. Map Fields is useful when you want to place or rearrange custom fields relative to that Opportunity canvas — not because every grayed system field must be remapped by hand.
Best Uses
Use Map Fields when you want to:
- Build stage-style intake forms (for example consultation questions on a Needs Analysis tab)
- Keep a pipeline-specific set of fields without creating duplicate field definitions
- Group related questions together with sections and two-column layouts
- Put required discovery fields first and optional notes later
- Make data entry clearer for sales staff working Opportunities day to day
Example: On a Projects pipeline, create subtabs that match your sales stages, then map only the fields needed at each stage onto that subtab.