The Workflow Library

Library / Customer onboarding / customer-onboarding-021

Data migration or import request workflow

Customer onboardingDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A closed-won deal flagged as needing data migration automatically opens a tracked request for the delivery team, with the source system and volume details already attached, instead of relying on the rep to remember to email someone.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-021
flowchart TD
    A[Deal stage = Closed Won, Requires Data Migration = true] --> B[Create ticket in Data Migration pipeline]
    B --> C[Set ticket owner]
    C --> D[Send internal notification]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when some, not all, new customers need data imported from a prior system, and that need is known and flagged before or at close.
  • UseUse it when the delivery or implementation team works from tickets rather than a shared inbox or spreadsheet.
  • SkipDo not use it if every customer requires migration by default, in that case fold the migration steps directly into the standard onboarding checklist (customer-onboarding-003) instead of a conditional branch.
  • SkipDo not use it if migration requests need approval before starting, add an approval task ahead of ticket creation, see customer-onboarding-043 for the review-gate pattern.
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.3 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.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.