Getting Order History into HubSpot Without a £600-a-Month Connector
An early years education supplier had bought a serious HubSpot package and was using it as an expensive mailing list, because everything that mattered about a customer lived in OrderWise, the order and stock system, and HubSpot could not see it. The off-the-shelf connectors cost up to £850 a month and could not sync orders. This is how the sync got built instead, and why the sequence was integration first, then the data audit, then the restructure.
The Challenge: The customer data was in the wrong system
The supplier sells resources and training to nurseries, schools and multi-academy trusts. HubSpot had been bought as a marketing upgrade and never implemented as a CRM. It held 42,000 contacts with no idea which of them had ever bought anything, because orders, invoices, account status and the real customer hierarchy all lived in OrderWise. Marketing was segmenting on guesswork. Sales had no pipeline. A new CRM owner had been hired specifically to fix it, and the first thing he needed was data he did not have.
The obvious answer was a connector. Two were assessed. One cost between £300 and £850 a month depending on sync frequency, required a higher HubSpot tier than the supplier had, and at the time could sync customers but not orders, invoices or products, which were the whole point. The other was enterprise middleware priced for businesses ten times the size.
There was also a sequencing question. The original plan put a data audit first. But auditing HubSpot before the order history was in it would have meant cleaning a picture that was missing its most important half. Integration had to come first.
What Was Built: A sync that does only what the business needs
Scoping spike before commitment. A short, fixed-price spike to confirm what the OrderWise REST API actually exposed, what the API module would cost from the vendor, and whether a daily batch was sufficient. It was. Nobody needed real-time; they needed correct.
Field mapping agreed with the CRM owner. Every field that would move from OrderWise to HubSpot was written down, with who owns it, before anything was built. HubSpot properties were created to receive OrderWise identifiers, account data and job roles, so the two systems could be matched reliably from then on.
The sync itself. A scheduled job that pulls new and changed customers, contacts and orders from OrderWise, matches them to HubSpot companies and contacts on the OrderWise identifiers, creates what is missing, and updates what has changed. The customer hierarchy, trusts above schools, is carried across as parent and child companies. Order history lands against the company record so marketing can finally segment on who has bought what, and when.
Rules for fields people also edit. A job role field is kept current by the sync, but the category the marketing team uses for segmentation is only written for brand-new contacts or where it is blank, so the sync never overwrites a human decision. Where the two disagree, a standing mismatch report goes to the CRM owner every seven days with an inbox to work through, and unresolved items are handed to the sales lead.
Written as a purpose-built service rather than assembled in an automation platform, because the matching logic, the ownership rules and the error handling needed to be exact and testable. Hosted by Stack Logic, with monitoring and a small monthly cover so it keeps running when either system changes.
With order history in place, the work moved to the phases that depend on it: the contact audit and deliverability cleanup, the parent-child restructure, pipeline setup for the curriculum sales team, and the automation that follows a purchase.
The return is a CRM that knows who its customers are, at a fraction of the recurring cost of the alternative.
42,000 contacts that now carry OrderWise identifiers, account status and order history, so segmentation runs on what people bought rather than what they clicked.
£7,000 or more a year in connector subscription avoided against the £600-a-month option, before the HubSpot tier upgrade it would also have required.
A seven-day mismatch report instead of a sync that silently overwrites the marketing team's own categorisation, which is the difference between a tool people trust and one they work around.
The supplier's CRM owner now has the data he was hired to work with, and the phases that were waiting on it, audit, restructure, pipeline and automation, are under way on the same fixed-price basis.
The client is anonymised. The contact count and connector pricing are as assessed at the time; the annual saving is calculated against the mid-tier connector price.