Short answer:HubSpot's native Shopify integration syncs customers, orders, products, and abandoned checkouts into HubSpot, with changes propagating in roughly ten minutes. It covers standard D2C automation well. It does not sync metafields, variant-level detail, or subscriptions, and those three gaps are what push B2B and subscription brands to middleware or a custom build.
01. Does HubSpot Integrate with Shopify?
Yes, natively. HubSpot builds and maintains an official Shopify app that connects your store through HubSpot's data sync engine. Installing it is free; the practical ceiling is your HubSpot tier, because the automation you will want to run on the synced data (workflows, custom-coded actions, advanced segmentation) lives in paid Hubs.
The integration answers a specific problem: your revenue data lives in Shopify while your customer communication lives in HubSpot, and without a sync your CRM is guessing. Connected properly, HubSpot stops being a mailing list and becomes the system that knows who bought, what they bought, what they abandoned, and when they went quiet.
What this guide covers is the part the install page does not: which objects actually move, in which direction, where the known gaps are, and the point at which the native app stops being enough.
02. What Syncs (and In Which Direction)
Direction matters more than most teams expect. Two-way objects can be edited on either side; one-way objects treat Shopify as the source of truth. Build your process around that or the two systems will disagree within a month.
| Object | Direction | Notes |
|---|---|---|
| Customers to Contacts | Two-way | Core fields: name, email, phone, address. Marketing consent status carries over; segment on it before sending |
| Orders | One-way (Shopify to HubSpot) | Order value, line items, and status. Feeds lifetime value, order recency, and purchase-behavior lists |
| Products | Two-way | Price and SKU sync so orders reference real product records. Variants roll up under the parent product |
| Abandoned checkouts to Carts | One-way (Shopify to HubSpot) | Cart contents attach to the contact; powers recovery workflows with real cart data in the email |
| Companies | One-way (Shopify to HubSpot) | Relevant mainly for B2B stores where Shopify company records exist; see section 06 |
| Metafields | Does not sync | Custom attributes stored in Shopify metafields need middleware or a custom API layer |
| Subscriptions | Does not sync | Recurring billing objects are outside the native scope; subscription brands need a custom path |
Sync behavior evolves with HubSpot and Shopify API releases. Verify the current object coverage in HubSpot's data sync settings before building automation on any single field.
03. Setting It Up: The 6-Step Sequence
The install takes minutes. The setup that determines whether the data is trustworthy takes a day. This is the order that avoids rework.
Install the HubSpot app from the Shopify App Store
Use the official HubSpot-built app, not a third-party connector, as your starting point. Connect it to the HubSpot portal that owns your marketing and CRM data. If an old third-party Shopify connector is still installed from a previous setup, remove it first so two apps do not write to the same properties.
Decide the identity rules before the first sync
Email address is the join key between Shopify customers and HubSpot contacts. Before syncing, decide how to handle guest checkouts, duplicate emails across stores, and existing HubSpot contacts that predate the store. The first sync writes at volume; cleaning up a bad merge afterward costs far more than an hour of planning.
Review property mappings, then run the historical sync
Walk the default field mappings and add custom mappings for anything your segmentation depends on. Then run the historical import of customers and orders so lifetime value and first-purchase dates are correct from day one. On large catalogs, expect the initial sync to take hours, and verify record counts against Shopify when it finishes.
Build the core lists
Minimum viable segmentation: first-time buyers, repeat buyers, high lifetime value, lapsed customers by order recency, and abandoned cart contacts. These five active lists power most e-commerce automation, and they only work if the order sync from step 03 is verified.
Turn on revenue workflows one at a time
Start with abandoned cart recovery, then post-purchase follow-up, then winback for lapsed customers. Launch them sequentially with a week between, so when metrics move you know which workflow moved them. Resist turning on every template the first day.
Verify the sync health monthly
Check HubSpot's data sync health screen for skipped or failing records, spot-check a handful of recent orders against Shopify, and re-verify mappings after any Shopify API version change or app update. Integrations rarely fail loudly; they drift.
04. Where It Breaks: The Five Known Gaps
These are the five issues that generate most of the support tickets we see on Shopify-HubSpot setups. None are fatal; all are cheaper to handle before launch than after.
Metafields do not cross the bridge.
Anything your team stores in Shopify metafields, product specs, customer tier, wholesale flags, stays in Shopify. If segmentation or routing depends on it, that data needs middleware or a scheduled custom sync into HubSpot properties.
Variants roll up to the parent product.
The product sync treats variants as children of one product record. Brands that report or automate at variant level (size, colorway, pack count) will find HubSpot blind at that grain without custom line-item handling.
Older abandoned cart mappings broke quietly.
Shopify API updates in 2025 removed legacy checkout fields. Cart recovery flows configured before then can keep sending with empty or wrong merge fields. If your flow predates 2025, audit the mappings even if the emails still send.
Multi-store portals need property discipline.
Two Shopify stores syncing into one HubSpot portal will fight over contact properties unless store-specific properties and list logic are planned up front. Decide the source of truth per property before connecting store number two.
Consent is synced, not solved.
Marketing consent captured at Shopify checkout carries into HubSpot, but your email sending logic still has to respect it per region (CASL in Canada, GDPR in Europe, UAE and Saudi rules in the Gulf). Sync status is not send permission.
When order data goes missing entirely rather than partially, the cause is usually upstream of the mappings; we broke down the seven most common failure modes in why orders fail to reach your sales pipeline.
05. Native vs Middleware vs Custom Build
The wrong way to decide is by tool. The right way is by data model: list what your automation actually needs to know about a customer, then check it against what the native sync provides.
- Stay native: single store, standard catalog, automation built on contacts, orders, and carts. This covers most D2C brands, and it is free
- Add middleware (iPaaS or a connector platform): you need metafields, variant-level data, subscription events, or a second system like an ERP feeding the same records
- Custom build: multi-store consolidation, B2B custom objects, ERP-driven pricing visible in the CRM, or sync logic with business rules no connector exposes
Sequencing advice that saves budgets: run the native app first even if you know you will outgrow it. It establishes the baseline sync, exposes your actual gaps within a few weeks, and lets you scope middleware around specific missing fields instead of paying to rebuild what the free app already does. Our integrations practice scopes it exactly that way.
06. The B2B Layer: Companies, Deals, and Wholesale Orders
For D2C, the integration is mostly a marketing engine. For B2B merchants on Shopify Plus, it becomes an account management system, and the configuration decisions change.
- Shopify B2B company records map to HubSpot companies, so wholesale accounts exist as accounts, not as a pile of individual buyer contacts
- Wholesale orders can be routed into the deals pipeline with stages and owners, giving account managers pipeline visibility on reorders, not just a commerce log
- Order recency and account-level spend feed workflows that flag accounts drifting below their historical order frequency before the quarter shows it
- Support tickets in Service Hub attach to the same account record, so the person answering a wholesale complaint sees order history without asking
This is the architecture we build for distributors and manufacturers: Shopify Plus for ordering, HubSpot for account management, and the integration wired for B2B objects rather than left on D2C defaults. See our B2B wholesale services and Service Hub onboarding for the two halves of that build. If you are layering AI on top afterward, our HubSpot Breeze AI guide covers what Breeze can actually do with synced store data.
07. Frequently Asked Questions
Does HubSpot integrate with Shopify?+
What data syncs between Shopify and HubSpot?+
How long does the Shopify HubSpot sync take?+
Does the integration sync abandoned carts?+
Do Shopify orders become deals in HubSpot?+
What are the limitations of the native Shopify HubSpot integration?+
When do I need middleware or a custom integration instead?+
Is your Shopify data actually reaching HubSpot?
eSolve is a Shopify and HubSpot partner agency. We implement, audit, and extend Shopify-HubSpot integrations for D2C and B2B merchants, from native setup to custom middleware. Book a 30-minute assessment and find out what your sync is silently missing.