Skip to content
Book a build

Portal reuse

Your best setup.
A different portal.

Bring selected assets from a proven setup into the next client’s context. Match destination assets, review mappings and translate references for one destination portal or several, and roll back a deployment if you need to.

A setup, translated for its destination
Source portal

Aerolume

The setup you want to reuse

Match · map · review
Destination portal

Quillstone

The client’s existing context

Contact property

Region

region
01
Match a destination property

Choose the destination’s Territory property. Review its field type and allowed values before using the mapping.

Existing property

Territory

territory
Pipeline stage

Demo-to-close / Demo booked

pipeline 18 · stage 4
02
Review the stage mapping

The destination has its own pipeline and stage IDs. Select the stage that represents the same business handoff.

Destination IDs

Sales / Demo scheduled

pipeline 72 · stage 9
Owner reference

Source portal owner

owner 104
03
Select a destination owner

Owner IDs are portal-specific. Confirm who should receive the work in this destination instead of carrying over the source ID.

Reviewed assignment

Destination portal owner

owner 208
Dependent workflow

Regional handoff

Its destination references become:

  • Property territory
  • Stage 9
  • Owner 208
Review before
deployment
References change. Business intent still needs your review.One source → each destination reviewed

Portals are not interchangeable

Reuse the work. Reconsider the context.

A source workflow carries references, not just logic. Its property names, stages, owners and connected assets need to make sense in the destination.

Keep the starting point.
Review the assumptions.

A repeatable service setup or a connected group of assets can be a useful starting point. Import the supported assets and their dependencies into your library, then choose what belongs in the next implementation.

The destination may already have a similar property, a different pipeline or a new team. Mapping lets you work with those differences instead of treating the client’s portal as empty.

A destination review

Already present?
Inspect existing destination assets and possible matches.
Same meaning?
Review property types, options, stages and business intent.
Correct references?
Confirm destination mappings for the selected scope.
Ready to deploy?
Review the target, dependency order and any manual steps.

Inside the reuse engine

Reuse the relationships. Not just the asset.

A copied workflow is only useful when its connected assets and references make sense in the destination. Jetstack handles supported relationships as part of the implementation.

  1. 01 / Discover

    Follow the supported graph.

    Import dependencies recursively: a workflow can lead to an email, its template and related segments. Forms, lists, properties and pipeline stages have their own supported relationships—not one universal copy rule.

  2. 02 / Resolve

    Work with the destination.

    Use explicit mappings or per-type matches to reuse existing assets. Reconcile supported missing properties, enum options and pipeline stages; review the changes this can make to existing configuration.

  3. 03 / Rewrite

    Deploy references, not source assumptions.

    Deploy supported dependencies before their parents and rewrite supported IDs/references. Inspect per-asset results and warnings. Missing relationships, cycles or partial failures can require intervention before activation.

Source → library → destination

A deliberate path into the next portal.

  1. 01

    Select a coherent starting point.

    Choose the supported source assets you want to import. Review their dependencies so the reusable unit is a connected setup, not a collection of unrelated pieces.

    Selecting source assets →
  2. 02

    Resolve the destination’s differences.

    Choose one target. Inspect matches, map the references that differ and resolve the items that need human input. An owner or pipeline ID from the source is not a destination choice.

    Mapping destination owners →
  3. 03

    Review, deploy and inspect the result.

    Check the selected assets, dependencies, mappings and destination before starting the deployment. Follow its activity details and investigate failures or remaining manual work.

    Reading deployment activity →

A useful boundary

One portal or many.
Each one reviewed.

Deploy to one destination or several at once. Each destination still has its own existing setup, permissions and supported asset types, so its mappings are reviewed on their own terms. If a deployment needs undoing, roll it back: Jetstack previews what will be removed, then deletes what that deployment created.

Mapping helps translate references; it does not establish that two clients have the same process. It also does not guarantee duplicate-free or error-free deployment. Check support and limitations before committing the scope.

The Jetstack advantage

Dependency-aware reuse. Beyond the copy.

Follow supported dependency chains. Map destination references. Make reuse part of your implementation platform.

All portal reuse comparisons →

Questions, answered

Before you reuse a setup.

Is this a full portal clone?

No. Portal reuse works with selected supported assets and their dependencies. It is not a promise to clone an entire portal, its CRM records, integrations or every HubSpot setting.

Does reuse deploy to multiple portals at once?

Yes. You can deploy the same setup to multiple destination portals. Each destination keeps its own assets, mappings, permissions and deployment context, and you review its mappings before it deploys.

Can I undo a deployment?

Yes. Roll the deployment back: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment.

What happens to source IDs and references?

Supported references are resolved against destination assets and remapped for deployment. Depending on the asset, this can include properties, pipeline stages, owners and related assets. Review missing or ambiguous mappings rather than assuming every source reference has an equivalent.

Can Jetstack use something that already exists in the destination?

Destination matching and mapping can connect supported references to existing assets. Review the match, naming and conflict choices before deployment. Reuse does not guarantee zero duplicates or that every asset can be updated in place.

What does dependency-aware reuse actually do?

Jetstack extracts supported relationships during import, follows connected assets recursively and deploys supported dependencies before their parents. Destination mappings and per-type matches determine where references point. Supported property options and pipeline stages can be reconciled, which may modify existing configuration. Cycles, unresolved references or partial failures can still need manual work; review warnings and test the destination.

Which assets can I reuse?

The supported set spans CRM structure, automation and content, with different import, mapping and deployment support by asset type. Check the supported-assets and known-limitations documentation for your intended setup. Some types need the Chrome extension.

Plan the next destination

Bring the setup you want to reuse.

Walk through the source assets, the destination’s differences and the mapping decisions that need your review.

Book a reuse walkthrough