# Custom field cleanup in Pipedrive: group, hide, lock, and delete only when you mean it

https://salesbond.app/blog/pipedrive-custom-fields-cleanup-data-fields/
Published: 2026-10-03 · Updated: 2026-10-25

Clean up Pipedrive custom fields in order of risk: group the fields first, then hide them per pipeline, then restrict who can edit them, and delete a field only after you have taken its data out. The order matters because the first three steps are reversible and the last one is not. Pipedrive’s help center puts it in one sentence: “Deleting your custom field will delete the field and its existing data from your Pipedrive account” ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). Everything below is about getting to that step with nothing left to lose.

## Forty-one custom fields, and nobody knows which ones matter

Picture a wholesale coffee roaster with five reps on Pipedrive. Two pipelines: Wholesale accounts for cafés and restaurants, Office coffee for companies that want beans and a brewer on a monthly subscription. Three years of use. Forty-one custom deal fields.

On Thursday, September 24, 2026, the sales manager, Priya, opens a deal to prepare for a renewal call and scrolls past “Trade show 2024”, “Trade show 2025”, “Sample sent?”, “Sample sent date”, “Lead source (old)” and “Lead source” before she finds “Contract end”. Two of those fields were created by a rep who left in 2025. One was created twice because nobody could find the first one. Nobody can say which of the two lead source fields the Insights report is built on.

Nothing here is broken. The reps still close. But every new deal form shows all 41 fields, so reps fill the ones at the top and skip the rest, and every report built on a custom field starts with “wait, which field?”

The temptation is to delete everything that looks old. Don’t. There are three cheaper moves to make first, and each one is undoable.

![Four-step ladder of rising risk: group, hide per pipeline, read-only, and delete last, the only step with no undo; the first three are reversible](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-custom-fields-cleanup-data-fields-2.png)

## Group first: it costs nothing

Field groups change the layout of the detail view and nothing else. Pipedrive describes them as a way to “organize related custom fields into sections, helping you declutter your detail views and focus on the information that matters most” ( [Pipedrive: field groups](https://support.pipedrive.com/en/article/field-groups)). No data moves. No report changes.

We treat grouping as the step where you learn what you actually have: you cannot drag a field into a group without asking what it is for. In Priya’s case the first pass produced four groups for the Wholesale pipeline: Contract (start, end, payment terms, wholesale tier), Volume (monthly kilograms, price per kilogram, roast profile), Equipment on loan (grinder on loan, grinder serial, water filter) and History (both trade show fields, both sample fields). History is the honest name for “we are not sure yet.”

Two things from the help center worth knowing before you start. Grouping is “only available to global admins and regular users with the ‘Edit custom fields setup’ permission enabled”, so one person does this, not five. And “Empty groups are hidden in the detail view”, which means you can build the structure before you fill it ( [Pipedrive: field groups](https://support.pipedrive.com/en/article/field-groups)). Deals also come with a preset Summary group at the top of the deal view. Keep it to the three or four fields a manager reads on every call.

Where to do it: open the account menu in the top right corner, then Personal preferences > Data fields. Groups are created there, and fields are dragged into them. The next three steps happen on the same screen.

## Hide by pipeline, and what stays visible

Grouping made the 41 fields readable, not fewer. The next step is to stop showing fields where they never apply. For a deal field, the help center’s instruction is to open the field, “click on ‘All pipelines’ and deselect the pipelines where you want the field to be hidden” ( [Pipedrive: data fields in Pipedrive](https://support.pipedrive.com/en/article/data-fields-in-pipedrive)).

For the roaster this split is obvious once the groups exist. “Grinder on loan”, “Grinder serial” and “Water filter” belong to Wholesale accounts; an office subscription ships a brewer and no grinder. “Brewer model” and “Delivery day” belong to Office coffee. Eleven fields were only ever relevant to one of the two pipelines, so they got switched off in the other. A rep opening an Office coffee deal no longer sees a grinder field. For the office subscriptions, one choice comes before any new field: [pick recurring or installments first](https://salesbond.app/blog/pipedrive-recurring-products-vs-installments/), because Pipedrive calculates those figures itself.

The question everyone asks before flipping the switch: what happens to the data already in there? “If the field already contains some data, that data won’t be deleted, only hidden. It’s also visible in the list view, Insights and APIs” ( [Pipedrive: data fields in Pipedrive](https://support.pipedrive.com/en/article/data-fields-in-pipedrive)). So the report that averaged a hidden field last quarter still works, and an integration reading it through the API still gets a value. Only the detail view in that pipeline changes.

It also tells you what hiding is not for. A field that is wrong for both pipelines goes on the deletion list, not in the trash, for now.

Wondering whether the second pipeline should exist at all? That is [a different cleanup](https://salesbond.app/blog/pipedrive-multiple-pipelines/).

## Locking a field, and the five doors it leaves open

Some fields are not clutter. They are precious, and the problem is the opposite: too many people can change them. “Contract end” at the roaster had been edited by reps to make a renewal look less urgent. “Wholesale tier” sets the price list and had been bumped by hand twice. For fields like these, when creating or editing a custom field, “you can use the editing options to select which users can edit it based on permission sets” ( [Pipedrive: read-only fields](https://support.pipedrive.com/en/article/read-only-fields)).

We lock fields sparingly, two at the roaster, because a lock says the the data has an owner and a process, and most fields do not deserve a process. “Contract end” is changed only by the manager, from the signed renewal; “Wholesale tier” only by the manager, after finance confirms. Who should hold that pen is the subject of [who owns CRM data quality when you have no ops person](https://salesbond.app/blog/crm-data-ownership-small-sales-team/).

Now the part the help center is unusually direct about. Read-only restricts editing by users in the interface. It does not stop the other ways data gets into a field ( [Pipedrive: read-only fields](https://support.pipedrive.com/en/article/read-only-fields)):

- workflow automation that changes a read-only field
- webforms that allow end-user data into read-only fields
- conversion of data from leads into read-only fields
- data import into read-only fields
- editing on mobile devices

Five doors. The one that bites most teams is the first: if an automation sets “Wholesale tier” when a deal moves stage, it will keep doing so after you lock the field, and the manager will wonder who changed it. If a locked field is changing and nobody admits to it, check these five before you check your people.

One more exception: “Editing permissions can’t be applied to formula fields since solutions are calculated automatically.” You change the inputs, not the result. Here is [a formula field in practice](https://salesbond.app/blog/pipedrive-formula-fields-deal-margin/): deal margin.

## Delete: the one step with no undo

Everything so far can be reversed in a minute. Deletion cannot. The field and its data are gone, on every deal that ever had a value.

So our rule is simple: a field is deleted only after its values exist somewhere else. A hidden field still shows in the list view and through the API, so add it as a column to a list of deals and copy the values into a spreadsheet with the deal ID next to each, or pull them through the API. Only then open the Data fields page. “Trade show 2024” had 37 deals with a value. Nobody wanted the data but nobody wanted to be the person who lost it either, so it lives in a sheet now and the field is gone.

Three more points from the [custom fields help page](https://support.pipedrive.com/en/article/custom-fields). First, adding, editing and deleting custom fields “is only available for users with the correct global permissions enabled”, so, like grouping, this is one person’s job. Second, “The custom field type can’t be changed once it has been created.” If “Sample sent?” is a text field and you want a yes/no, the honest path is a new field of the right type, a copy of the old values, and then a deletion of the old one, in that order. Third, how many custom fields you can have depends on your plan, and dead fields take room from the ones you will need.

What qualified for deletion at the roaster, after everything else: “Lead source (old)”, once its values were copied into the surviving “Lead source” where the new one was empty; “Trade show 2024” and “Trade show 2025”, exported; a duplicate “Payment terms” with four values, all matching the original; and “Sample sent?”, replaced by a proper yes/no field and a date. Five fields out of 41. Most of the mess was a layout and visibility problem, not a deletion problem.

Still nervous about a deletion? Leave the field hidden for a quarter and come back. Nothing is lost by waiting. One field worth adding rather than deleting: a plain text field for the buyer’s own words about how they found you, kept [next to the system-filled source](https://salesbond.app/blog/self-reported-attribution-pipedrive/) and never overwritten by reps.

## A 20-minute custom field audit

All of the above compresses into one table with a row per field, filled once a quarter. The columns are the questions that decide a field’s fate.

| Field | Who fills it | Where it is used | Decision |
| --- | --- | --- | --- |
| Contract end | Manager, from signed renewal | Renewal filter, Insights | Keep, Summary group, read-only |
| Wholesale tier | Manager, after finance | Price list, automation on stage change | Keep, Contract group, read-only, check the automation |
| Grinder serial | Rep, at install | Nothing | Keep, Equipment group, hide in Office coffee |
| Delivery day | Rep, at close | Ops handover | Keep, hide in Wholesale accounts |
| Trade show 2024 | Nobody since 2024 | Nothing | Copy out, delete |
| Lead source (old) | Nobody since 2025 | One Insights report | Copy into Lead source, rebuild report, delete |
| Sample sent? | Rep, text field | Nothing | New yes/no field, copy, delete |

The third column is where the audit earns its time. “Where it is used” means filters, Insights reports, automations and integrations. A field nobody fills but a report still reads cannot be deleted without breaking teh report. Hunt for the report before you hunt for the field; we described how custom fields end up in averages in [custom field averages in Pipedrive Insights](https://salesbond.app/blog/pipedrive-insights-custom-field-averages/).

Pipedrive gives admins a head start on that column. Open a field and click “View field stats”: the help center says you will see “creation and update dates, along with stats showing where it is filled in or used in filters” ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). Reports and automations you still check by hand.

The tally for the roaster’s 41 fields: 12 stayed as they were, 11 moved into groups and nothing else, 11 were hidden in one of the two pipelines, 2 became read-only, and 5 were deleted after their values were copied out. The deletions took a second sitting, because the copying did. Everything else fit in the first twenty minutes.

The table does not decide which fields should be required; that is [a separate question](https://salesbond.app/blog/required-fields-pipedrive/). Nor does it replace [a full Pipedrive audit](https://salesbond.app/blog/pipedrive-audit/). Field cleanup is the part of that audit you can do on a Thursday afternoon with one admin and one spreadsheet. If the clutter came with a move from another CRM, start with the [fields that landed in the wrong place after a migration](https://salesbond.app/blog/migrate-to-pipedrive-data-audit/).

A note on where we stand. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Deal Health checks every deal against more than 20 rules, including a Data category, and explains what lowered each deal’s score. If you want to see what your deals look like after the cleanup, [check your CRM with SalesBond](https://salesbond.app/).

Then put a recurring task in your own calendar for the first week of January: open Data fields, count, and ask what grew.