Operations

Custom CRM Fields Settings

The Custom CRM Fields tab allows your organization to define additional structured data fields that persist alongside standard account data during CRM uploads and exports.

Use this section when your workflows or reporting require account attributes that are not included in the platform's default field set.

What Custom CRM Fields Are Used For

Custom CRM fields let you store extra information on accounts, such as institution-specific data, portfolio attributes, or business-defined metadata.

These fields are retained during CRM imports and exports, making them useful for organizations with custom data models or reporting requirements.

Managing Custom Fields

From the Custom CRM Fields section, administrators can:

  • add a new field

  • upload fields from CSV or Excel

  • edit an existing field

  • delete a field

  • review field metadata

Field Details

Displayed field details include:

  • Key - the internal identifier for the field

  • Label - the display name shown in the platform

  • Type - the data type of the field

  • Created Date - when the field was added

The platform also shows how many custom fields are currently in use.

Adding a Field

Use Add Field to create a new custom field directly in the platform.

This is useful when you need to introduce a new data point without changing your existing CRM upload process first.

Uploading CSV or Excel

Use Upload CSV/Excel when you want to add multiple fields from an external file.

This can be helpful during initial setup or when migrating a structured field list from another system.

Editing and Deleting Fields

Existing fields can be edited or removed from the fields table.

Editing is useful when you need to adjust naming or metadata. Deleting should be handled carefully, especially if the field is already being used in account imports, exports, or internal processes.

Before deleting a field, confirm it is not referenced in any active workflows, reports, or CRM integrations. Removing an in-use field may disrupt downstream processes.

Best Practices

  • Create only fields your team actively uses. Avoid cluttering your field list with unused or redundant attributes.

  • Keep field names clear and consistent. Use naming conventions that align with how your team refers to each data point.

  • Align keys and labels with your CRM naming standards. This reduces confusion during imports and exports.

  • Review field usage before deleting anything. Confirm the field is not referenced in workflows, reports, or external systems.

  • Avoid duplicating information already stored in standard account fields. Custom fields should extend your data model, not replicate what the platform already tracks.

Summary

The Custom CRM Fields tab helps organizations extend the platform's data model without overloading standard account fields. A clean custom field setup makes CRM uploads, exports, and downstream reporting easier to manage.

Was this helpful?