> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/crm-v1-old/contacts/how-to-update-custom-fields-in-bulk.md).

# How to Update Custom Fields in Bulk ?

To update custom fields for your contacts in a bulk manner, follow these steps:

1. Navigate to your contacts list.
2. Click on the **three dots** menu at the top.
3. Choose **"Edit all"** to update fields for all contacts or **"Edit selected"** to update fields for specific contacts.
   * To update custom fields for contacts meeting specific criteria, first use the **filters option** to narrow down your contacts. After filtering, click on the **three dots** and select **"Edit filtered"**.
4. Update the required custom fields as desired.

**Please note** that bulk editing custom fields may take a few seconds to complete. Currently, updating custom fields for individual contacts via CSV import is not supported.

{% embed url="<https://www.youtube.com/watch?v=_HDS8UocOEY>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/crm-v1-old/contacts/how-to-update-custom-fields-in-bulk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.