Case studyBusiness tool synchronisation
Synchronising an ERP, a CRM and Outlook to eliminate double entry
An SME that sells and installs laboratory equipment connects HubSpot, Odoo and Outlook. Prospects, contacts, quotes, orders and sales exchanges flow according to precise rules, without recreating the same data in each tool or letting several versions of one customer contradict each other.
- HubSpot
- Odoo
- Outlook

- Company
- Laboratory equipment distributor, 38 employees
- Volume
- 120 active customers and 250 updates a day
- Team
- 6 salespeople, 3 sales admin assistants and 4 technicians
- Tools involved
- HubSpot, Odoo, Outlook and PostgreSQL
(01)Before the automation
Before: the same customers existed in several versions across the CRM, the ERP and mailboxes
Salespeople created prospects, contacts and opportunities in HubSpot. When a deal was won, a sales admin assistant recreated the customer in Odoo, copying over the billing address, the delivery address, the VAT number and the contacts needed for the order.
Exchanges, technical documents and confirmations stayed in Outlook. A change requested by a laboratory could be recorded in HubSpot, corrected in Odoo or simply remain in an email thread. So the team did not always know which address to use for delivery, which contact should receive the invoice or which version of the quote had actually been approved.
Duplicates multiplied when one group owned several laboratories or when the name of the establishment varied slightly. Corrections were made in one tool without being passed on to the others, so that three reliable pieces of software ended up producing, together, uncertain information.
(02)System put in place
Case studyAfter: each type of data has a source of truth and a rule for how it flows
HubSpot remains the source of truth for prospects, sales contacts, opportunities and next actions. Odoo becomes the reference for billed customers, delivery addresses, orders, payment terms and equipment sold.
When an opportunity moves to “won” in HubSpot, the workflow checks the required fields, looks for an existing customer in Odoo and creates the account only if no reliable match is found. The Odoo identifier is then sent back to HubSpot to link the two records.
Outlook keeps the exchanges, but emails tied to an opportunity or an order are attached to the right file through its identifier. Address conflicts, possible duplicates and incomplete fields go into a validation queue instead of being passed automatically to every system.
(03)How the workflow runs
Case studyThe workflow does not copy all the data everywhere.
It moves only the information needed, from a clearly defined source to the system concerned.
- 01
Detect a won opportunity or a relevant change in HubSpot
- 02
Check the SIREN number, VAT, addresses and required contacts
- 03
Look for the existing customer in Odoo
- 04
Create or update the account according to the priority rules
- 05
Send the Odoo identifier and the synchronisation status back to HubSpot
- 06
Attach Outlook emails to the right customer, quote or order
- 07
Put duplicates and conflicts in a validation queue
- 08
Log exchanges, corrections and retries
What stays under human control
- Validating duplicates and ambiguous matches
- Deciding on address or contact conflicts
- Correcting the data in its source system
- Evolving the synchronisation rules and access rights
Possible operational effects
- A large part of double entry removed
- More consistent customers and contacts across departments
- Less searching before an order or delivery
- Traceable synchronisations and errors
(04)Example synchronisation rule
Case studyThe “Bordeaux laboratory spectrometer” opportunity moves to “won” in HubSpot.
The system checks the SIREN number, the delivery address and the billing contact, and looks for a matching establishment in Odoo.
Opportunity won → Odoo customer found → order prepared → Odoo identifier sent back to HubSpot
If two establishments have similar names or the billing address differs from the one on record, the creation is suspended. The sales admin assistant receives both records, the conflicting fields and the history needed to decide whether to update the customer or create a new establishment.
(05)Points to watch
Five things to keep an eye on.
- 01Each field must have a clearly defined source of truth.
- 02Two-way synchronisation must not create a loop or overwrite a more recent value.
- 03Technical identifiers must be kept between HubSpot and Odoo.
- 04Errors must be retried without replaying operations that already succeeded.
- 05Any change to an API, schema or access right must be monitored.
Security, access rights, GDPR, error logging and retry tests must be suited to the commercial and financial data exchanged.
(06)Conclusion of the case
Each piece of information is created once, in the right tool, then shared according to a known rule
In this scenario, HubSpot drives the sales relationship, Odoo manages the order and Outlook keeps the exchanges. The integration layer connects these systems, isolates conflicts and stops teams from maintaining several competing versions of the same customer.
Services behind this project