Custom Fields
Custom Fields let you extend Leads, Deals, Contacts, Companies, and Products with fields that fit how your team actually sells β deal probability, decision timeline, account tier, anything you need to track that isn't covered by the standard fields.
Custom Fields are configured under Settings β Custom Fields, on five sub-tabs β one per entity.
Supported field types
Ten types are available. The right type makes filtering, exporting, and reporting much easier later, so pick deliberately.
Type | Use for |
|---|---|
Short text | Up to 255 characters. Names, codes, one-line notes. |
Paragraph | Multi-line free text. Pain points, meeting notes, descriptions. |
Dropdown | Single choice from a fixed list of options you define. |
Multi-select | Multiple choices from a fixed list. |
Labels | Free-form multi-select tags. You can pre-fill suggested labels users can choose from. |
Number | Numeric values. Budget, employee count, score. |
Date | Date only. Decision timeline, renewal date, launch date. |
Timestamp | Date and time. For events tied to a specific moment. |
People | User picker. Champion, technical owner, executive sponsor. |
URL | Web address with validation. LinkedIn, vendor profile, internal wiki link. |
Adding a custom field
Go to Settings β Custom Fields, pick the entity tab, and click + Add Custom Field.
Fill in:
Name β up to 255 characters. This is what users see on the entity's detail page, in filters, and in column headers.
Field type β pick one of the ten options above.
Description β optional, up to 4,000 characters. Helps your teammates understand what the field is for.
Some field types need a little extra setup:
Dropdown and Multi-select β add at least two options. Each option has a name up to 80 characters. Use + Add Option for each value, and the X next to a row to remove it.
Labels β you can optionally pre-fill Suggested labels. Users can still type any label they want; suggestions just appear in the autocomplete to keep teams aligned.
Click Create when you're done. The field appears immediately on every record of that entity, ready to be filled in.
Custom fields per entity
Each of the five core entities has its own set of custom fields, configured on its own sub-tab. There is no shared field across entities β if you want the same field to exist on Leads and Deals (for example, a Lead Score), you create it on both sub-tabs.
That said, when a Lead converts to a Deal, matching fields do carry over automatically. See Lead to Deal Conversion for the full rules and the cross-entity flow below.
Leads
Lead custom fields show up on the Leads list (as optional columns), in the filter panel, on the Lead detail page's More fields section, and in CSV exports. They're also available when bulk-importing Leads β see Leads Import.
Deals
Deal custom fields appear on the Deals list, in filters, on the Deal detail's More fields section, and in exports.
Contacts
Contact custom fields appear on the Contacts list, in filters, on the Contact detail's More fields section, and in exports. They're also available when bulk-importing Contacts β see Contacts Import.
Companies
Company custom fields appear on the Companies list, in filters, on the Company detail's More fields section, and in exports. They're also available when bulk-importing Companies β see Companies Import.
Products
Product custom fields appear on the Products list, in filters, on the Product detail page's More fields section, and in exports.
Lead β Deal conversion copy
When you convert a Lead to a Deal, Mria CRM automatically copies the value of any custom field that exists on both Leads and Deals with the same name and the same type.
For example, if you have a Lead Score Dropdown on Leads and a Lead Score Dropdown on Deals, the value carries over on conversion. If the names differ, or the types differ (one Dropdown, one Short text), the value will not copy β the system treats them as separate fields.
Want a value to follow a Lead through to its Deal? Create the field on both entities with the exact same name and type. A good convention is to define the Lead version first, then copy its setup over to the Deal tab.
Where custom fields appear
Once created, custom fields are usable across the CRM:
List views β click Customize table on the entity list to show or hide custom-field columns. The order of columns is saved per user.
Filters β custom fields appear in the filter panel under their entity. Dropdown/Multi-select/Labels filter as picklists; Number and Date filter as ranges.
Detail pages β the right-side More fields section lists every custom field for that entity. Click a value (or the "-" placeholder) to edit inline.
CSV exports β custom fields are included automatically when you export the list.
Bulk imports β Leads, Contacts, and Companies imports support mapping CSV/XLSX columns to custom fields. See Leads Import, Contacts Import, and Companies Import.
Reports (coming soon) β deal-based reports can pivot on Deal custom fields (e.g., breakdown by
Lead Score). Lead/Contact/Company custom fields are available in the relevant report builders.
Change log
Mria CRM keeps a running history of every custom-field change made on Leads and Deals β who edited which field, when, and what the value was before and after. Open a Lead or Deal's Timeline tab to review the change log alongside other activity.
Editing, reordering, deleting
Back on Settings β Custom Fields:
Rename a field by clicking its row and editing the Name. Existing data is preserved.
Reorder fields with the drag handle on the left of each row. The order shown here is the order custom fields appear on detail pages and in exports.
Edit options on a Dropdown or Multi-select β add, rename, or remove options. Removing an option clears it from any records currently using it.
Delete a field with the β¦ menu on the right of its row. Deletion is permanent and removes the value from every record β you'll be asked to confirm.
Deleting a custom field doesn't remove history of that field from the change log.
Tips
Keep field names short. They show up as column headers and in filter dropdowns β long names get truncated.
For values you'll filter or report on, prefer Dropdown over Short text. A controlled list keeps reports clean.
If you want a value to follow Leads as they convert to Deals, create a matching field on the Deal tab with the same name and type.
Use Labels when you want a flexible tag-style field (Bestseller, Strategic, Champion). Suggested labels keep usage consistent without locking the list down.
Use Description on each field to explain what it's for β especially helpful for newer team members reading reports six months later.