HubSpot Shopify integration: records and permissions
Assess a HubSpot Shopify integration. Verify supported records, sync direction and consent fields, then check duplicates, changed orders and staff access.
- Published
- Last updated
Yes, the HubSpot Shopify integration uses HubSpot’s Shopify Data Sync app to copy store records into its customer relationship management (CRM) system. Some records support two-way sync, while orders flow from Shopify to HubSpot. Set ownership for each field before enabling writes back to the store. A copied customer record doesn’t establish permission to send marketing.
Identify the supported HubSpot connection
Use the Shopify Data Sync connection for a new setup. HubSpot’s connection instructions list all HubSpot plans, with extra subscriptions for specific features. Installation requires Super Admin or App Marketplace permissions. Custom mappings require at least Data Hub Starter. Installing the app also adds HubSpot’s tracking code to the store.
Keep the connector name and connected store URL in your setup record. Match the store to the intended HubSpot account before authorising access. Review the requested permissions with the person responsible for customer data. That decision covers the records the app can access, separately from what a staff member can view.
Older instructions can describe orders as deals in an ecommerce pipeline. HubSpot’s earlier Academy demonstration shows that model. The Data Sync connection uses order and cart objects instead. A deal-based report or workflow needs its own migration check. Changing the connection doesn’t prove that the old automation follows the new records.
Connect the app through HubSpot’s Marketplace, then configure each object under Connected Apps. HubSpot’s data sync setup guide separates installation from enabling sync. Select the direction and conflict winner before starting the initial import. Begin with filters that isolate a small sample you can inspect.
Map the store and CRM records
Map each object to the record your staff will actually use. An order association must lead to the right customer, and a product description must identify the purchased variant. A connection-level success status can hide a mistake in either relationship.
Object directions
| Shopify record | HubSpot destination | Supported direction |
|---|---|---|
| Customer | Contact | Two-way configuration available |
| Company | Company | Two-way configuration available, with Shopify Plus required |
| Product | Product | Two-way configuration available |
| Order | Order | Shopify to HubSpot |
| Abandoned checkout | Cart | Shopify to HubSpot |
| Product variant | Separate product linked to its base product | Shopify to HubSpot through variant sync |
HubSpot matches contacts by email and base products by name. Orders and carts don’t automatically merge duplicates. Shopify metafields aren’t supported by the Data Sync app. Preserve source identifiers in your reconciliation record so staff can distinguish matching names from matching records.
Product variants need a separate setup. HubSpot’s variant sync instructions require product sync first. Each variant becomes a product record, and later changes flow from Shopify.
The configuration can match existing products by stock keeping unit (SKU). Use that option deliberately when you already have variant records. A medium green shirt and a large green shirt must remain distinguishable after sync.
For each mapped field, write down the source, destination and person allowed to change it. Select the conflict winner for two-way fields. HubSpot’s field mapping guidance explains that field types and direction constrain a mapping. A matching label alone doesn’t establish compatible values. Compare a status value in both records before using it in an automation.
The initial data sync indexes existing records, then processes later changes. Choose the historical sample through the available filters instead of assuming the connector starts with new orders only. Include a previously imported order in that review. Record its Shopify identifier beside the HubSpot identifier before allowing a wider import.
Keep customer context and permission separate
Customer-service staff need the order context to answer a question, while marketing staff need a separate record of messaging permission. Keep those responsibilities distinct in the field map and staff access settings.
Consider a fictional customer who asks why a green shirt hasn’t arrived. The service agent opens the associated HubSpot order and checks its Shopify source. They compare the purchased variant with the current fulfilment information in Shopify. If the synced information is stale, they use the source order to investigate before replying.
The agent records the question and assigns the follow-up to the staff member responsible for delivery enquiries. The handover includes the original order identifier and the action already taken. It also names the next action, such as investigating a missing dispatch scan. This is a service procedure your team sets up. Syncing an order doesn’t create that procedure automatically.
Separate the customer fields
| Information | What it answers | Suggested owner |
|---|---|---|
| Order and service history | What did the customer buy, and what needs resolving? | Customer-service team |
| Marketing contact status | Is this contact included in HubSpot’s marketing-contact category? | CRM administrator |
| Communication subscription | What messages has this email address subscribed to? | Marketing permission owner |
| Customer identity correction | Which person owns these records? | Staff member authorised to resolve identity conflicts |
HubSpot’s subscription management guidance ties email subscription preferences to the email address. The status persists when a contact is deleted and recreated with the same address. Inspect the subscription history before changing permission. A completed purchase or a newly synced contact is insufficient evidence for a new subscription.
Incorrect: marking every customer as subscribed because their order appears in HubSpot. Correct: retaining the customer’s recorded subscription choice while staff handle the order enquiry.
Test an existing contact alongside a duplicate before widening customer sync. Compare the order associations and subscription history before choosing the surviving record. For a changed email address, verify the customer’s identity through your store procedure. Then inspect both linked records and the new address’s subscriptions. Don’t carry permission across solely because two records share a name.
Verify changes and failures
Verify the connection with source records and destination records side by side. HubSpot documents changes syncing within 10 minutes after the initial import. Record when the source changes so a delayed update is visible.
HubSpot’s integrations sync card shows the linked record, sync status and last update. Its statuses distinguish a record that is excluded from one that has an error or has sync turned off. Use that difference to choose the recovery action.
Connection acceptance checks
| Check | What to inspect | Passing outcome |
|---|---|---|
| Changed order | Original Shopify order and its HubSpot counterpart | The configured fields update on the existing associated order |
| Partial refund | Shopify refund details and mapped order fields | Staff can identify the source refund without treating a stale copied total as proof |
| Delayed update | Source change time, sync card and sync health | The delay has a visible cause and the existing record catches up |
| Revoked access | Connection status after a controlled access removal | An administrator can identify the access failure and restore the intended connection |
| Failed mapping | Rejected record and property types | A corrected mapping updates the intended record without a second import |
| Changed email | Both customer records and subscription histories | The intended identity and messaging preferences remain distinct |
Run access removal only in a test setup or an agreed maintenance window. Keep the affected IDs before retrying a failed record. Correct the field or permission that caused the failure, then confirm the same record updates. A bulk reimport can obscure the original fault and create competing records.
Keep Shopify’s refund detail available to service staff. Don’t treat an order object as a complete refund ledger or assume a refund object transfers alongside it. Test the mapped fields your team relies on before using them to promise a customer that money has been returned.
Assign one administrator to connection access and one CRM owner to mappings and duplicate correction. Give the marketing permission owner control over subscription changes. Record the plan requirements and included features when approving the connection budget. Separate that subscription cost from implementation and ongoing data correction.
Finish acceptance with one changed order and its customer association. Let the staff member who handles the next enquiry confirm they can find the current source record and understand what action remains.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.