Business Systems
Architecting a Single Customer View Across HubSpot, Shopify, and Legacy Billing Systems
Learn how to build a unified customer profile across Shopify, HubSpot, and legacy billing tools using primary keys and clear conflict rules.
Lubili2 min read
Sarah runs a business that sells commercial equipment online and services client contracts offline. Her team uses Shopify for online orders, HubSpot for managing leads, and an older legacy billing system for corporate invoices. Because records live in three different places, calculating real customer lifetime value or checking support history is difficult. Building a single customer view across HubSpot, Shopify, and legacy billing systems solves this problem by merging fragmented data into one reliable profile.
Establishing a Primary Key Strategy
To merge records from three separate tools, you must uniquely identify every buyer. Email addresses work for simple online orders, but corporate clients often use different emails for purchasing, support, and billing.
Instead of relying only on email, create a master customer identification strategy. You can store a custom field named master_customer_id across all three platforms.
- Shopify: Store the master ID inside customer metafields.
- HubSpot: Store the master ID inside a custom contact property.
- Legacy Billing: Store the master ID inside account reference numbers.
When a buyer enters any platform, your integration layer checks for an existing record. If no match exists, it assigns a new unique identifier. This prevents duplicate profiles when a client buys an item on Shopify using a personal email and signs a contract using a work email.
Setting Field-Level Conflict Resolution Rules
Data conflicts happen when different systems store different values for the same customer. For example, Shopify might hold an old shipping address, while HubSpot holds an updated office address.
You resolve conflicts by assigning a single source of truth for every data field. Never allow systems to overwrite each other without clear rules.
HubSpot should own contact names, lead status, and marketing preferences. Shopify should own recent shipping addresses and online purchase activity. Your legacy billing system should own corporate tax numbers, formal payment terms, and total invoiced balances.
System integrations fail when you try to sync every field everywhere. Define one authoritative system for each data point and limit data flow to that direction.
Syncing a Single Customer View Across Systems
You do not need an expensive enterprise platform to sync records. A lightweight automation script or middleware server can listen for updates using webhooks.
When a customer places an order in Shopify, a webhook notifies your integration service. The service reads the master_customer_id, applies your field rules, and updates HubSpot and your legacy accounting database. Support agents in HubSpot can then view the full history of online orders alongside legacy invoices without switching tools.
Audit your existing fields in Shopify, HubSpot, and your billing software today. Draw a clear chart showing which system owns each field before writing your first integration script.