The Workflow Library

Library / Renewal and expansion / renewal-expansion-049

Territory-based renewal deal reassignment on account transfer

Renewal and expansionDealSales Hub EnterpriseIntermediate~55 min to buildFull spec

Outcome. When an account is transferred to a new sales territory, every one of its open renewal deals moves to that territory's designated owner automatically, instead of a rep quietly keeping deals from an account that no longer belongs to their patch.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-049
flowchart TD
    A[Company Territory changes, open Renewal deals exist] --> B[Custom code: find open Renewal deals, look up new territory owner, reassign]
    B --> C{Succeeded?}
    C -->|Yes| D[Notify new owner]
    C -->|No| E[Notify sales ops: reassignment failed]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it once territory assignment already lives on a Territories custom object (as built by an example like sales-ops-022), with a designated owner per territory, and accounts transfer between territories periodically (a re-carve, a promotion, a restructuring).
  • UseUse it to keep renewal ownership consistent with territory ownership, without a manual sweep of every open deal each time a transfer happens.
  • SkipDo not use it if territory changes are rare and few enough that a manual reassignment is simpler than building and maintaining a custom coded action for it.
  • SkipDo not use it for accounts whose renewal deals should stay with the original rep for continuity reasons (a strategic account with a named relationship owner, for example); exclude those explicitly rather than letting a blanket territory rule override a deliberate ownership decision.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.5 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the renewal and expansion pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.