Custom Rollup Fields Not Populating for Existing Data

I created a new rollup field for Deals based on line items.

I can only get the value to populate when I manually add or re-add a line item to a deal.

Is there a way to force all rollup fields to populate on existing deals with line items?

You’re absolutely right — this is a known limitation with HubSpot’s custom rollup fields.

Currently, rollup fields only recalculate when a triggering event occurs, such as manually adding, removing, or editing a line item. Unfortunately, they don’t retroactively populate for existing deals unless there’s a change that causes the rollup logic to fire.

:white_check_mark: Workarounds:

  1. Manual Trigger: Manually remove and re-add a line item on each deal — not scalable, but works in small batches.

  2. Workflow Automation (If You Have Operations Hub Pro/Ent):

    • Create a custom workflow that updates a dummy field or property on the line item.
    • This forces a “change” and triggers the rollup field to recalculate.
  3. API Script (Developer Option):

    • Use the HubSpot API to loop through deals and update one of the line items slightly (e.g., a no-op update).
    • This simulates an edit and forces the rollup field to update.
  4. Support Ticket: Occasionally, HubSpot Support can trigger a background recalculation for you — worth reaching out if it’s a large dataset.


If you need help automating this or want to script it out using the HubSpot API, feel free to reach out — our team at Market Minds Creative has handled similar cases and can assist with a clean workaround.

Thank you! Makes total sense.

Hi @NMcMurray,

Can you share a screenshot of the roll up configuration? Generally, this sounds like a bug and I’d recommend flagging it with support in-app directly, via chat or email.

@SBrown62 please stop sharing gen AI content without a disclaimer.

Best regards

Hi Karsten,

Here’s the rollip field.

The field it’s rolling up is a Number field that is tied to a product.

@NMcMurray thank you - I don’t see why this wouldn’t behave as expected and would recommend to check with HubSpot support.