Start a project
Home
Services
Web Application DevelopmentMobile App DevelopmentCloud & DevOpsCRM & Business SystemsData, Analytics & BISupport & MaintenanceAll services
IndustriesWorkAboutInsightsCareersContactStart a project
Our product · in validation

BridgeCentral

Business Central and HubSpot, kept in step. A two-way sync we design, build, fund and support ourselves — and the clearest evidence we can show of how we approach integration work.

What it is

BridgeCentral is a two-way integration between Microsoft Dynamics 365 Business Central and HubSpot, built by VOL Group. It keeps companies, contacts, items and invoices in step, and surfaces account balance and overdue invoices on the HubSpot company record.

Syncing is webhook-driven rather than batched, so changes propagate within a minute. The pilot programme opens in autumn 2026, with a HubSpot App Marketplace listing planned for early 2027.

The problem it solves

Finance lives in the ERP and sales lives in the CRM, and the two disagree. Somebody rekeys an order, an invoice never makes it across, or a sync quietly merges two customers because it matched on company name.

The connectors that exist tend to be either unreliable at the edges — partial syncs, wrong-record merges, no invoice data at all — or capable but priced for enterprise budgets. There is a gap in the middle, and that is where this sits.

Capability

What it does

The decisions below are the ones that separate an integration that survives contact with real data from one that does not.

Companies and contacts

Records matched on customer number rather than fuzzy name matching, so a sync never silently merges two customers that happen to share a trading name.

Items and invoices

Product and service items flow through to HubSpot, and posted invoices arrive with them — so a deal record shows what was actually billed, not what somebody hoped would be.

Balance and overdue visibility

Account balance and overdue invoices surface on the HubSpot company record. Sales can see a customer is 60 days late before they pitch an upsell, without opening the ERP.

Webhook-driven, not polled

Changes propagate within a minute because both ends push. Nightly batch jobs are the reason most ERP-to-CRM integrations feel stale by lunchtime.

Built to survive a failed call

Retries, idempotent writes and a logged audit of every record touched. Integration work lives or dies on what happens when the other end returns a 500.

Field mapping you can read

Mappings are configuration, not code. Changing which BC field lands in which HubSpot property does not require a deployment.

Where it is

Status and timeline

We would rather show you a product mid-build and be straight about the stage it is at than wait until it is finished and claim it was always inevitable.

Platform
.NET 8C#Azure FunctionsAzure Service BusAzure SQL
Integrations
Business Central OData & API v2.0HubSpot CRM API v3OAuth 2.0Webhooks
Operations
Azure MonitorApplication InsightsStructured audit loggingInfrastructure as code
Now

Validation and pilot recruitment

Talking to Business Central partners and end customers to confirm which fields and flows actually matter before the sync surface is locked.

Autumn 2026

Pilot programme

A small number of pilot organisations running the connector against real data, free for the pilot period, with direct access to the people building it.

Early 2027

HubSpot App Marketplace

Listing on the HubSpot App Marketplace, subject to their review process and to the pilot telling us the product is ready.

Why it is on this page

A product is a better portfolio than a case study

Client work is confidential and, until written permission comes through, unusable as evidence. A product we own is not. You can read the positioning, see the architecture choices, watch the timeline hold or slip, and judge us on all of it.

Answers

About BridgeCentral

Is BridgeCentral a client project or your own product?

It is our own. VOL Group designs, builds, funds and supports it. We are including it here because it is the clearest available evidence of how we approach ERP and CRM integration — the code, the architecture decisions and the operational choices are all ours to show.

Can I use it yet?

The pilot programme opens in autumn 2026 and we are recruiting for it now. Details, pricing and the waitlist are on bridgecentral.io.

Why build a product rather than take on more client work?

Because integration between ERP and CRM is a problem we kept meeting, and the existing options were either unreliable or priced for enterprise budgets. Building it once properly is more useful than solving it bespoke for each client — and the engineering that goes into it is the same engineering our clients get.

Does this mean you only work with Business Central and HubSpot?

No. BridgeCentral is one product built on general integration practice. We work across Salesforce, Zoho, Dynamics, Xero, Sage and bespoke systems — see CRM and business systems.

Who do I talk to about a similar integration for our systems?

Us, directly. Get in touch and describe the two systems and what has to stay in step between them.

Need two systems to agree with each other?

ERP to CRM, CRM to finance, website to warehouse. Describe what has to stay in step and we will tell you honestly what it takes.