On this page
A workflow is not self-contained. Its filters can reference properties and lists; its actions can reference emails, owners, pipelines and other configuration. Copying its visible outline without resolving those relationships can leave something that looks familiar but behaves differently.
Start by defining the configuration you want to reuse, why it belongs in the destination and who can approve the local decisions. Jetstack AI’s Portal reuse workflow supports importing assets, inspecting dependencies and deploying into a destination with reference remapping and matching. Deploy to one destination portal or several, and review each destination’s mappings on their own. A deployment can be rolled back if it needs undoing. It is not a promise of identical results across arbitrary portals or a bulk synchronisation service.
1. Separate configuration from business data
List the assets in scope and distinguish them from CRM records, activity history, subscriptions and operational state. Moving a workflow definition is not moving its enrollment history. Copying a form is not a statement that submissions, consent or every connected integration will move with it.
Check the known limitations and supported import/deploy path before committing to the scope. Availability varies with asset type, HubSpot plan, permissions and access method. Where a browser-mediated path is required, follow the documented connection and portal requirements rather than assuming an OAuth connection covers every operation.
2. Follow the source dependencies
Import from the connected source and inspect what was captured. Source import is read-only; destination deployment is the operation that changes configuration. Record the source portal, capture context and intended baseline. If the source changes after capture, decide whether to refresh the import before proceeding.
Read the dependency tree as a reviewer, even when the tool discovers relationships. A selected workflow may pull in assets that have their own business owners. Confirm those assets belong in the approved scope and do not carry old location names, obsolete policy or environment-specific values.
3. Build a destination mapping
Open the destination inventory before choosing “create” or “reuse.” Compare internal definitions and intended semantics, not just display labels. A property named region in both portals may use different object types or option values. A pipeline stage called “Qualified” may mean something different to another team.
This illustrative mapping ledger uses invented names and IDs. It is not a customer receipt:
| Source reference | Destination decision | Review needed |
|---|---|---|
Contact property service_region | Reuse destination property | Check type, internal values and business meaning |
Pipeline source-pipeline-A | Map to destination-pipeline-B | Map stages explicitly; do not reuse source stage IDs |
Owner source-owner-A | Choose a destination owner | Confirm local routing and access |
List source-list-A | Create or match after schema review | Inspect remapped filter references |
Workflow source-workflow-A | Deploy after prerequisites | Verify enrollment and action references |
Mappings are destination-specific. Do not carry one portal’s owner or stage IDs into the next portal. Matching reduces unnecessary duplication when an appropriate asset exists; it does not guarantee that duplicates or semantic mismatches are impossible.
4. Deploy prerequisites before consumers
The dependency order matters because consumers need the destination identifiers of their prerequisites. Conceptually, the sequence is property and pipeline definitions, dependent lists or forms, then the workflow that uses them. The exact order depends on the asset graph, not a universal checklist of types.
Source list → source property reference ↓ reviewed mappingDestination property → destination list → destination workflowReview property, pipeline and owner mapping decisions before deployment. If a required schema definition cannot be created or matched, stop that branch of work. A dependent workflow should not be considered ready just because unrelated assets succeeded. Use the dependency documentation and property mapping guide for the product’s controls.
5. Inspect partial failures before retrying
Read the outcome for each asset. A missing permission, unsupported option or unavailable destination dependency can prevent completion. If the operation reports an ambiguous result, inspect the destination and the available execution record before sending the same creation again.
Keep the original source-to-destination mapping with the result. When a retry is appropriate, target the unresolved assets and their dependencies. Do not infer that a generic “complete” label establishes that every reference and every operational setting was validated.
6. Verify the destination in its own context
Inspect filters, pipeline stages, owner assignments and embedded references in the destination. Confirm that a workflow refers to the intended destination list rather than a missing source reference. Check publishing and activation states before allowing side effects. A configuration copy is not permission to start messaging contacts.
Run controlled behavioural checks authorised by the destination owner. Test a qualifying record and at least one exclusion or fallback case appropriate to the process. Record any manual follow-up such as integration configuration or domain-specific content review. Only then consider the next destination as a new deployment with its own mapping and acceptance.
Further reading
Read workflow dependencies for a closer look at connected assets. Use the multi-location guide when local exceptions are part of the design. Explore Portal reuse for the implementation workflow.
The implementation workflow
Resolve the references.
A destination-specific mapping and verification record.
Explore Portal reuse