When a business runs HubSpot alongside an ERP, the arguments are rarely about technology. They are about authority: sales says the address in HubSpot is right, finance says the ERP is right, and both systems happily overwrite each other until nobody trusts either. The fix is not a cleverer sync. It is deciding, field by field, which system owns which data, and building the integration to enforce it.
The one-owner principle
Every type of data should have exactly one system of record: the place where it is created, corrected and trusted. Other systems may hold copies for convenience, but copies are read-mostly and always lose an argument with the owner. Once you adopt that principle, most integration design questions answer themselves.
A sensible default ownership map
Every business differs, but this default holds for most UK mid-market companies running HubSpot with an ERP such as NetSuite, Business Central, Sage 200 or an industry system:
| Data | Owner | Why |
|---|---|---|
| Contacts, communication history, consent | HubSpot | The CRM is where relationships live and where marketing compliance is managed. |
| Pipeline, deals, forecasts | HubSpot | Selling happens in the CRM; the ERP only needs to know about deals that become orders. |
| Products, price lists, discount rules | ERP | Pricing is a finance-controlled asset; HubSpot receives a published copy for quoting. |
| Stock and availability | ERP | Operational truth lives where goods are managed; the CRM shows it read-only. |
| Invoices, payments, credit status, balances | ERP | Auditable financial records belong in the ledgered system; HubSpot displays them. |
| Billing address and payment terms | ERP | Finance verifies these; a rep's edit in the CRM should propose, not overwrite. |
The grey zones (where the fights actually happen)
The customer record itself. A company usually starts life in HubSpot as a prospect. The clean pattern is a handover of ownership: HubSpot owns the account until the first order is accepted, at which point the ERP creates the customer, becomes the owner of its commercial identity, and passes back the ERP customer number as the shared key.
Orders and quotes. A quote is a sales artefact; an accepted order is a finance artefact. Decide the precise moment of handover (usually order acceptance) and make the integration perform it explicitly, rather than letting both systems hold half-formed versions of the same thing. This is the order-to-cash join we cover in syncing HubSpot deals to invoices.
Write rules that make ownership real
Ownership only means something if the integration enforces it. Four rules do most of the work:
1. Writes flow from owner to copy. The owner broadcasts changes; copies accept them. Edits made on a copy either sync back as a proposal for review or are locked in the interface.
2. Conflicts resolve by ownership, not by timestamp. "Latest write wins" is how a stale laptop edit beats a verified invoice address. The owner wins, whatever the clock says.
3. Every record carries a shared key. Store the ERP customer number on the HubSpot company and the HubSpot record ID in the ERP. Matching on names or emails eventually merges two different customers, and unpicking that costs far more than doing keys properly on day one.
4. Drift gets measured. A weekly automated comparison of key fields between systems catches the slow divergence that silent failures cause. If the drift count is not zero, an engineer looks at it. Unmonitored syncs rot; our guide to integration reliability explains what good monitoring looks like.
How this shapes the build
A source-of-truth map turns a vague "sync HubSpot with the ERP" project into a precise specification: which objects, which direction, which triggers, which conflict rules. That is the document we produce in the scoping phase of every custom HubSpot integration, and it is why fixed-price quoting is possible at all. It is also a useful exercise even if you build nothing for a year: agreeing ownership on paper stops most of the data fights on its own.
Frequently asked questions
Should HubSpot or the ERP be our source of truth?
Neither owns everything. HubSpot should own relationships, pipeline and consent; the ERP should own products, pricing, stock and financial documents. The customer record itself usually transfers ownership from CRM to ERP at the first accepted order.
How do we stop HubSpot and our ERP overwriting each other?
Enforce one owner per field, make writes flow from owner to copy, resolve conflicts by ownership rather than by latest timestamp, and join records on a shared key such as the ERP customer number instead of matching names.
Can we do this with a native connector?
Native syncs generally treat both systems as equals with field mappings, which is the opposite of ownership. Enforcing per-field ownership, proposal-style write-backs and drift monitoring normally requires a custom integration.
Designing a HubSpot and ERP architecture? Read the complete guide to connecting anything to HubSpot, see how we handle NetSuite, Business Central and Sage 200, or talk to us about custom HubSpot integration services.
Stay Updated with Our Latest Insights
Get expert HubSpot tips and integration strategies delivered to your inbox.