It happens the same way in almost every group. One region buys HubSpot and it works. Another region sees it and buys its own. Five years later there are six portals, six contracts and nobody can answer a question about the group without exporting spreadsheets.
We recently built this case for a global consultancy running six regional portals. The saving was real, but it was not the most important finding. Here is how to build the case properly, and where it usually goes wrong.
Start with billing, not invoices
Every region believes it knows what it pays. Most are wrong in the detail. Open the account and billing page in each portal and write down what is actually live:
- Every product and tier, including the Starter add ons nobody remembers buying
- Core seats and sales or service seats, separately
- Marketing contact tiers
- The renewal date and the discount on each contract
In our case the group had bought Content Hub five separate times and Data Hub Starter four times. One region was paying for a website with no CRM behind it. Another had no platform at all, because a standalone portal was too expensive to justify on its own.
Model one portal honestly
Price a single portal carrying every seat the regions actually use, at the tier the group needs. Then compare it with the total. For our client the modelled cost came in a little under half the current spend.
If the saving pays for the migration, the single source of truth is free.
Do not stop at licences. Add the costs the fragmentation creates: the BI work to stitch six databases together, the separate negotiations, and the regions that cannot justify a subscription at all.
The objection you will hear first
Every regional leader has the same worry: one portal means our data, our brand and our team mixed up with everyone else's. Answer it before it is asked.
| The worry | How HubSpot handles it |
|---|---|
| We have our own brand and domains | Business Units partition brand, sender domains, assets and reporting per region, and Content Hub hosts multiple domains in one account |
| Other regions will see our deals | Pipelines and records are permissioned by team |
| We sell in our own currency | Multi currency deals, rolled up to one reporting currency |
| Our site is not in English | Native multi language pages with a language switcher |
This is also why the tier matters. Without Business Units, which need Enterprise, consolidation puts every brand in one shared space and recreates the mess it set out to fix. Build the Enterprise cost into the model from the start.
Sell the prize, not the saving
The saving gets the meeting. The shared database gets the decision. With one portal a group can finally see itself:
- One leaderboardEvery consultant ranked on the same numbers, regardless of region
- Cross sellA rep in one country sees that a client is already engaged in another
- Group pipelineBoard level visibility with no warehouse or ETL
- No shadow systemsRegional workarounds get one clean source to read from
Sequence it by renewal date
- Get one group quote. One negotiation instead of six small ones.
- Build the structure first. Business Units, domains, teams and permissions before any data moves.
- Pilot where a region gains. A region getting its first CRM is low risk and quick proof. A region losing a working CRM is neither.
- Move the rest on their renewal dates. Cut over before each contract renews so nobody pays twice.
- Name an owner per region. Consolidation is change management with a data migration attached.
When not to consolidate
If regions share no clients, no products and no leadership reporting, the argument weakens. If one region is on a heavily customised setup with integrations that only it uses, price that migration properly before promising a saving. The case has to survive the first regional leader who checks it.
Want the model run on your own portals? Send us the regions and the renewal dates and we will tell you whether it pays.
