A retail data migration
Shopify POS→Lightspeed Retail R Series
We review how Shopify products and options should become R Series items and matrices. The mapping covers the agreed SKUs, barcodes, prices, costs, and customer fields.
Plan this migration Data migration: $2,999. Scope confirmed before booking.The records we review.
- Products & variants
- Style, size, and color relationships
- SKUs & barcodes
- Identifiers used across your stores
- Customers
- Supported fields and matching decisions
- Opening inventory
- Quantities mapped to each location
- Existing destination records
- Products and customers already in your next system
The decisions
we make first.
Source access
Review representative exports and the available extraction method.
History & balances
Assess sales history, gift cards, loyalty, and credits separately.
Test & acceptance
Agree the records and checks before the final transfer.
Build the right product structure
We review how Shopify products and options should become R Series items and matrices. The mapping covers the agreed SKUs, barcodes, prices, costs, and customer fields.
If Shopify will continue running your ecommerce store, we also identify which catalog and inventory connections need attention before changing the POS.
Make the inventory transfer deliberate
R Series’ documented spreadsheet workflow adds quantity on hand to existing inventory. We therefore confirm whether the destination contains existing stock and plan the import accordingly.
We test representative variants and location quantities before the final transfer. Existing gift cards, store credit, and sales history need separate review because standard data imports do not reproduce every record or workflow.
Confirm a defined migration
The data migration service costs $2,999 for the agreed scope. A sample review establishes the supported records and any exceptions before booking, followed by preparation, a test, the production transfer, and reconciliation.
Directional data plan: Shopify POS to Lightspeed Retail R Series
This is a planning matrix for assessment, not evidence of a completed transfer. The included fields and receiving method are confirmed from authorized samples before booking.
| Dataset | Source evidence | Receiving decision and acceptance |
|---|---|---|
| Products and variants | Product/variant CSV, customer CSV and inventory export by location; keep the files separate. | R Series item import template; customer and balance workflow confirmed separately. |
| Identifiers and existing records | Keep Shopify IDs and handles if the online store remains; contact CSV does not carry order history. | Test matrices and whether stock is added to existing quantities before importing production data. |
| Customer contacts | Obtain a separate customer sample with source IDs and duplicate candidates. | Confirm supported fields and match rules; reconcile created, matched and rejected profiles. Contacts do not establish transferred balances. |
| Opening inventory | Identify each source store, quantity state and export time. | Map each store to the receiving location and compare each included variant/location pair after the test. |
| History and liabilities | List required receipts, gift cards, credit, loyalty and open orders separately. | Approve a specific native method, usable archive or exclusion for each. Do not infer support from the catalog import. |
Shopify variants into R Series matrices
Define how each Shopify product and option combination becomes an R Series matrix item. Test the difference between an empty destination and an item update; do not use a quantity-adding import as an unexplained replacement of opening stock.
Acceptance before production
Choose a full style with several variants, an unusual barcode, an existing customer and stock in two locations where relevant. Record expected grouping, identifiers and quantities before loading it. Compare the returned destination records with the source crosswalk, resolve rejected rows and have the retailer approve exceptions.
Agree the final snapshot, trading changes and recovery action before the production transfer. Hardware, staff training and ongoing ecommerce or accounting connections have separate implementation owners. Correction responsibilities and support duration belong in the written scope.
Official references
Your systems. Your next chapter.
From the first export to the final review.
Tell us where your data is today, and where you’d like to go. We’ll help you understand the next step.
Check my migration Retail data migration for $2,999. Scope confirmed before booking.