Outcome. Every closed-won deal gets a structured Onboarding Project record, associated to the deal, giving the team one dedicated object to track implementation details without overloading deal or ticket properties.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-038
flowchart TD
A[Deal stage = Closed Won, no project yet] --> B[Create Onboarding Project record]
B --> C[Copy deal amount and owner onto the new record]
C --> D[Associate record to deal]
D --> E[Set Onboarding Project Created on deal]
When to use it, when not to
- UseUse it when onboarding has enough of its own data (a target go-live date, an implementation type, a project owner distinct from the deal owner) that it deserves its own object instead of living as an ever-growing set of deal properties.
- UseUse it when several other onboarding fiches in this category (health score, milestone percent-complete) would benefit from a single project record to attach their properties to, instead of spreading them across deal and ticket.
- SkipDo not use it without Sales Hub Enterprise (or Service Hub or Data Hub Enterprise), custom objects and the workflow action to create them require an Enterprise-tier subscription (https://knowledge.hubspot.com/object-settings/create-custom-objects).
- SkipDo not use it if a ticket-based tracker (customer-onboarding-005 and customer-onboarding-011) already covers your needs at Professional tier, a custom object is more overhead for the same outcome unless you specifically need object-level reporting or a data model shared with a different Enterprise-tier tool.
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.8 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.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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.PDF, Markdown, JSON
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 customer onboarding 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.
