Guide · Connected systems
Connect your CRM to your ERP without replacing it
When integration beats replacement, which system owns which data, and how the connection is built, secured and kept running.
You can connect HubSpot or Pipedrive to your ERP, accounts package or print MIS without replacing your ERP. The ERP stays the system of record for products, stock, orders and invoices; the CRM shows the sales team what it needs from them, on the account they already work from. Replacement is worth considering only when the ERP itself no longer fits the business, which is a different and much larger decision.
This guide is for managing directors, operations directors and IT leads at UK manufacturers and distributors. It covers when integration beats replacement, which system should own which data, how the connection is built, what to check on security and on-premises systems, and where these projects usually go wrong.
When is integration better than replacing the ERP?
Integration is usually the better answer when:
- the ERP does its core job of stock, production, orders and invoicing well
- the problem is that sales cannot see what the ERP knows
- the business has years of history and processes built around the ERP
- the cost and disruption of moving operations to a new system is out of proportion to the problem
Replacement deserves a serious look when the ERP is out of support, cannot be reached by any secure means, cannot model how the business now works, or is being replaced for operational reasons anyway. Even then, the CRM connection is usually part of the new system's project rather than a reason for it.
Which system should own each type of data?
Each field should have one owner. The other system reads it, and only changes it through agreed rules.
| Data | Owner | Shown in the CRM? |
|---|---|---|
| Customer accounts and billing details | ERP or accounts | Yes, read by sales |
| Contacts and relationships | CRM | Passed to the ERP where orders need a named contact |
| Products, price lists and stock | ERP | Yes, for quoting and conversations |
| Opportunities and pipeline | CRM | No need to send to the ERP |
| Quotes | One of the two, agreed per business | Yes |
| Orders and order status | ERP | Yes |
| Invoices, credit status and payments | ERP or accounts | Yes, summarised |
| Jobs and production status (print MIS) | MIS | Yes, for account managers |
What information do salespeople actually need?
Less than the ERP holds, and more than most CRMs show. On each account, usually:
- what the customer has bought, by product family, and when they last ordered
- spend this year against last year
- open quotes, with a value and an owner
- order status, so nobody phones the warehouse to find out
- credit status, so a rep does not promise what accounts will not release
- for print and packaging, job status from the MIS
Anything else should earn its place. A record crowded with ERP fields nobody reads is harder to use than one with none.
How is the integration built?
At its simplest, three parts:
- A way in to each system. Usually each system's API: the official way to read and write its data. Cloud systems such as Xero and HubSpot provide one; on-premises systems may need a secure route in first (see below).
- The logic in between. Matching records (which ERP customer is which CRM company), mapping fields, applying the ownership rules and handling errors. This is where most of the design work sits.
- A tool to run it. Whichever suits the job: a native connector where one exists and goes deep enough, an integration platform such as Make or n8n, BPA Platform, or custom code for unusual systems or volumes.
Whichever tool is used, the integration should log what it did, retry what failed and tell someone when it stops.
What about an on-premises ERP?
Many Sage 200 and older ERP installations run on a server inside the business. A cloud CRM cannot reach them directly, and opening the network to the internet is not an acceptable answer. The usual options:
- a secure outbound connection from inside the network, so nothing has to be opened up; Flowbird built this for an on-premises Sage 200 and describes it in Flowbird Tunnel
- the ERP vendor's own cloud connector, where one exists
- a scheduled export to a secure location, for low-volume or low-urgency data
Ask early who manages the server, who holds the ERP's support contract and what the ERP partner allows. Working alongside the ERP partner, not around them, avoids most surprises.
What should you check on security and permissions?
- Least privilege. The integration's user in each system should be able to read and write only what the integration needs, and nothing else.
- Read-only where possible. Most of what flows from the ERP to the CRM can be read-only on the ERP side.
- Who sees what in the CRM. Margin, credit limits and pricing may need restricting to certain roles once they are visible to sales.
- Credentials. Stored by the integration tool, not in spreadsheets or emails, and changed when people leave.
- Personal data. Contact data moving between systems is still personal data under UK GDPR, so agree what moves, why, and how long it is kept.
- An audit trail. Logs of what changed, when, and from which system.
How often should data synchronise?
As often as the business needs, and no more:
| Data | Typical frequency | Why |
|---|---|---|
| New customers and contacts | As they change, or within the hour | Sales and accounts both act on them quickly |
| Orders and order status | As they change, or several times a day | Reps answer customer questions from them |
| Invoices and payments | Daily | Account review rather than live decisions |
| Products, prices and stock | Daily, or as they change for fast-moving stock | Quoting accuracy |
| Historical spend and buying patterns | Nightly | Built from order history; nothing changes minute to minute |
Real-time sounds better but costs more to build and monitor. Most of the value comes from data that is reliably a few hours old rather than occasionally instant.
What are the common project risks?
- Dirty data copied faithfully. Duplicate customers, inconsistent product codes and branches set up as separate customers all travel through the connection. Clean them first.
- No agreed owner per field. Two-way syncs without clear rules overwrite each other.
- Scope creep. Every field looks useful in the workshop. Start with the information that changes a sales conversation.
- Hidden ERP customisation. Older installations often carry custom fields and processes nobody documented.
- No one watching it. Integrations stop quietly when a password changes or a system updates. Monitoring and an owner matter more than the build.
- Leaving the ERP partner out. They know the system and its support terms; bring them in early.
What are the stages of a CRM to ERP connection?
- Discovery. Agree the questions the sales team needs answered and the records that answer them.
- Data review. Check duplicates, codes and account structures in both systems.
- Design. Field ownership, matching rules, direction and frequency, written down and agreed.
- Access. API users, permissions and, for on-premises systems, the secure route in.
- Build and test. Against a copy or a sample first, then with real data and real users.
- Go-live and monitoring. Switch on, watch closely for the first weeks, and agree who owns it after that.
Which connections has Flowbird delivered?
Flowbird distinguishes between connections it has delivered, connections with a published case study, and connections that are technically possible:
| System | Status |
|---|---|
| Sage 200 (on-premises) to HubSpot | Delivered; published case study: Connecting Sage 200 and HubSpot |
| Xero from Pipedrive | Delivered; published case study: automating invoice creation |
| Sage 50 (on-premises) to HubSpot | Delivered; published case study: Sage 50 orders in HubSpot |
| Linnworks (order management) to Pipedrive | Delivered; published case study: every sale credited to the right person |
| Tharstern (print MIS) to HubSpot | Delivered; published case study: print estimates in HubSpot |
| TidyERP | Connection underway; not yet delivered |
| Odoo | Flowbird advises on choosing Odoo and supports its implementation alongside an Odoo partner; no Flowbird-built connection yet |
| Other ERPs | Technically possible where the system offers an API; not yet delivered by Flowbird |
For a system not on the list, the first question is what it exposes: an API, a database Flowbird can be given secure access to, or exports. The discovery call establishes that before anything is promised. More on the service itself is on CRM and ERP integration, and by sector on manufacturing and engineering, wholesale and distribution and packaging and printing.
Where to start
If you already know which systems need connecting, talk to an integration specialist: a free conversation with someone who builds these connections, about the systems you run and what the sales team needs from them.
If the question is still what your customer and order information could show, start with the Account Growth Audit, a fixed-price, two-week analysis of two years of invoice data exported from your ERP. It shows which accounts are buying less, what they have stopped buying and who is overdue a reorder, and ends with a plan for connecting your ERP and CRM.
Two worked examples: a UK print and labels group whose Tharstern estimates reach HubSpot within minutes, and a business whose Sage 50 orders reach HubSpot every three hours through the Power BI it already ran.