Skip down to the research record

Deal formula limits: 70 parentheses, 40 fields, 10 fields

Quota Forecast Editorial Team · Published · 10 min read

A calculated deal number runs only inside the formula limits the tool publishes, and HubSpot's nesting cap is 70 parentheses according to HubSpot.

Key takeaways

  • HubSpot allows up to 70 open parentheses in a calculation formula, so count your nesting before you trust the result.
  • Freshsales allows 40 formula fields in each module, while Pipedrive allows ten formula fields in each company account. These are separate limits.
  • In HubSpot, use the if and is_known functions to set an empty number property to 0.
  • In Pipedrive, an empty input makes the formula return a null value with the message not calculated.
  • Printed dollar and percent figures in vendor pages are examples, not your deal values.

Why published limits decide a calculated deal number

The specific ceiling for nested open parentheses in a calculation formula is 70, as documented by HubSpot. Their printed example, (((1+2)+3)+4), results in a nest count of 4 according to HubSpot. This specific ceiling belongs to HubSpot's calculation properties and does not apply to other tools. Keep the claim tied to this named source; do not generalize vendor behavior to every product.

PublisherLimit typePublished valueSource page
HubSpotParenthesis ceiling70 open parenthesesCreate calculation and rollup properties

Check one deal that shows a calculated number and verify whether every input the formula needs is filled before the weekly call. For other ways to do deal arithmetic, see Sales calculation tools: 4 options for deal arithmetic.

Nesting depth and field count limits

Before you rely on a number your CRM generated, check whether the formula structure and input fields fall within the specific ceilings documented by your platform.

Nesting depth limit. HubSpot allows you to nest up to 70 open parentheses within your calculation formula, according to HubSpot. For example, the string (((1+2)+3)+4) results in a nest count of 4, according to HubSpot. If your formula structure approaches this 70-parenthesis ceiling, verify that the nesting count stays within the limit.

Field count limits. Different platforms impose different limits on how many formula fields can exist on a single module or account. Freshsales allows you to create formula fields across all modules, but each module can have a limit of 40 formula fields, according to Freshsales. Pipedrive states that each company account can have up to ten formula fields, according to Pipedrive. These are distinct ceilings; do not treat the 40-field limit and the 10-field limit as the same constraint. Check which limit applies to your specific tool and module before adding new formula fields.

Illustrative example: counting formula fields against a limit

The numbers here are illustrative only. Suppose a tool publishes a limit of 40 formula fields in each module, and one module already holds 35. Subtracting 35 from 40 leaves room for 5 more fields. Adding a sixth would go past the published limit, so you would remove or combine a field first. The same counting habit works for nesting: the string (((1+2)+3)+4) has a nest count of 4, which leaves 66 of a 70-parenthesis ceiling.

A reference table of the formula rule by publisher

The table below lists the specific formula limits published by each vendor. Each row cites the source page where that limit appears, so you can verify the exact constraint before relying on a calculated deal number.

PublisherLimit typePublished valueSource page
HubSpotParenthesis nesting ceiling70 open parenthesesHubSpot
FreshsalesFormula field limit40 formula fields in each moduleFreshsales
PipedriveFormula field limitUp to ten formula fields in each company accountPipedrive
ClosePrinted expected value example$1,000 value x 75% confidence = $750 valueClose

Close documents that Expected Value is calculated by multiplying Value X Confidence, with a printed example of $1,000 value X 75% confidence = $750 value, according to Close.

Check your specific tool's documentation to confirm which limit applies to your current deal structure.

HubSpot's 70 parenthesis cap, 50 conditions, and 100 pairs

The "Create calculation and rollup properties" page documents the specific boundaries for calculation logic. HubSpot says you can configure up to 50 number and enumeration field type conditions for each rollup property, according to HubSpot. The same page states that you can add up to 100 total condition/value pairs, according to HubSpot. These pairs represent the combined limit for conditions and their associated values.

When building a formula that selects a value from multiple sources, the documentation notes that it returns the first non-empty value from 2 to 100 inputs, according to HubSpot. This range defines the minimum and maximum number of inputs the function accepts. The 70 parenthesis cap is a nesting limit that must be checked against these condition and input counts.

Check the number of conditions in your rollup property against the 50-condition ceiling. Verify that the total condition/value pairs do not exceed 100. Ensure that any function using multiple inputs stays within the 2 to 100 input range. These limits are specific to the calculation and rollup properties described on the HubSpot page. Do not apply these numbers to other tools or property types.

The limits for conditions, pairs, and inputs are distinct from the parenthesis nesting limit. Each must be checked independently.

What an empty input returns, and HubSpot's sample amount test

When a number property is empty inside a custom formula, the value can be set to 0 by including the if and is_known functions, according to HubSpot. This behavior applies specifically to number properties within that tool’s calculation and rollup properties. If you rely on a calculated deal number, verify that your formula explicitly handles empty states using these functions so the result does not remain undefined.

The documentation also provides a printed sample test: if([properties.amount] > 1000, "large", "small"), according to HubSpot. This example uses the $1,000 figure and the "large" and "small" labels as a demonstration of how conditional logic works in the formula builder. It is not a description of your specific deal amount, nor is it a target win rate or a standard discount tier. Do not interpret the $1,000 threshold in this example as a rule for your own pipeline; it is strictly a publisher’s printed example to illustrate syntax.

Check your own formula logic against these two points. First, confirm whether your formula uses is_known to catch empty number properties and return 0. Second, ensure you are not confusing the publisher’s sample figures with your actual deal data. If your formula references a specific dollar amount or percentage, verify that it comes from your deal record, not from a documentation example.

Freshsales' 40 field cap, Pipedrive's ten field cap, and the printed examples

The formula field limits differ by product and must be read against the specific page that publishes them. You can create formula fields across all modules ( Contact, Account, and Deal), but each module can have a limit of 40 formula fields, according to Freshsales. This ceiling applies to each module individually within the Freshsales environment. Each company account can have up to ten formula fields, according to Pipedrive. This ten-field ceiling applies to the company account level in Pipedrive.

Pipedrive's documentation includes printed examples that illustrate how these formulas calculate values. One printed activity formula is ( #Deal Done activities / #Deal total activities ) * 100, according to Pipedrive. This example demonstrates a calculation involving activity counts. Another printed percent example is #Deal value - 10% (subtracts 10% of the deal value), according to Pipedrive. This specific example shows a subtraction operation based on a percentage of the deal value.

A further printed commission example in Pipedrive's documentation states that the formula field called “Commission fee” uses only the deal value of $500 as an input, which is then multiplied by 5%, according to Pipedrive. As a result, the “Commission fee” returns $25, according to Pipedrive. The $500 deal value, 5% multiplier, and $25 result are Pipedrive's printed examples, not your specific deal amount, discount, or fee.

When reading a calculated number on a software deal, verify which publisher's limit applies to your tool. If you use Freshsales, check if your module has reached the 40 formula field limit. If you use Pipedrive, check if your company account has reached the ten formula field limit.

A formula check for one live deal

Use this worksheet to verify whether a specific deal's inputs allow a formula to run.

CheckAction
Deal contextConfirm the record is a deal, not a lead
Input statusVerify no required field is empty
Revenue entryCheck if estimated revenue is typed

Formula fields created using lead or deal custom fields only calculate values in deals, according to Pipedrive. If a field is empty, the formula will return a null value with the message not calculated, according to Pipedrive. If you're not yet ready to add products to the opportunity, you can specify the estimated revenue, according to Microsoft. Empty inputs are often a required-field problem, so also read Required-field rules in 4 tools before stage change.

Next step for today: open one deal that shows a calculated number and write down whether every input the formula needs is filled. No signup and no payment.

Deal formula FAQ

How deep can a HubSpot formula be nested?

You can nest up to 70 open parentheses within a calculation formula according to HubSpot. The documentation provides an example where (((1+2)+3)+4) results in a nest count of 4 according to HubSpot. This limit applies specifically to the calculation property structure described on that page.

How many formula fields can one module hold?

In Freshsales, each module can have a limit of 40 formula fields according to Freshsales. Formula fields can be created across all modules, including Contact, Account, and Deal according to Freshsales.

What happens when an input is empty?

In HubSpot, you can include the if and is_known functions to set the value to 0 when a number property is empty according to HubSpot. In Pipedrive, an empty field makes the formula return a null value with the message not calculated according to Pipedrive.

Are the sample dollars my discount?

No, the 1,000 figure in if([properties.amount] > 1000, "large", "small") is a printed example from HubSpot's documentation according to HubSpot. It does not represent your specific deal amount or discount. Similarly, any dollar figures in Pipedrive's examples are printed illustrations, not your actual transaction data according to Pipedrive.

What do I check before the call?

Verify that every input the formula needs is filled on the specific deal. Check if number properties are empty, as HubSpot allows setting these to 0 using if and is_known functions according to HubSpot. Confirm the formula does not exceed the 70 open parenthesis nesting limit according to HubSpot. Ensure the module has not exceeded the 40 formula field limit if using Freshsales according to Freshsales.

Sources