Move JTL customer data and orders into HubSpot
Push customers, companies and orders from JTL-Wawi into the HubSpot CRM automatically – with clean field mapping and no duplicates. So sales and service work with complete profiles instead of retyping records by hand.
In short: a sync reads your customer, company and order data straight from the JTL database and creates them in HubSpot as contacts, companies and deals. The sync runs one-way, JTL stays the source and HubSpot follows. Thanks to the JTL customer number as a unique key, every customer stays exactly one record, no matter how often the sync runs. The rest of this page shows which fields go where, in what timing, and how the duplicate protection works technically.
- What is the JTL–HubSpot data sync?
- The sync transfers the master data from the JTL warehouse system into the HubSpot CRM: a JTL customer becomes a HubSpot contact, an account becomes a company, an order becomes a deal. The goal is a CRM where sales and service see the full customer without switching to the shop system.
Why the data stays stuck in JTL
In many merchant setups the customer sits in JTL-Wawi but not in the CRM. Sales then works on half profiles: name and email are there, but customer group, revenue or the last order are missing. So someone keeps switching between the warehouse system and HubSpot, or types the customer in a second time.
If your concern is instead an existing CRM base that has gone stale, the guide on enriching customer master data is the better starting point. When the data comes from an ERP rather than JTL, it is more a case for CRM integration.
Which data moves from JTL into HubSpot
On the left the JTL object, on the right the target in HubSpot. Customers and companies are the core, orders and revenue an extension. The customer number is not a display field but the key everything is matched on.
| JTL-Wawi | HubSpot |
|---|---|
| CustomerCore Name, email, phone, billing and shipping address, customer group | Contact |
| Company / accountCore Company name, address, VAT ID, linked contacts | Company |
| Customer numberKey Unique key for the match – prevents duplicates | Custom property (external ID) |
| OrderExtension Order number, order value, status, linked contact | Deal |
| Revenue / order historyExtension Total revenue, last order, number of orders | Metric on contact / company |
Custom JTL attributes like a customer segment or a sales territory can map onto additional HubSpot properties. If the data should come from an ERP or a line-of-business application rather than JTL, that is more a case for CRM integration.
The key against duplicates
The most common problem when moving customer data is duplicates. Run an import twice and the customer suddenly sits in the CRM twice, and from there the reports count wrong. The sync solves this with the JTL customer number: it is carried as its own property on the HubSpot contact.
On every run the sync first looks for that number. If it finds the customer, it updates the record. If not, it creates one. This upsert principle makes duplicates technically impossible, no matter how often the sync runs. As a second signal the email address helps when a contact already existed in HubSpot by hand.
How often the sync runs
Not everything has to be real-time. Timing is set per object, matched to how quickly the data is needed in the CRM.
For everyday sales work an hourly sync is almost always the right trade-off: HubSpot is practically current during the day and the load on the warehouse system stays low. Real-time pays off where a new customer should trigger a CRM automation right away, for example a welcome sequence.
Not sure which JTL fields are actually maintained cleanly on your side?
Discuss your JTL setup →Orders and revenue in the CRM
Customers and companies are the core. The interesting part begins when orders come along too. A JTL order becomes a HubSpot deal with order value and status, total revenue and order history land as metrics directly on the contact or the company.
That way sales sees not just who a customer is, but what they are worth. Segmenting by high-revenue existing customers becomes possible, as do automatic follow-up sequences based on the last order. This order and revenue link is an extension of the standard sync that we plan separately in the project, because it depends more on the structure of your JTL orders.
What the sync saves in time
When the automatic sync pays off
Sync pays off
- New customers arrive regularly through the shop or the warehouse system
- Sales and service work in HubSpot and need current profiles
- Customer data changes constantly (address, contacts, revenue)
- Reports in HubSpot should run on the full base, not a slice
Export/import is enough
- The customer base is small and rarely changes
- HubSpot is only used for individual campaigns, not day-to-day
- Transferring a list once or twice a year is enough
Common questions about the JTL–HubSpot sync
Discuss your JTL–HubSpot setup
20 minutes, no strings. We look at your JTL and HubSpot setup and clarify which data should move over and in what timing. Then you get an honest assessment.
Pick a time →Tell me about your shop setup
Let me know how many customers and orders you have in JTL and what you want to do with them in HubSpot. I estimate effort, timing and field mapping before anything runs.
I have been building integrations between warehouse systems and CRMs for years, mostly with JTL, HubSpot and n8n. This page sums up what really matters when moving customer data: clean mapping, a unique key and the right sync timing.
Auf LinkedIn vernetzen →