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.
Aerolume
The setup you want to reuse
Quillstone
The client’s existing context
Region
region Match a destination property
Choose the destination’s Territory property. Review its field type and allowed values before using the mapping.
Territory
territory Demo-to-close / Demo booked
pipeline 18 · stage 4 Review the stage mapping
The destination has its own pipeline and stage IDs. Select the stage that represents the same business handoff.
Sales / Demo scheduled
pipeline 72 · stage 9 Source portal owner
owner 104 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.
Destination portal owner
owner 208 Regional handoff
Its destination references become:
- Property
territory - Stage
9 - Owner
208
deployment
The Jetstack advantage
Dependency-aware reuse. Beyond the copy.
Follow supported dependency chains. Map destination references. Make reuse part of your implementation platform.
Jetstack vs Supered
Supered moves a package. Jetstack follows every supported dependency, rewrites references for the new portal and builds what’s next.
Jetstack vs Datawarehouse.io
A migration suite with a beta workflow copier. Jetstack reuses HubSpot configuration with remapped references, matched assets and rollback.
Jetstack vs HubSpot Partner Portability
A beta copy wizard with six asset categories. Jetstack gives you a reusable library, destination mapping and the platform to build what’s next.
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.
Elsewhere in the platform