Calculated properties in HubSpot update themselves automatically by running a formula over data that already exists in your portal. When a deal amount changes or a date is logged, the calculated field recalculates on its own. No manual entry, no copy-paste between records.
This guide explains what calculated properties are and how to create them, with the most useful applications for Southeast Asian teams.
In your HubSpot portal, click the settings icon and navigate to Properties. Select the object type the property belongs to (Contact / Deal / Company / Ticket).
Click Create property. Name it clearly, then select Calculated from the field type dropdown. Choose the formula type from the dropdown (Number / Duration / Percent / Score). Each is described in the next section.
Use the formula builder to select source properties and define the calculation. For Number, pick properties and operators (+ – * /). For Duration, pick two date properties and choose the output unit (days, months).
Save the property. Open a contact or deal where the source properties have values and confirm the calculated field shows the expected result.
Calculated properties appear in record and list views, and can be added to any reporting dashboard. Pin it to the sidebar for quick visibility.
What Is a Calculated Property in HubSpot?
A calculated property is a custom CRM field that derives its value from a formula. It is available across all standard HubSpot object types. The formula references other numeric or date properties on the same record. HubSpot recalculates the value each time a source field changes.
For example: a “days since last enquiry” property subtracts the Last activity date from today. Or a “deal value in THB” field multiplies a USD deal amount by a fixed exchange rate. Both update automatically, with no workflow required.
What Types of Formulas Are Available?
HubSpot’s formula builder supports four property types:
- Number: arithmetic on numeric fields. Add, subtract, multiply, or divide. Useful for revenue calculations, ratios, or weighted scores.
- Duration: the difference between two date properties, expressed as a number of days. Useful for tracking time-in-stage, response time, or deal velocity.
- Percent: a ratio expressed as a percentage. Useful for win rates or completion scores.
- Score: a weighted sum of multiple numeric fields. Useful for custom lead or deal scoring where each input carries a different weight.
Formulas can reference multiple source properties and use parentheses to control the order of operations. The output is always a number or a duration; calculated properties cannot return text.
What Are the Most Useful Applications?
The cases where calculated properties save the most time are those where your team currently updates values manually or derives them in a spreadsheet.
- Deal velocity: how many days a deal has been open, calculated from Create date to today or to Close date.
- Time since last contact: a duration between Last contacted and today, useful for flagging leads going cold.
- Revenue in local currency: multiply a USD deal amount by a fixed rate. Useful for SEA teams working across THB, SGD, USD, or other currencies.
- Weighted pipeline score: combine deal amount with close probability into a single weighted number for prioritisation.
- Enrollment completion rate: for education teams, a percent property dividing completed intake steps by total required steps.
Are There Limitations to Know?
Calculated properties work reliably within their scope, but a few constraints matter in practice.
They can only reference properties on the same object. A calculated property on a deal cannot pull values from an associated contact. If you need cross-object calculations, a workflow action that copies or derives values manually is the alternative.
They cannot output text. If you need a property that labels a contact “high value” or “at risk” based on a number, you need a separate workflow that reads the calculated number and writes a text value to a different property.
Calculated properties are only available on paid HubSpot tiers. The exact tier requirement varies by object type, so check your current plan before building formulas you plan to rely on in production.
How Do Calculated Properties Work With Workflows?
A calculated property is a data layer, not an action layer. It derives a value and stores it. Workflows then act on that value.
A practical pattern: a “days in stage” Duration property calculates automatically. A workflow checks that property each day and creates an internal task when it exceeds a threshold. The calculated field handles the arithmetic; the workflow handles the follow-up. This separation keeps workflow logic simpler and easier to maintain.
Instead of date arithmetic inside a workflow, you reference one clean property. The condition reads: “days in stage is greater than 14” rather than a nested date calculation with multiple if/then branches.
How Does This Differ From HubSpot’s Native Score Property?
HubSpot has a separate Score type in the formula builder designed for weighting multiple numeric inputs. This differs from the native HubSpot Score property, which uses an activity-based point system with positive and negative criteria.
A calculated Score property suits situations where you want a formula: for example, giving revenue potential twice the weight of activity signals in a lead score. The native HubSpot Score suits situations where you want to add or subtract points based on specific actions like email opens or form submissions.
Both can coexist. Some teams run both: a calculated score for commercial weighting and a native HubSpot score for activity signals, then combine the outputs in a workflow decision branch.
Frequently Asked Questions
Can I use a calculated property in a list filter?
Yes. Calculated properties appear in list and workflow filters once they have values. Filter on number ranges or duration thresholds the same way as any numeric property.
Do calculated properties update in real time?
HubSpot recalculates when a source property value changes. The update is not always instant but typically resolves within minutes. Avoid using them as triggers for time-critical automation where immediate recalculation is essential.
Can I export calculated property values?
Yes. They appear as a standard column in any object export.
What happens if a source property has no value?
HubSpot treats blank source fields as zero in arithmetic formulas. This can produce misleading results on records with incomplete data. Use list filters to exclude records where the source property is unknown before reporting on calculated values.
How many calculated properties can I create?
HubSpot does not publish a specific cap. In practice the limit is the same as the custom property limit for each object type and varies by tier.
Calculated properties work best when you identify a value your team currently maintains manually and replace it with a formula. Start with one or two high-value cases. Verify the results against known records before expanding further.
For more on managing properties in HubSpot, see the HubSpot custom properties guide and the HubSpot data quality guide.
This resource is produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us