> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/docs/platform/extensibility/custom-fields/custom-fields-and-legacy-custom-fields/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Custom fields and legacy custom fields

> Depending on the object type and how custom fields are created, some custom fields on standard objects are recognized as legacy custom fields, while others are referred to as custom fields or advanced custom fields.

Depending on the object type and how custom fields are created, some custom fields on standard objects are recognized as legacy custom fields, while others are referred to as custom fields or advanced custom fields.

Zuora recommends using custom fields if possible because custom fields are more powerful and have fewer limitations than legacy custom fields.

## Standard objects that support both custom fields and legacy custom fields

The following standard objects support both custom fields and legacy custom fields:

* Account
* Credit Memo
* Debit Memo
* EInvoiceProfile (only if the E-Invoicing feature is enabled)
* Invoice
* Orders
* Order Actions
* Order Line Items
* Payment
* Product
* Product Rate Plan
* Product Rate Plan Charge
* Refund
* Subscription
* Subscription Rate Plan
* Subscription Rate Plan Charge
* Usage

For other standard objects, only legacy custom fields are supported.

## Comparison between custom fields and legacy custom fields

The following table describes the differences between custom fields and legacy custom fields.

<table>
  <tr>
    <th />

    <th>
      Custom field
    </th>

    <th>
      Legacy custom field
    </th>
  </tr>

  <tr>
    <td>
      Supported custom field types for an object
    </td>

    <td>
      * Text
      * Long Text
      * URL
      * Integer
      * Number
      * Boolean
      * Date
      * Datetime
      * Picklist
      * Multiselect

      Note that the Relationship custom field type applies only to custom objects.
    </td>

    <td>
      * Text
      * Integer
      * Number
      * Boolean
      * Date
      * Picklist
    </td>
  </tr>

  <tr>
    <td>
      The maximum number of total custom fields on an object
    </td>

    <td>
      Varies depending on your Zuora edition or Zuora modules:

      * Growth/Bronze: 50
      * Enterprise/Silver: 75
      * Nine/Gold: 100

      For more information, see Zuora Editions and Zuora Modules.
    </td>

    <td>
      50
    </td>
  </tr>

  <tr>
    <td>
      The maximum number of filterable custom fields on an object
    </td>

    <td>
      Varies depending on your Zuora edition or Zuora modules:

      * Growth/Bronze: 10
      * Enterprise/Silver: 15
      * Nine/Gold: 20

      For more information, see Zuora Editions and Zuora Modules.
    </td>

    <td>
      10
    </td>
  </tr>

  <tr>
    <td>
      Support self-serve conversion from indexed to non-indexed and vice versa?
    </td>

    <td>
      Yes
    </td>

    <td>
      No
    </td>
  </tr>

  <tr>
    <td>
      Support the **Unique** setting? (Enforce a unique value restriction on the custom field)
    </td>

    <td>
      Yes

      Applies only to custom fields on custom objects.
    </td>

    <td>
      No
    </td>
  </tr>

  <tr>
    <td>
      Support the **Auditable** setting? (Enable Audit Trail to record the changes of the custom field)
    </td>

    <td>
      Yes

      Applies only to custom fields on custom objects.
    </td>

    <td>
      No
    </td>
  </tr>

  <tr>
    <td>
      Support the **UI Read Only** setting? (Restrict the access to the custom field in the UI to read-only)
    </td>

    <td>
      No
    </td>

    <td>
      Yes
    </td>
  </tr>

  <tr>
    <td>
      Support for sharing with sub-entities?
    </td>

    <td>
      No
    </td>

    <td>
      Yes
    </td>
  </tr>

  <tr>
    <td>
      How to create?
    </td>

    <td>
      * Via the Object Manager

      If a standard object does not support advanced custom fields, you can define only legacy custom fields via the Object Manager.
    </td>

    <td>
      * Via the Object Manager (applies only to standard objects that do not support advanced custom fields)
      * On the Manage Custom Fields settings page
    </td>
  </tr>
</table>

> Depending on the object type and how custom fields are created, some custom fields on standard objects are recognized as legacy custom fields, while others are referred to as custom fields or advanced custom fields.

## Docs

- [Identify legacy custom fields on a standard object](https://zuora.ferndocs.com/docs/platform/extensibility/custom-fields/custom-fields-and-legacy-custom-fields/identify-legacy-custom-fields-on-a-standard-object.md): Learn how to distinct legacy custom fields from advanced custom fields on standard objects.