How Octopus Energy Merged Two HubSpot Portals Into One

How Octopus Energy Merged Two HubSpot Portals Into One

Octopus Energy ran its B2B partner network across two separate HubSpot accounts: Octopus Trusted Partners (OTP), covering its installer network, and a second account covering Zero Bills and Tenant Power. Different teams working the same partner base couldn't see each other's history, and Octopus was paying for two licences to run what was, in practice, one business relationship.

We consolidated both into a single HubSpot instance in a three-week execution window, with no lost contracts, no duplicate billing, and the account's business-critical reporting intact from day one.

Two Disconnected HubSpot Environments

Octopus Energy's B2B partner network ran across two separate HubSpot accounts: Octopus Trusted Partners (OTP), covering its installer network of roughly 1,200 companies, and a second account covering Zero Bills and Tenant Power, with its own UK and German teams.

Different teams working the same partner base couldn't see each other's history. Sales and partner teams sometimes contacted the same company independently, unaware of prior conversations. And Octopus was paying for two separate HubSpot licences to run what was, in practice, one connected business relationship.

A Lean, Migration-First Project

We ran this as a lean, migration-first project: get one clean, unified environment live first, then layer in further automation later rather than scope-creeping the first phase.

Paid Discovery Before Quoting

Before any commitment, we ran a scoped discovery phase mapping both environments properly: data volumes, pipelines, existing automations, and every workflow that depended on the account structure staying exactly as it was, including a Google Sheets export feeding senior leadership reporting that had to survive the move intact.

A Sandbox Dry Run Before the Real Cutover

We ran a full sandbox migration first, specifically to catch anything that would only surface at scale. It worked: the dry run surfaced a data-loss risk where companies sharing the same domain would collapse into a single record during migration, silently dropping the others. We resolved every affected record before the issue ever touched production.

A Single, Out-of-Hours Cutover

We froze the account overnight on a Saturday, ran the full migration, and validated the result before Monday, so no one lost a working day to it. The old account was kept live and read-only afterwards rather than switched off, so historical data stayed accessible throughout.

Manual Rebuild Where the Tooling Couldn't Reach

The migration tool doesn't touch marketing email history, dashboards, saved views, or message templates. We rebuilt the business-critical Google Sheets reporting workflow from scratch and tested it for exact output parity with the original, recreated the saved deal and contact views used daily across UK and German teams, and preserved the original data-owner history against a custom property so nothing about who-owned-what was lost in the move.

Fast Follow-Up on the Details That Only Show Up at Cutover

Reconnecting integrations, restoring a German team email workflow tied to the old account's domain, and fine-tuning company ownership after the move were all planned parts of the post-cutover week, flagged to the team in advance rather than discovered as surprises, and resolved within days of go-live.