How Pineo Migrated Octopus Energy's Two HubSpot Accounts Into One

How Pineo Helped Octopus Energy Consolidate Two HubSpot Accounts

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 project from start to finish. The data migration itself happened on a Saturday, and the team was back in and working normally from the Monday, no lost working day and no lost data. Once the old Zero Bills account is cancelled, it's an annual saving of £14,000 from licence costs.

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.

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. One of the most important things discovery surfaced was a Google Sheets export used for reporting, an integration that doesn't migrate automatically and had to be rebuilt from scratch, so it went into the plan from day one rather than being found late.

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

The team used HubSpot as normal on Friday afternoon. We froze the account overnight, ran the full migration on Saturday, and validated the result before Monday. When the team logged back in on Monday morning, the new environment was live and usable straight away, no lost working day, no re-onboarding. The old Zero Bills account was switched to read-only, encouraging the team to use the new OTP environment going forward.

The migration into one HubSpot account went a lot more smoothly than we expected. We didn't lose a single working day, and by Monday morning it just worked. Pineo planned for the things that could go wrong, so when something did come up, it had already been thought through.

_{Sivvy Mikitsey
GTM Lead, Octopus Energy}

Manual Rebuild Where the Tooling Couldn't Reach

The migration tool doesn't migrate marketing email history, reporting dashboards, saved views, or message templates. We rebuilt the business-critical Google Sheets reporting workflow partly with the HubSpot API, with the final configuration done manually directly in the HubSpot workflow.

We also recreated the views used by both the UK and German teams on the deal, company, and contact objects.

We preserved the original record-owner history against a custom property so nothing about who-owned-what was lost in the move, since there were conflicting company and contact owners in both HubSpot accounts for the same records.

The German team's email inbox was migrated across into the new environment, with a domain configuration step needed to get it sending correctly, resolved within days of go-live.

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

Reconnecting integrations and fine-tuning company ownership after the move were 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.