Skip to main content
Treat migration workflows and future-state client workflows as two separate projects. Combining them can accidentally create client-facing activity during migration, or leave new clients without the intended experience after launch. See Intro to automations for the ways you can build and manage workflows.

​
Migration and backfill workflows

Use temporary tags, automations, or internal processes to organize imported records, assign existing information, and prepare current clients for launch. While backfilling:
  • Keep Client notifications muted.
  • Clearly name temporary automations so your team knows they are related to migration.
  • Document which automations or processes should be disabled once the backfill is complete.
  • Confirm that migration workflows do not trigger unintended client-facing actions.
Rename your automations as you create them, so you can tell at a glance which ones are meant to run on an ongoing basis and which existed only for initial setup.

​
Ongoing client workflows

Next, build the repeatable experience that should apply to clients joining after launch. Common triggers include a contact being created, a tag or status being added, or a client logging in for the first time. Depending on how your business uses Assembly, a workflow might:
  • Send a welcome message or surface a welcome resource.
  • Present the appropriate onboarding experience.
  • Collect information from the client.
  • Share relevant files, apps, or Help Desk resources.
  • Notify an internal account owner, or create an internal follow-up.
  • Display different resources or workflows based on a client’s service, segment, location, status, or owner.
These experiences can be created using Assembly’s apps, template apps, the app builder, or a combination of tools. Focus on the outcome the client and your team need rather than requiring every workflow to use a particular app.
Important: multiple automations or app experiences may run from the same trigger. This can create a polished first-login experience, but you should test the full sequence before using it with real clients.