Cross-selling, shared services and group reporting all wait until the customer data sits in one place under one set of definitions. We consolidate multi-brand groups onto HubSpot as a HubSpot Gold Solutions Partner, and build the integration layer underneath.
Today
3 systems of truthBrand A
own CRM412 duplicates
Brand B
own CRM1,109 duplicates
Brand C
own CRM268 duplicates
Group report
Assembled by hand, monthly
One customer who buys from two brands is counted twice.
After consolidation
one system of truthOne customer record
One contact list, one set of definitions
brand = field on the record
Group report
From the system, any day of the month
Cross-brand revenue becomes something you can read, not reconstruct.
SHAPE 01
One company joins an existing platform. The question is whose processes win.
SHAPE 02
Several a year. The priority is a repeatable pattern, because bespoke each time does not scale.
SHAPE 03
The business has to leave the parent's systems by a deadline, often with no CRM of its own.
SHAPE 04
No single deal. Leadership wants comparable reporting across companies that grew up apart.
The shape differs. The decisions underneath are the same.
Phase it. But if you buy on a cadence the quiet moment never arrives, and every delay means absorbing several companies at once instead of one.
Settle three things now: one customer record, one agreed set of definitions, one reporting model.
The customer record, before anyone's workflow. And the first argument is about words, not software. One company says lead, another says account. One counts a deal at proposal, another at signature.
Until those definitions are agreed, every report built on them is wrong and nobody notices for a quarter.
Standardize what has to be compared across the group, leave alone what makes each brand work. One customer record and one reporting model for everyone, while campaigns, sales stages and routing stay each brand's own.
You bought those brands for their markets. They usually have habits worth keeping.
Keep the brands inside one system. Separate portals rebuild the silos you just paid to remove, and merging everything into one list erases the distinctions the business runs on.
The middle path: brand becomes a field on a shared record, with its own pipelines and permissions on top.
A form on one brand's site is often asking for another brand's service. Attribution should stay with the site that earned the enquiry while the record routes to the company that will deliver it.
Two different questions, two different fields. Collapsing them is how cross-sell goes invisible.
Connect, do not replace. The ERP keeps products, pricing, quotes and orders. HubSpot owns engagement: contacts, companies, pipeline, campaigns and service.
Move history across too. If people cannot find last year's data in the new system, they quietly keep the old one running.
All six hubs, and the integration work underneath. The part in the middle, between HubSpot and the systems that already run the business, is usually where the program is won or lost.
Shared contact and company model with deduplication resolved before go-live, brand as a field rather than a separate portal, and lifecycle stages that let a customer be existing for one brand and new for another.
Custom objects · Business units · Teams & permissions
Lead, account, qualified opportunity, quote, deal. Written down, agreed across companies, and encoded in the portal, with a named owner for each process that now crosses a company boundary.
Process maps · Glossary · Lifecycle & pipeline design
Form source drives attribution, service interest drives allocation. Enquiries arriving on one brand's site route to the company that delivers the work without losing where they came from.
Workflows · Form migration · Routing rules
Custom integration between HubSpot and the systems of record, built so the system underneath can be swapped without rebuilding the CRM. Off-the-shelf connectors handle the easy cases; the ones that matter rarely are.
Operations Hub · Custom middleware · ERP & commerce APIs
Nurture, win-back and dormant programs moved off per-brand marketing tools onto one platform, plus ticketing and conversations, company by company rather than all at once.
Marketing Hub · Service Hub · Migration scripts
Group roll-up and per-company views that come out of the system itself, so leadership stops quoting a summary assembled by hand.
Dashboards · Forecasting · Attribution reporting
FIRST
What counts as a lead, an account and a qualified opportunity, and who owns each process now that it spans more than one company.
THEN
Contacts, companies, pipeline and the brand model, with duplicates resolved first. Sales foundation before marketing automation.
THEN
Marketing, forms and support migrated company by company. The ERP connected through governed middleware, not replaced.
THROUGHOUT
Every team watches its own process run before go-live. Training happens during testing, not afterwards.
The part most plans underestimate is not the software. It is the worry that a familiar way of working is about to get worse. That gap closes when a team watches its own process run, which is why testing and enablement happen together rather than in sequence.
What goes wrong
Nothing destroys trust in the numbers faster. Deduplication is a first-phase task, not a cleanup ticket.
What goes wrong
Anything that crosses a company boundary needs a named owner before it is automated.
What goes wrong
Teams who have already survived one CRM project are not being difficult. They are protecting themselves, and they usually have reason to.
FIRST 30 DAYS
All pipeline sits in one system. The side spreadsheets stop.
BY 90 DAYS
Leads route correctly between companies. Leadership quotes the CRM, not a hand-assembled summary.
BY 6 MONTHS
Marketing runs on one platform across brands, and you still see which brand earned each deal.
BY 12 MONTHS
The next acquisition is onboarded in weeks, not quarters.
An industrial safety group built by acquisition: separate per-brand marketing instances, lead capture on a third tool, and cross-sell tracked in spreadsheets. A previous CRM attempt had failed on data and adoption, so trust was the real constraint.
HubSpot became the engagement system of record: one customer timeline, agreed definitions, brand-level pipelines and permissions, plus middleware to the ERP so the system underneath could change without rebuilding the CRM. Delivered inside HubSpot's co-delivery program alongside the group's advisory partner.
The shape of it
Client named on request. We do not publish engagement details before the client does.
Groups we've engineered for
Multi-brand programs, membership organizations and safety groups with complex data, acquisitions and shared operations.
Get the foundation right early and every later change is an adjustment, not a rebuild.
A read of what each company runs today, a feasibility check on the integrations, and a 100-day plan you can take to the board.