Cloning a Theme Onto a Second Brand's Site on One Shared HubSpot Portal
A single HubSpot portal syncs to only one Salesforce org, and the flagship brand's site already held that connection. A Change of Scope then funded a second, fully separate branded site for the company's other product line. Rather than build a second portal, we cloned the existing theme onto a new domain on the same one, giving the second site its own product listing, product detail, and resource templates.
Executive Summary
Context
An environmental and hydro-meteorological monitoring equipment manufacturer runs its flagship site on HubSpot Content Hub Enterprise, synced to a single Salesforce instance for lead routing. A Change of Scope added a full second website build for the company's other branded product line, sharing that one connection instead of a second.
What We Built
We cloned the flagship brand's HubSpot theme into a second, fully separate branded site on the same portal. The new site got its own mega menu and footer, product listing and detail templates, HubDB resource and technical-information tables, and blog and press templates, plus its own multi-language setup and technical SEO pass.
Tech Stack
- HubSpot Content Hub Enterprise
- HubDB
- Salesforce Sales Cloud
Not a fit if a second brand needs full portal-level independence: its own permissions, its own reporting, or its own Salesforce connection separate from the parent brand's. A shared portal keeps both brands on one Salesforce sync and one set of account-level settings.
The Challenge
The flagship brand's site already ran on HubSpot Content Hub Enterprise, synced to the company's single Salesforce Sales Cloud instance for lead routing. A Change of Scope then funded a full second website build for the company's other product line. We weighed standing up a dedicated HubSpot portal for it.
HubSpot's platform limit ruled that out. A single portal can't run two parallel Salesforce integrations, and the new brand's contacts still needed to reach the same Salesforce org. A dedicated portal would have meant a second Salesforce org or no working lead sync at all.
Our Approach
Our first option was a dedicated HubSpot portal, because it would have kept the new site's Salesforce sync and reporting separate from the flagship brand's. That ran into HubSpot's own limit: a single Salesforce org can carry only one active portal-level integration, and the second brand's contacts still needed to reach that same Salesforce Sales Cloud instance. The platform doesn't support building a second sync against that org from a second portal.
So we cloned the existing theme onto the same portal and gave the new site its own domain. The clone carried over the section library and theme architecture. We built the mega menu and footer, the product listing and detail templates, the HubDB resource and technical-information tables, and the blog and press templates new.
The new templates had to clear the same WCAG accessibility bar as the flagship brand's. The site also got a separate multi-language setup and a pre-launch technical SEO pass. The trade-off is that both brands share one portal's account-level settings and its single Salesforce connection.
Impact
A second brand ships without a second Salesforce integration
The new site's contacts reach the same Salesforce Sales Cloud instance the flagship brand already synced to, because one portal's single integration serves both sites. That let the company add a fully branded second site without building or maintaining a second Salesforce connection.
Its own templates, not the flagship brand's reused
The second site's product listing and detail pages, HubDB resource tables, and blog and press templates were built for it specifically, not pointed at the flagship brand's equivalents. A visitor to either site sees a distinct catalog, not a reskinned copy.
Two brands, two domains, one portal underneath
The second brand runs on its own domain with its own theme and navigation, so nothing in the visitor experience discloses the shared portal underneath. The two sites share account-level settings and the Salesforce connection, not their content.
Its own pre-launch QA and technical SEO pass
The second site went through its own quality assurance and technical SEO setup before launch rather than inheriting the flagship brand's sign-off. A defect or an SEO gap specific to the new brand's pages surfaced on its own checklist, not the other's.
The existing HubSpot theme's section library and architecture were copied onto a new domain for the second brand rather than a subfolder of the flagship brand's site, so the same building blocks render two distinct sites.
The second brand's own product listing and detail templates render its own product set, unconnected to the flagship brand's HubDB tables, so a change to one catalog carries no dependency on the other.
The second brand's blog and press pages render from their own templates, not the flagship brand's, keeping its editorial pages separate even though both sites publish from the same portal.
Contact records from both sites' forms reach Salesforce via the one integration the flagship brand's site already had configured, the single connection HubSpot allows per Salesforce org.
The flagship brand's site and the second brand's site, a clone of the same theme on its own domain, both run in one shared HubSpot portal. That portal carries the single Salesforce integration HubSpot allows per Salesforce org, so contacts from both sites reach Salesforce Sales Cloud through it. A dedicated portal for the second brand was considered and rejected, because a second portal can't run a second sync against the same org.
FAQ
HubSpot allows only one Salesforce integration per portal, and the new brand's contacts needed to reach the same Salesforce org the flagship brand already synced to. A second portal would have meant a second integration against that org, which the platform doesn't support, so we cloned the theme onto the existing portal instead.
Its own domain, product listing and detail templates, HubDB resource tables, and blog and press templates, plus a separate multi-language setup and technical SEO pass. Only the theme architecture and the Salesforce connection are shared.
