Your store in WooCommerce, your customers in HubSpot: one purchase history, up to date on both sides. Orders, products and carts flow with no exports or re-keying.
The problem
When WooCommerce and HubSpot don't talk, the store sells on one side and marketing communicates on the other, without knowing who bought what. The symptoms look alike from one store to the next.
To target a campaign, someone exports orders from WooCommerce, cleans up the file and imports it into HubSpot. By the time it's done, the list is already out of date and the latest buyers are missing.
A customer gets a promotion on the product they just bought, or a cart reminder after they have already paid. Without orders in HubSpot, your emails are shooting in the dark.
Number of orders, average order value, date of last purchase: everything exists in WooCommerce, nothing is usable in HubSpot. There is no way to tell a loyal customer from a one-time buyer.
Definition
WooCommerce is the e-commerce extension for WordPress, widely used by brands and SMBs that want to stay in control of their website. It manages the product catalog, cart, payment, orders and customer accounts. HubSpot carries the relationship: emails, segmentation, automated journeys, customer service and reporting.
The integration continuously moves customers, orders and products from WooCommerce to HubSpot, and consents both ways. The store keeps working as it does, and every contact record finally tells the full purchase story.
What flows
Here are the most common mappings between HubSpot and WooCommerce. The exact scope depends on your WooCommerce version, your extensions (subscriptions, abandoned carts, B2B) and what your hosting allows.
| In HubSpot | In WooCommerce | Direction | When |
|---|---|---|---|
| Contacts | Customers (accounts and guest orders) | Both ways | When the account is created or the first order is placed |
| Deals | Orders and their statuses | WooCommerce → HubSpot | On every order, then on every status change |
| Line items | Order lines (products, quantities, discounts) | WooCommerce → HubSpot | With the order |
| Products | Products, variations, SKUs and prices | WooCommerce → HubSpot | When a product or a price changes |
| Abandoned carts | Unfinished carts, depending on the extension used | WooCommerce → HubSpot | After the inactivity delay set at scoping |
| Purchase properties | Order history (total spend, number of orders, last purchase) | WooCommerce → HubSpot | Recalculated on every order |
| Refunds | Refunds and cancelled orders | WooCommerce → HubSpot | When the refund is processed |
| Marketing consent | Newsletter opt-in box at checkout | Both ways | At checkout, then on every unsubscribe |
Which system is the reference? WooCommerce for orders, products, prices, stock and payments; HubSpot for segmentation, marketing journeys and email subscription status. This master data rule is set in writing at scoping, field by field.
Tell us how your store runs: we will tell you what can sync with your WooCommerce version and extensions.
How to connect
Before continuous sync, there is often a historical data load: customers and past orders, loaded once into HubSpot by export and import, middleware or API, so customer value starts out right. After that, there are three ways to keep data flowing day to day.
WordPress extensions and HubSpot marketplace apps connect the two tools, depending on your version. The one to pick for a standard need: contacts, orders, products. Its limit: a fixed mapping that struggles with your extensions and custom fields.
Data Sync, Make, Workato or a specialized middleware orchestrate the flows from the WooCommerce API and webhooks. The right choice when your rules go beyond the standard and your catalog is stable. Its limit: every scenario has to be configured, maintained and monitored.
A direct connection, built for your rules: subscriptions, B2B sales, multiple stores, custom objects. Essential when the extension or the platform can no longer keep up. Its limit: it has to be designed around call limits, order peaks and your hosting, and it needs monitoring.
We recommend an option after auditing your flows, not before.
Use cases
A follow-up sequence goes out from HubSpot, with the products left in the cart. It stops on its own as soon as the order is placed.
The contact moves to the customer stage and enters a welcome journey: usage tips, a review request, a complementary product offer.
Their last purchase is older than their usual rhythm. A repurchase campaign is triggered, targeted on what they usually order.
A ticket opens in HubSpot for customer service, and the contact is removed from promotional campaigns while their request is handled.
Our method
Three phases, each covering processes, technology and people. A dedicated project manager stays with you from the first workshop to go-live, with a project committee and a steering committee.
Understand · Think
Three workshops, business, functional and technical, to map each flow with its source, direction and rules: order statuses, consents, extensions in place. We compare several approaches and recommend one. Nothing gets built before your written sign-off.
Build · Build
Field-by-field mapping between WooCommerce and HubSpot, then configuration or development. A pilot runs on a real sample of customers, products and orders before cutover; a delta then catches up the orders placed in the meantime.
Steer · Run
Go-live, team training, sync error monitoring and fixes. The integration then evolves with your store: a new extension, a new journey, a WooCommerce update.
At delivery
Acceptance testing runs in three steps: we test and share the counts, you check a sample of records in a shared file, we fix the gaps and rerun the checks. The acceptance report is signed after that, not before.
Pitfalls to avoid
An e-commerce integration rarely fails on the technology. It fails on rules nobody set. Here are the six points we lock down before writing a single line of code.
Case study
Apoticaria asked Copernic to connect its online store to HubSpot: orders, customers and carts brought together for follow-ups and journeys that track real purchases.
What clients say
“The Copernic agency really helped me get to grips with HubSpot and set up a strategy to optimize our conversion rate.”
“They know their product well and adapt strategies and needs to each person's level.”
Scroll →
Reviews translated from French
HubSpot Elite Partner
For 10+ years, we have connected HubSpot to online stores, ERPs and business tools: WooCommerce, Shopify, Sage, Pennylane. 800+ clients have trusted us with their CRM, and HubSpot has awarded us its highest partner tier.
Elite Partner and 4 accreditations
CRM implementation · Onboarding · Data migration · Architecture design
Yes, WordPress extensions and HubSpot marketplace apps connect the two tools. Their coverage depends on your WooCommerce version, your extensions and your HubSpot edition: they handle contacts, orders and products well, subscriptions, B2B sales or custom fields less so. We check what your store allows from the first conversation, then recommend the simplest approach that covers your flows, with no over-engineering.
The most common flows: customers, orders and their statuses, order lines, products and variations, abandoned carts, refunds, marketing consents and purchase properties such as total spend. The direction of each flow and the reference tool are set at scoping. Product images and attachments do not carry over by default. If you need custom objects in HubSpot, an Enterprise license is required.
Both, depending on the flow. An order or an abandoned cart can come through within minutes thanks to WooCommerce webhooks; the historical data load or recalculating purchase properties are often done in batches. The pace depends on your version, your hosting, call limits and your order peaks. We choose it flow by flow, based on how your teams use it.
A few weeks for a standard scope (customers, orders, products, abandoned carts), confirmed after scoping. A wider scope, with subscriptions, several stores, a large historical data load or data cleanup, takes longer. The schedule is set in the scoping document; it also depends on how available your leads are to approve each step.
An error must never go unnoticed. Every flow is logged: a rejected order (invalid email, unknown product, duplicate) is flagged without blocking the others. An alert goes to the designated person, the error is fixed at the source, then the order is replayed. In the Run phase, we track these logs, especially after a WordPress or extension update, and fix recurring anomalies at the root.
Yes, and it is often the best idea. Many projects start with a single flow: customers and their orders brought into HubSpot, to segment and measure customer value. Abandoned cart follow-ups, repurchase journeys and customer service are added next, on the same foundation. Scoping plans this path so nothing has to be redone at step two.
Other integrations
An expert calls you back within one business day.