Skip to content

Quarter-end pipeline snapshot property set (amount and stage captured on a fixed date)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Deal4 stepsUpdated for HubSpot seat pricing
OutcomeOn a fixed schedule at the end of each quarter, every open deal gets its amount and stage frozen into snapshot properties, so quarter-over-quarter pipeline comparisons do not get overwritten by later edits to the live fields.
Workflow mapreporting-alerts-031
Scheduled trigger: quarter end, 18:00 leads to Enrollment: open deals across pipelines. Enrollment: open deals across pipelines leads to Set snapshot_amount_q_end = current amount. Set snapshot_amount_q_end = current amount leads to Set snapshot_stage_q_end = current stage. Set snapshot_stage_q_end = current stage leads to Set snapshot_date = today. Scheduled trigger: quarter end, 18:00 Enrollment: open deals across pipelines Set snapshot_amount_q_end = current amount Set snapshot_stage_q_end = current stage Set snapshot_date = today
Scheduled trigger: quarter end, 18:00 leads to Enrollment: open deals across pipelines. Enrollment: open deals across pipelines leads to Set snapshot_amount_q_end = current amount. Set snapshot_amount_q_end = current amount leads to Set snapshot_stage_q_end = current stage. Set snapshot_stage_q_end = current stage leads to Set snapshot_date = today. Scheduled trigger: quarter end, 18:00 Enrollment: open deals across pipelines Set snapshot_amount_q_end = current amount Set snapshot_stage_q_end = current stage Set snapshot_date = today

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use it when finance or RevOps needs a point-in-time pipeline value that survives later amount or stage changes on the same deal.
  • Use it to build a trend report of pipeline composition across quarters without exporting a manual snapshot each time.
Read more on when to use itShow less

Skip it

  • Do not use it if the portal already exports pipeline snapshots through a data warehouse or BI tool on a schedule. That is a cleaner source of truth than CRM properties for historical trend analysis.
  • Do not use it on a portal with only one pipeline stage in active use. A quarter-end freeze adds little when the field barely changes.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 5 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library