Let's Unbox OW Sync - Orderwise Connector with Daryl Michel
- Chris CarolanHost
- Daryl MichelGuest
June 18, 2025
Daryl Michel walks Chris through OW Sync, the connector that brings OrderWise ERP data into HubSpot: mapping a customer can change themselves, a one-way sync on purpose, and a live build that pulls work orders into a native object. Underneath, why order data belongs where customer-facing teams work.
Key takeaways
Order data belongs where customer-facing teams already work. The project began with a client who wanted reps to see order history in HubSpot without logging into the ERP [09:00].
A two-way sync can spread bad data in both directions. OW Sync runs one way by design, and data goes back only through workflows when criteria are met [10:04][10:38].
The customer owns the mapping: which properties sync, which stay in the ERP and how often, configured inside HubSpot instead of waiting on a developer [29:33][33:26].
Don't import the ERP's naming into HubSpot. Value lists turn ERP codes into readable values without breaking HubSpot's data model [37:03][39:20].
Export definitions let a custom ERP query land on any HubSpot object, shown live with work orders on the native Listings object [41:24][51:36].
Faster is not always better. Start on a longer sync cycle, shorten it once the data comes through correctly, and use the on-demand refresh when a record can't wait [56:26].
Chris's frame: decide where the unified view of the customer lives first, then the question becomes how data gets there, not who owns which system [17:09][18:15].
Scoping and data mapping take more of the project than the build itself [16:37].
The guest
Daryl Michel
Keep learning
You just watched the work. Now build it.
The next step is doing it yourself — live, with people on the same path.
Get the next conversation in your inbox
One signal-dense note when a new episode lands. No noise.