---
title: "Custom fields | Floral"
description: "Eight typed custom field types across six entity types (companies, people, deals, tasks, briefings, summaries). Validation, archiving, and CSV import support."
canonical: https://floral.so/features/crm/custom-fields
---

# Custom fields | Floral

> Eight typed custom field types across six entity types (companies, people, deals, tasks, briefings, summaries). Validation, archiving, and CSV import support.

Source: https://floral.so/features/crm/custom-fields

[CRM add-onRead about Floral CRM add-on ](https://floral.so/features/crm)

# Your data shape, not someone else’s

Eight typed field types across six entity types. Filterable, importable, archivable. Add the columns your team actually needs without waiting on a release cycle - and remove them again when the experiment is over.

[Read about Floral CRM](https://floral.so/features/crm)[Let's meet](https://floral.so/book-a-demo)

The field editor

## Pick a type, name the field, ship

![Floral custom fields editor](https://floral.so/img/features/crm/custom-fields/settings-custom-fields.png)

### Text + multiline text

For names, descriptions, anything free-form. Optional min/max length validation.

### Number

Integer or decimal. Optional min/max bounds. Useful for headcount, ARR, contract length.

### Boolean

Yes/no toggles. Great for flags like "uses competitor" or "renewal at risk".

### Datetime

Date, time, or full datetime - pick the granularity per field. Anniversary tracking, deadline fields, custom dates.

### Single-select & multi-select

Curated value lists. Useful for industry, region, source, or any closed vocabulary.

### URL

Validated URL field. Links auto-render as clickable on detail pages.

How they behave

## The lifecycle, not just the schema

### Six entity types

Companies, people, deals, tasks, briefings, summaries. Independent schemas per entity.

### Filterable everywhere

Every list page lets you filter by custom field values. Build the slice of data you need.

### Archive, do not delete

Archived fields keep their data for reporting. Restore at any time. Hard-delete optional.

Related features

## Pairs well with

[CSV importMap your import columns directly into custom fields.Learn more ](https://floral.so/features/crm/csv-import)[Bulk editingSet custom field values on many records at once.Learn more ](https://floral.so/features/crm/bulk-editing)[Companies & contactsWhere most workspaces start adding custom fields.Learn more ](https://floral.so/features/crm/companies-and-contacts)

[All CRM add-on features](https://floral.so/features/crm)[All core features](https://floral.so/features)

## Frequently asked

Which field types are supported?

Eight: text, multiline text, URL, number, boolean, datetime (with optional date-only / time-only granularity), single-select, multi-select. Validation rules - required, min/max - are configurable per field.

Which entities can have custom fields?

Companies, people, deals, tasks, briefings, and summaries. Each entity has its own field set; the meeting layer can have different fields than the CRM layer.

What if I no longer need a field?

Archive it. Archived fields keep their data - useful for reporting on historical state - but disappear from forms and filters. Hard-delete an archived field if you want to remove the data permanently.

Can I import data into custom fields?

Yes. CSV import maps to custom fields in the column mapping step. If a column does not match any field, it falls into the entity’s metadata bag - visible but not validated.

How many custom fields can I have?

Soft limit of 50 active definitions per (workspace, entity type). Generous for most teams; if you need more, archive the ones you no longer use first.

## Model your data the way you actually work

Add five custom fields in five minutes. Iterate without an engineering ticket.

[Sign up](https://floral.so/signup)[Let's meet](https://floral.so/book-a-demo)