Choose a deal field type: 4 systems and storage rules

• Start by matching the field type to the specific data you must store and query.
• For HubSpot, each dropdown option has a maximum of 3,000 characters, including its label, value, and description, according to HubSpot. This enumeration limit applies to dropdown select, multiple checkboxes, and radio select properties. Do not confuse this with number-format rules; formatted numbers in HubSpot should not exceed 20 digits in length, according to HubSpot. These are distinct rules for different field types, not shared CRM limits.
• When selecting numeric types in Microsoft Dataverse, use decimals when you need to provide reports that require very accurate calculations, or if you typically use queries that look for values that are equal or not equal to another value, according to Microsoft. Microsoft also notes that up to 15 digits can be handled precisely in browser or app contexts, according to Microsoft. This precision guidance is specific to browser and app number handling, not a database precision limit.
• For percentage fields, HubSpot stores percentage property values as decimals, with 75% stored as .75, according to HubSpot. This storage method is specific to HubSpot and does not apply to all systems.
• Before adding a field, verify whether your team needs single-choice or multiple-choice options, as these require different property types. Also determine if the field will appear on both leads and deals, since Pipedrive shares field definitions across leads and deals.

When you create a custom property in HubSpot, the type of information you want the property to collect and store will determine the field type to select, according to HubSpot.

The decision starts with the specific data point you intend to track. You must identify whether the information is a fixed list of options, a continuous number, or a point in time. This initial classification dictates the structural rules the system applies to that column. If you select a text field for a qualification status, the system will not enforce a closed list of valid answers. If you select a number field for a status, the system will not accept alphabetic characters. The field type acts as a constraint on what can be entered and how that entry can be queried later.

Keep the scope of this decision narrow. You are choosing a data type for a single, new field. You are not redesigning your entire pipeline structure. You are not changing existing fields. You are adding one new column to your deal record. Focus on the specific storage and query needs of that one column. The rest of your pipeline structure remains unchanged. This focused approach reduces the risk of unintended side effects on your existing reports and workflows.

The table below lists the specific storage rules and type definitions for the four systems. Each row cites only the publisher’s documented limits for its own property types.

These rules are distinct to each publisher’s platform. HubSpot’s enumeration limits apply specifically to its dropdown select, multiple checkboxes, and radio select properties, not to all field types. Its number-format guidance separates formatted numbers from unformatted numbers, with different digit recommendations for each. Microsoft’s decimal and floating-point guidance addresses query behavior and calculation accuracy within its Dataverse environment, while its 15-digit precision note refers to browser and app handling rather than database storage. Pipedrive’s documentation explicitly states that leads and deals share the same custom fields, meaning a field created for deals appears on leads with identical properties. Close’s dropdown definitions explicitly name Lead records in their descriptions; these quotes do not confirm identical behavior for Opportunity custom fields or other record types. When selecting a type, match the storage rule to the specific data you plan to enter and the queries you intend to run. For example, if you need to filter by exact equality, Microsoft’s decimal guidance applies. If you need to compare ranges, its floating-point guidance applies. If you are adding a multi-select qualification field in HubSpot, each option has a maximum of 3,000 characters, and the maximum size of the property is 512,000 bytes, or 5,000 options, whichever is reached first. If you are adding a date field in Close, the distinction between a date-only field and a date-and-time field determines whether the time component is required. Verify the specific object type and field category in your system’s documentation before finalizing the choice, as these rules do not generalize across platforms or field categories.

Selecting the correct data type prevents data entry errors and ensures your team can filter records accurately. The distinction between single and multiple choice fields, as well as the difference between date and date-time fields, is critical for maintaining clean data.

According to Close, a Dropdown (single) is a dropdown of predefined choices where you can only select a single choice on a single Lead. This type is suitable for qualification fields where a deal has one definitive status, such as "Qualified" or "Disqualified." If your qualification process requires tracking multiple attributes simultaneously, such as "Technical Fit" and "Budget Confirmed," a single-choice field will not capture both.

See Open, won, and lost stage rules in 4 sales tools.

In contrast, a Dropdown (multiple) allows you to select one or more choices on a single Lead, according to Close. This type supports scenarios where a deal might have several qualification flags active at once. For example, a deal could be marked as both "Security Review Passed" and "Legal Review Pending." Using a multiple-choice field ensures that no qualification status is overwritten when another is added.

For time-based qualification data, the difference between a date and a date-and-time field matters. A Date field is a text field that only accepts a date, according to Close. This is appropriate for tracking when a qualification milestone was reached if the specific time of day is irrelevant to your forecast. For instance, if you track the date a security review was completed, a date field is sufficient.

However, if you need to track the precise moment a qualification event occurred, use a Date & Time field, which requires both a date and a time, according to Close. This is useful for logging when a demo was scheduled or when a contract was signed, especially if you analyze time-to-close metrics. Choosing the wrong type can lead to data loss or formatting errors when your team enters values.

See Close date change log: why the date moved.

Recommendation: Before adding the field, determine if your qualification process involves mutually exclusive states or multiple concurrent flags. If states are exclusive, use a single-choice dropdown. If flags can coexist, use a multiple-choice dropdown. For time tracking, ask if the time of day impacts your analysis; if not, use a date field to simplify data entry.

See Pipeline, Best Case, Commit: Forecast Categories Explained.

The Close dropdown quotes name a single Lead, while the Date and Date & Time quotes do not name an object. When designing fields for other objects or systems, verify the specific type definitions and constraints documented by that platform. The choice between these types directly affects how your team will filter and report on qualification data.

When a qualification field involves numbers, the choice between decimal and floating-point types depends on how you will query the data. In "Column data types in Microsoft Dataverse - Power Apps | Microsoft Learn," Microsoft advises using decimals when reports require very accurate calculations or when queries look for values that are equal or not equal to another value Microsoft. For data representing fractions or values typically queried by comparing to another value using greater than or less than operators, the same source recommends floating-point numbers Microsoft. Note that up to 15 digits can be handled precisely in browser or app number handling, which is distinct from database precision limits Microsoft.

In "Understand property field types in HubSpot," HubSpot specifies that for best results in reports, values should not exceed 38 total digits, 10 of which can be to the right of the decimal place HubSpot. This guidance applies specifically to Unformatted number properties. Regarding percentage fields, HubSpot states that percentage property values are stored as decimals; for example, 75% is stored as .75 HubSpot. Do not assume other systems store percentages identically. If your qualification field tracks a score or probability, verify how the specific platform stores that value to ensure your filters and reports retrieve the correct data.

Recommendation: Before adding a numeric qualification field in Microsoft Dataverse, use decimals for very accurate calculations or equal or not equal queries, and use floating point numbers for fractions or greater than or less than queries. Document the digit count your data needs for that field.

Before you finalize the data type for a new recurring qualification field, verify which record types will display that field. In Pipedrive, the system links custom fields across objects in a specific way. According to Pipedrive, "Leads use the same fields as deals." This means you cannot create a field that appears exclusively on deal records without it also appearing on lead records. The documentation states, "When a custom field is created for deals, the same field with the same name and properties will also be created for leads."

This shared scope affects your choice of data type. If you select a single-choice dropdown for a qualification stage that only applies to deals, that same dropdown will appear on leads. You must decide if the allowed values make sense for both record types. For example, a qualification field with values like "Budget Confirmed" or "Decision Maker Identified" may not be relevant to a lead that has not yet been converted to a deal. According to Pipedrive, to create a field successfully, you must at least name it and select its type.

Do not assume that other systems handle this scope identically. The quoted rule applies specifically to Pipedrive's custom fields feature. If your firm uses a different CRM, check its documentation for how custom fields propagate between leads and deals.

List 4 values and allow only 1 to be true, so use a single-choice field. Store a score from 0 to 10 that you test for equality with 8 as a decimal. Store the review day as a date when the hour does not matter.

Before creating the new qualification field, document its specific role in your deal record. According to HubSpot, the type of information you want the property to collect and store will determine the field type to select. Use this principle as your primary next action: for one proposed qualification field, write its purpose, allowed values, whether multiple choices are permitted and how the team will filter it.

Start by defining the purpose in one sentence. Is the field tracking a binary qualification status, a specific stage of validation, or a recurring metric? This definition prevents selecting a type that cannot hold the intended data structure. Next, list the allowed values. If the field is a dropdown, write out every option the sales team will select. If it is a text field, specify the expected format, such as a date string or a short note.

Once filled, choose the matching type from the reference table. This step aligns the field’s storage rules with your team’s daily workflow.

Should this field allow one choice or several?

Use a single-choice type when the status holds one value, and a multiple-choice type when it holds several. In HubSpot, each option in an enumeration property has a maximum of 3,000 characters, including its label, value, and description, according to HubSpot. Choose the type that matches your filtering needs before creating the field.

Should I use a date or a date-and-time field?

Use a date field when the time of day is irrelevant to the qualification. Use a date-and-time field when the specific hour and minute matter for reporting or sequencing. The choice depends on how your team will query the data later. If you only need to know when a qualification occurred, a date field is sufficient. If you need to order events within the same day, a date-and-time field is required.

How are percentage values stored?

In HubSpot, percentage property values are stored as decimals, for example, 75% is stored as .75, according to HubSpot. Check the specific documentation for your platform to confirm how decimal values are represented and displayed. This storage format affects how you write queries and build reports that filter by percentage thresholds.

When does numeric precision matter?

Precision matters when your reports require very accurate calculations or when you use queries that look for values equal to or not equal to another value. Microsoft advises using decimals in these scenarios, according to Microsoft. If your qualification score involves many decimal places or exact equality checks, choose a decimal type over a floating-point type.

Will a new deal field also appear on leads?

In Pipedrive, leads use the same fields as deals, according to Pipedrive. This means a custom field added to the deal record will also be available on lead records. Do not assume independent field definitions for leads and deals in this system. If you need different fields for leads and deals, Pipedrive does not support that separation for custom fields. Plan your field scope with this shared structure in mind.