Names are not IDs.
Owners, pipelines and other referenced assets need to resolve in the destination. Portal reuse can remap IDs and references as part of that work.
For franchise & multi-location teams
Give every new location a better starting point. Understand the existing setup, build the shared operating model and adapt supported assets to the next portal’s owners, pipelines and references.
Property → pipeline → workflow
Next, separately Hill portal · its own mapping review
Find. Build. Adapt.
Review each portal’s wider audit findings. Investigate workflow health, dependency paths and evidence with the read-only workflow advisor before scoping the changes.
Explore auditsUse Projects to generate supported enquiry properties, pipelines, segments and follow-up workflows. Review the plan, approve generation and separately approve deployment.
Explore ProjectsBring supported assets into the next location’s portal. Follow dependencies, review destination matches and local references, then inspect per-asset results and warnings.
Explore portal reuseOne location or every location. Each portal’s mappings are reviewed before it deploys, and a deployment can be rolled back. It’s a reviewed copy, not live synchronization or automatic enforcement.
Consistency with context
A standard is a considered starting point. The destination portal determines how it is implemented.
Agree the purpose of the properties, the stages of the pipeline and the logic the workflow needs to support.
Build the source with ProjectsOwners, pipelines and other referenced assets need to resolve in the destination. Portal reuse can remap IDs and references as part of that work.
Match destination assets and review dependencies. A portal with an established setup is not an empty canvas.
Use the location’s requirements to scope the implementation. Do not treat a shared source as permission to overwrite differences.
Questions, answered
Yes. Portal reuse can deploy the same setup to multiple location portals, and you review each location’s matches and references before it deploys. Each location gets a reviewed copy, not live synchronization, and a deployment can be rolled back if a location needs it undone.
Destination references need to resolve to the assets and IDs in that location’s portal. Review the relevant owners, properties, pipelines and dependencies rather than assuming the source IDs will work unchanged.
Run a read-only Portal Audit for that portal and review the scored evidence. The report is an input to deciding what to change; it does not automatically repair differences or enforce a network-wide standard.
Scope the location requirements inside that portal. Projects can generate supported properties, pipelines, workflows and segments from the reviewed brief. Portal reuse is for supported assets between portals; it is not required just because several locations use one portal, and it does not create location-level access controls.
The next location
Walk through one location’s HubSpot requirements, the reusable core and the destination decisions that make it work.
Book a location walkthrough