Skip to content

Expansion deal associated to original deal for pipeline lineage

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: Sales Hub Professional.

Deal3 stepsUpdated for HubSpot seat pricing
OutcomeA new expansion deal is automatically linked back to the original deal that produced the account, so anyone opening either record can trace the full relationship history instead of piecing it together from memory.
Workflow maprenewal-expansion-038
Deal Type = Expansion, Original Deal ID known, not yet linked leads to Create association to original deal. Create association to original deal leads to Association succeeded?. Association succeeded? leads to Yes: Set Lineage Linked = true; No: Notify owner: check Original Deal ID. Yes No Deal Type = Expansion, Original Deal ID known, not yet linked Create association to original deal Association succeeded? Set Lineage Linked = true Notify owner: check Original Deal ID
Deal Type = Expansion, Original Deal ID known, not yet linked leads to Create association to original deal. Create association to original deal leads to Association succeeded?. Association succeeded? leads to Yes: Set Lineage Linked = true; No: Notify owner: check Original Deal ID. Yes No Deal Type = Expansion, Original Deal ID known, not yet linked Create association to original deal Association succeeded? Set Lineage Linked = true Notify owner: check Original Deal ID

When to use it, when not to

Use it

  • Use it whenever expansion, upsell, or cross-sell deals are created for an existing account and the team wants a direct record-to-record link back to the deal that first won the account, not just a shared company association.
  • Use it as a companion to renewal-expansion-033, which is a common source of a first "original deal" reference on a newly converted account.
Read more on when to use itShow less

Skip it

  • Do not use it if your reporting only ever needs the shared company association; a direct deal-to-deal link is worth building specifically when lineage needs to survive company merges or when several deals exist per company and a shared company link alone is not specific enough.
  • Do not use it if Original Deal ID is rarely populated in practice; an association workflow with mostly empty inputs adds workflow noise without much reporting value.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 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 · 3 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 · 2 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, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

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 Renewal and expansion 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