CRM 7 min read

Shopify HubSpot Integration Setup: Step-by-Step Checklist (2025)

Step-by-step setup for Shopify HubSpot integration: connect accounts, map data, test sync, and avoid common mistakes. (2025 checklist)

Quick Answers

Do I need developer access to connect Shopify and HubSpot?

Usually no. Most connectors use an in-app OAuth flow. You may need admin permissions in Shopify and the ability to create an API key/token in HubSpot depending on the connector.

What should I test first after enabling the Shopify HubSpot integration?

Create a test order and verify totals, taxes, shipping, discounts, and customer identity fields. Then test a refund to confirm the accounting/CRM/analytics side stays consistent.

Shopify HubSpot Integration Setup is only valuable if the data stays consistent after day 1. This page focuses on the practical steps to set expectations, verify mapping, and keep the integration reliable in 2025.

Shopify
integrates with
HubSpot
CRM 1
TOP PICK

HubSpot CRM

CRM Integration for Shopify
1
4 reviews
Price
Free plan available
Last Updated
2025-12-19

2025 listing snapshot (quick sanity check)

  • Listing rating: 1.0/5 based on 4 reviews (as last recorded).
  • Pricing model: Free plan available (verify current plan details before you commit).
  • Last updated (listing): 2025-06-15.

Prerequisites

  • Admin access to both systems (or the integration app account)
  • A clear decision on what to sync (orders only vs orders + customers + products)
  • A test order you can create/refund without impacting real customers

Step-by-step setup

  1. Install/enable the connector app (or integration method you picked)
  2. Authorize access in Shopify and HubSpot
  3. Choose the sync scope (orders/customers/products)
  4. Set your historical import window (start small: 30-90 days)
  5. Create a test order and verify the data end-to-end

Configuration tips (avoid sync surprises)

  • Start with the minimum fields you need (email, currency, SKU, order totals)
  • Decide how to handle refunds and chargebacks (and test one)
  • If you sell internationally, confirm timezone + currency behavior before launching

How the data flows

  • Make sure status changes are consistent (paid -> fulfilled -> refunded)
  • Confirm how discounts, shipping, and taxes are represented
  • If you use bundles/subscriptions, validate how line items are represented
Data Flow
%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#e0f2fe', 'primaryTextColor': '#0369a1', 'primaryBorderColor': '#0369a1', 'lineColor': '#64748b', 'secondaryColor': '#f0fdf4', 'tertiaryColor': '#fef3c7'}}}%% graph LR A[Shopify Store] -->|Customer Data| B[Shopify] A -->|Order History| B B -->|Segments & Tags| C[HubSpot] C -->|Campaigns| D[Email/SMS] D -->|Engagement| A
Real-time sync Scheduled sync

Launch checklist

  • Run a quick QA: 5-10 real orders across different scenarios (discount, refund, multi-item)
  • Enable 1-2 automations first (don’t turn on everything on day 1)
  • Set a weekly check for errors and duplicates for the first month

Shopify + HubSpot implementation checklist (2025)

This section adds practical “make it stable” steps you can use after you install the app/connector. It’s intentionally lightweight: the goal is fewer sync surprises, cleaner reporting, and easier troubleshooting.

1) Quick setup checklist

  • Permissions first: grant only the scopes you need (orders/customers/products as required) and document who owns the admin credentials.
  • Data mapping: confirm how email, phone, currency, and SKU are mapped between Shopify and HubSpot.
  • Historical import: decide how far back to import orders/customers (avoid importing years of data if you don’t need it).
  • Deduplication rules: pick one unique identifier per object (usually email for customers, order ID for orders) to prevent doubles.
  • Alerts: set a lightweight alert path (email/Slack) for failed syncs, auth expiry, and API rate limits.

2) Data you should verify after connecting

Most integration issues show up in the first hour if you test the right things. Use the table below as a QA checklist (create a test order if needed).

Data objectWhat to checkWhy it matters
CustomersEmail/phone format, marketing consent fields, duplicatesPrevents double messaging and broken segmentation
OrdersOrder total, tax, discount, shipping, currencyKeeps revenue reporting and automation triggers accurate
Line itemsSKU, variant ID, quantity, refunds/returns behaviorAvoids inventory and attribution mismatches
FulfillmentStatus changes + timestamps, tracking numbers, carrier fieldsDrives customer notifications and post-purchase flows
CatalogProduct titles, handles, images, collections/tagsEnsures personalization and reporting match your storefront

3) Automation ideas for CRM

  • Lead capture: new customer/signup → create/update contact in HubSpot with consent fields.
  • Lifecycle stages: first purchase → move contact to customer stage and start onboarding tasks in HubSpot.
  • Support handoff: high-value order → create a task/notification so reps can follow up in HubSpot.
  • Deal signals: repeat purchase or high cart value → trigger sales outreach for B2B accounts.
  • Dedupe rules: standardize email/phone formatting to prevent duplicate records across systems.

API sanity check (Shopify Admin API)

If your integration UI says “connected” but data isn’t flowing, a quick API call helps confirm whether the store is accessible and returning the objects you expect.

# List the 5 most recent orders (GraphQL)
curl -X POST "https://your-store.myshopify.com/admin/api/2025-01/graphql.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"query\":\"{ orders(first: 5, sortKey: CREATED_AT, reverse: true) { edges { node { id name createdAt totalPriceSet { shopMoney { amount currencyCode } } customer { email } } } } }\"}"

Tip: keep tokens/keys in environment variables, and test in a staging store/site before rolling changes to production.

4) KPIs to monitor (so you catch problems early)

  • Sync freshness: how long it takes for a new order/customer event to appear in HubSpot.
  • Error rate: failed syncs per day (and which object types fail most).
  • Duplicates: number of merged/duplicate contacts or orders created by mapping mistakes.
  • Revenue parity: weekly spot-check that Shopify totals match downstream reporting (especially after refunds).
  • Attribution sanity: confirm that key events (purchase, refund, subscription) are tracked consistently.

5) A simple 30-day optimization plan

  1. Week 1: connect + map fields, then validate with 5–10 real orders/customers.
  2. Week 2: enable 1–2 automations and measure baseline KPIs (conversion, AOV, repeat rate).
  3. Week 3: tighten segmentation/rules (exclude recent buyers, add VIP thresholds, handle edge cases).
  4. Week 4: document the setup, create an “owner” checklist, and set a recurring monthly audit.

Related integration guides

Common issues (and fast fixes)

Even “simple” integrations fail in predictable ways. Use this as a quick troubleshooting playbook for Shopify + HubSpot.

  • Duplicate customers/orders: usually caused by running two connectors at once. Pick one source of truth and dedupe by email (customers) and order ID (orders).
  • Currency/timezone drift: confirm store timezone and reporting currency match what HubSpot expects, especially if you sell internationally.
  • Missing permissions: if data is partially syncing, re-check API scopes (orders vs customers vs products) and re-authorize the app.
  • Webhooks not firing: look for blocked callbacks, disabled webhooks, or a stale token. If possible, test with a fresh order and watch for events.
  • Rate limits & delays: large imports or high order volume can queue syncs. Stagger imports, reduce lookback windows, and monitor retry queues.
  • Refund/return mismatch: clarify whether refunds create separate objects or adjust the original order record (finance teams should agree on the model).

Privacy & compliance notes (2025)

Integrations often touch personal data (email, phone, address). Keep this lightweight checklist in mind:

  • Least privilege: only grant the data scopes you actively use; remove unused apps quarterly.
  • Consent fields: treat marketing consent separately from transactional messaging (especially for SMS).
  • Data retention: define how long you keep customer event data, and who can export it.
  • Access review: restrict admin accounts and rotate keys/tokens if staff changes.

Suggested rollout plan

  1. Connect in staging (if possible): validate mapping on a small dataset.
  2. Import a short history window: start with 30–90 days unless you have a clear reason to import more.
  3. Run side-by-side QA: compare a handful of orders across systems (totals, taxes, shipping, refunds).
  4. Go live gradually: enable 1–2 automations first, then expand once you trust the data.

Change control (keep it maintainable)

  • One owner: assign a single owner for the integration (who approves mapping and workflow changes).
  • Log changes: track what you changed (fields, filters, timing) and why, so you can roll back quickly.
  • Monthly audit: re-check scopes, API tokens, and error logs—especially after major store/theme/app changes.

Sources


See also: Main Shopify + HubSpot integration guide.

CRM Integration Comparison

Compare key features across popular crm solutions

FeatureHubSpotPipedriveSalesforceZoho CRM
Free tierAvailable without paymentYesNoNoYes (3 users)
Contact syncCustomer data synchronizationYesYesYesYes
Order historyPurchase data in CRMYesYesYesYes
Abandoned cartCart recovery workflowsYesVia ZapierVia automationVia workflow
Custom fieldsCustom data mappingYesYesYesYes
Bi-directional syncTwo-way data flowLimitedLimitedYesYes

Data based on publicly available information as of January 2026. Features and pricing may vary.