Does customer purchase history and loyalty-points balance transfer from Lightspeed Retail to Shopify, or does that data get lost?
Short answer
Purchase history does not transfer with Lightspeed Retail customers to Shopify. Shopify's customer file skips Total Spent and Total Orders (Shopify Help Center, October 2026), and Lightspeed's integration cannot move sales history (Lightspeed X-Series support). Orders need a third-party import app (Shopify Help Center). Loyalty balances skip the file, so X-Series loyalty dollars can be loaded as Shopify store credit (Shopify developer docs).
- Spend totals in Shopify's customer file
- Not importedShopify's field reference says of Total Spent and of Total Orders that the column isn't imported with customer details (October 2026).Source: Shopify Help Center (Importing and exporting customer lists)
- Sales history through Lightspeed's sync
- Not transferableLightspeed says it isn't currently possible to transfer Retail POS sales history to Shopify through its integration (October 2026).Source: Lightspeed X-Series support (About the Shopify integration)
- Order import apps Shopify names
- Matrixify, LitExtension, EZ Importer, Cart2CartMatrixify: Basic $20 a month at 1,000 orders per file, Big $50 at 10,000, Enterprise $200 unlimited; 4.9 stars on 1,744 reviews (October 2026).Sources: Shopify Help Center (Migrate from Lightspeed); ITissible (Matrixify: Data Export Import on the Shopify App Store)
- Imported orders in US tax insights
- Counted only with a shipping addressShopify leaves an imported order without a shipping address out of its US tax liability insights, so walk-in sales stay out (October 2026).Source: Shopify Help Center (Review your US tax liability insights)
Deploi’s call
Purchase history does not transfer with the customer (per Shopify's Help Center and Lightspeed, October 2026), so treat it as an archive problem, not a migration problem. Import the returns-policy window into Shopify so the service desk can do its job. Export the rest to storage you control. Stop paying migration prices for data whose only consumer is a quarterly slide. Loyalty balances are a separate move: Lightspeed X-Series loyalty dollars land as Shopify store credit (per Shopify's developer docs, October 2026).
BuyImport the returns window with an app when
- Your service desk looks up past purchases by customer.
- Returns against an older purchase fall inside your returns policy.
- Marketing segments on lifetime value, which our record on keeping store and online data in step lists among the gains of one customer record.
WaitKeep older history as files you control when
- Nobody has named who will use the history.
- The orders fall outside your returns window.
- Product codes will change after cutover, which would orphan old line items.
Basis: Build or Buy POS-Ecom Coherence on Shopify?, our Build vs. Buy decision record, scored WAIT.
What happens to purchase history when customers move from Lightspeed to Shopify?
Purchase history stays behind when customers move from the Lightspeed Retail point of sale (POS) to Shopify: the customer record moves, and the orders do not. Lightspeed says of its own Shopify integration, "It isn't currently possible to transfer your Retail POS sales history over to Shopify" (Lightspeed, October 2026). Shopify's customer comma-separated values (CSV) file has Total Spent and Total Orders columns. Its field reference says of each: "This column isn't imported with customer details" (Shopify Help Center, October 2026).
That is the trap. A spreadsheet that maps Lightspeed's lifetime spend onto Total Spent validates, imports without error and produces a customer list where every top customer shows $0.00 spent. Nothing failed, so nobody looks. The same Shopify page adds: "You can't import order information using a customer CSV file." So order history is its own import, which the full Lightspeed cutover plan budgets as a separate project.
Which customer data survives the move from Lightspeed, object by object?
Contact details, tags, marketing consent and supported metafields survive in Shopify's customer file; spend totals, orders, loyalty balances and passwords do not.
| Object | In Shopify's customer file? | How it moves, if at all |
|---|---|---|
| Name, email, phone, default address | Yes | Customer file, or Shopify's Store Migration app, in early access for Lightspeed |
| Tags | Yes | Comma-separated; tags aren't case sensitive |
| Email, text message and WhatsApp consent | Yes, as yes or no fields | Carrying consent forward is a legal question, not a file question |
| Customer metafields | Yes, for supported types | The metafield must already exist in the Shopify admin |
| Total Spent and Total Orders | No | Shopify derives them from orders; the columns are not imported |
| Orders | No | Third-party import apps only |
| Loyalty balance | No | Lightspeed X-Series exports loyalty_balance; a dollar balance can be loaded as Shopify store credit through Shopify's application programming interface (API) |
| Passwords | No | Shopify's customer accounts sign in with a one-time code instead |
Passwords never move, because they are encrypted outside Shopify (Shopify Help Center, October 2026). On Shopify's customer accounts that costs little: customers get "a one-time 6-digit verification code," and "A password isn't required to sign in" (Shopify Help Center). On legacy accounts, invite each customer to create a new password. For loyalty, see where Lightspeed loyalty balances should land.
How much Lightspeed order history is worth importing into Shopify?
Our rule: import only the window your team will be asked about, usually 12 to 24 months matched to your returns policy, and archive the rest as files. Shopify's Lightspeed guide routes order history to third-party apps and names Matrixify, LitExtension, EZ Importer and Cart2Cart (Shopify Help Center, October 2026). Matrixify, an import and export app, holds 4.9 stars across 1,744 reviews. Its Basic plan, at $20 a month, imports 1,000 orders per file. Big, at $50, imports 10,000, and Enterprise, at $200, has no limit (Shopify App Store, October 2026).
So the import is affordable; the question is whether it is worth it. Imported orders serve three uses: customer service lookup, returns against an old purchase, and lifetime-value segments. Our record on keeping store and online data in step lists those segments among the gains of one customer record (checked October 2026). Imported orders are not financial records, because the money already cleared on Lightspeed. Restating it in Shopify creates a reconciliation problem. That is why the window is the returns policy, with everything older stored somewhere that is not a point of sale vendor.
Do imported in-store orders count in Shopify's US tax liability insights?
No: imported in-store orders without a shipping address do not count in Shopify's US tax liability insights. Shopify's guide says "if an imported order doesn't contain a shipping address, then it isn't considered when determining your tax liabilities" (Shopify Help Center, October 2026). The insights count "Transactions that occur within Shopify" and "Orders imported into Shopify that include valid shipping addresses." A walk-in sale at a Lightspeed register has no shipping address, so importing three years of store sales will not move the thresholds Shopify tracks for you, in either direction. That is the right behaviour, and it surprises teams who imported the history to see it there. Check that the import leaves the shipping address empty on store sales, because a copied home address would put a store sale into the insights.
When should you not import Lightspeed order history?
Do not import order history when nobody will use it, when an R-Series export has no priced route, or before the catalog is final, because each turns the import into cost without a user:
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- Migration vendors quote "full customer history" as a line item, and they can deliver the orders. They cannot deliver the derived fields, because Shopify computes those and will not accept them. Ask any vendor quoting lifetime value to state in writing which Shopify field receives it.
- What we tell clients to check first
- Build one VIP segment in the new store before go-live and look at it. The Total Spent column fails silently, because it imports without error and produces a plausible-looking customer list where every high-value customer reads zero. A five-minute check before cutover beats finding it when marketing builds a segment three weeks after.
- What this page adds
- that Lightspeed's own integration cannot move sales history, that Shopify's customer file accepts and then discards the two spend columns most migration plans care about, that passwords never move, and that imported walk-in orders without a shipping address are left out of Shopify's US tax liability insights.
Decision records behind this answer
When this answer changes
- Shopify starts importing Total Spent and Total Orders from the customer file, or adds an order import to the admin.
- Lightspeed's Shopify integration starts transferring Retail POS sales history.
- Shopify changes which imported orders count in its US tax liability insights.
- Matrixify changes its plan prices or its per-file order limits.
- Shopify adds a loyalty or store credit column to the customer file.
Related questions
This follows from How do I migrate from Lightspeed Retail (POS) to Shopify without disrupting in-store sales during the transition?
- What's the migration path for Lightspeed's built-in customer loyalty program if Shopify has no native loyalty equivalent?
Lightspeed X-Series loyalty is a dollar balance, not points, so its closest Shopify home is native store credit (Lightspeed X-Series support, October 2026).
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Shopify Help Center, Importing and exporting customer lists
- Lightspeed X-Series support, About the Shopify integration
- Shopify Help Center, Migrate from Lightspeed
- Shopify blog, Store Migration Shopify App: Import Data (2026)
- Lightspeed X-Series support, Adjusting customer loyalty balances
- Shopify developer docs, storeCreditAccountCredit
- Shopify Help Center, Customer accounts
- ITissible, Matrixify: Data Export Import on the Shopify App Store
- Shopify Help Center, Review your US tax liability insights
- Deploi Build vs. Buy, Build or Buy POS-Ecom Coherence on Shopify?