Bring supported Shopify contacts, products, collections, orders and transactions into the same CRM used for customer communication and automation. This guide separates historical import from ongoing synchronization and shows how to use purchase data without overwriting trusted customer information.
Open Shopify under Settings and Integrations, enter the store name, select the historical records to import, choose the data and events that should keep syncing, then authorize the current OAuth app in Shopify. Test one existing customer and one new paid order before launching workflows.
Go to Settings and Integrations, locate Shopify and start the connection. New connections use OAuth, so do not follow obsolete custom-app token instructions.
Enter the store name or the identifier from the myshopify.com URL. Confirm the store and business entity before authorizing access.
Select only the contacts, products, collections, orders and transactions required for CRM history. Estimate volume and test in a controlled window.
Enable the supported records and events the CRM must continue receiving. Treat this separately from the one-time historical import.
Review the requested permissions in Shopify and install the app. Existing working legacy connections should not be disconnected without a migration plan.
Confirm contact matching, order values, products, transaction status and purchase-history fields. Then test each workflow with a real test order and refund or cancellation path where relevant.
Trigger
A supported first completed-order event
Actions
Result
A buyer receives the right next step while the CRM records the commercial context.
Trigger
Lifetime value or order count reaches the business threshold
Actions
Result
High-value customers receive differentiated service based on synced purchase history.
Trigger
Last-order date exceeds the approved inactivity period
Actions
Result
Reactivation uses purchase context and respects eligibility rather than broadcasting to every contact.
Confirm the Shopify session, store identifier and business account before authorizing again.
Review the selected import elements, date or record limitations and the import status separately from live synchronization.
Some standard contact values may fill only when the CRM field is empty. Review field ownership before forcing updates.
Use order or transaction ID as the event key and distinguish created, paid, fulfilled, refunded and cancelled states.
Connectors, events, actions and usage charges can vary by plan, account and region. Verify the options shown in your account and test them before publishing.
Supported synchronization can include contacts, products, collections, orders, transactions and selected ecommerce events. Available options should be confirmed in the connection screen.
No. Current new connections use Shopify OAuth. Existing working legacy custom-app connections should be changed only with a deliberate migration plan.
Yes. Supported order and payment events and synced purchase fields can be used for segmentation and workflows such as onboarding, retention and reactivation.
Retain Shopify Customer ID, normalize email and phone, document the contact match rule and test an existing customer before importing the full history.
Connect the event to an owner, next action and outcome, then test it before launch.
Discuss your integration.png){kind=logo}