Lightspeed Retail S Series→Lightspeed Retail X Series

Review the Lightspeed Retail S Series source

S Series/ShopKeep item-list or variant export with explicit filters, columns and location scope; customers require a separate method.

S Series is not R Series or X Series. Preserve Item UUID and variant relationships and do not substitute another Lightspeed edition’s template.

Record the original identifiers, account/edition, included stores, extraction time and any source issues. Preserve an untouched original and verify that files or responses include the full intended record set.

Establish the Lightspeed Retail X Series receiving method

X Series standard/variant template with explicit new/existing IDs, outlets and customer requirements.

Product identity rules and grouping differ from the source. Standard bulk historical-sales import is limited and cannot be inferred from a product load.

Agree create, match and update behavior before preparing a full file. Keep a source-to-destination identity crosswalk rather than placing unrelated internal IDs into receiving fields.

Directional data plan

Proposed representative test

Use an S Series variant family, an archived item and stock from each included location. In Lightspeed Retail X Series, also check a variant family, an existing product link and stock across two outlets. These are illustrative planning cases. Write expected identities, grouping and quantities before the sample and compare returned records with the approved map.

Investigate rejected rows, changed identities and stock differences. If history or balances are included, test their side effects separately. Record trading changes after the inventory snapshot and approve exceptions before the launch milestone.

Confirm before booking

• Confirm complete S Series product/variant export and customer access, map Item UUID/grouping explicitly and establish the destination’s independent quantity/matching method.
• Confirm grouping and receiving-ID rules, the customer method, outlet quantities and individual history/balance outcomes.
• Record exact editions, full authorized access, source data coverage, existing destination records and the approved included field map.
• Agree separate outcomes for history, gift cards, credit, loyalty and open commitments; complete a controlled representative test and retailer acceptance before launch.

Check my migration with the actual editions, stores and required records. The final scope follows the access and method review; no pre-existing implementation or universal data support is implied.

Official references

• Lightspeed S Series filtered inventory exports
• Lightspeed S Series variant update rules
• Lightspeed X Series product importer
• Lightspeed X Series bulk historical-sales restriction

What the vendor documentation establishes

S Series stock export with variants: Export includes variant rows and Item UUID, which is a source identity, not a Shopify destination ID.

S Series customer export: Export Customers is a separate BackOffice operation and includes source Customer Record ID and contacts.

S Series Export Center: Customer List and gift-card/deposit exports are not covered by Export Center; obtain them separately.

X Series product import: Product and variant imports have ID/handle/SKU rules. Shopify-linked handles need preservation; receiving stock and existing catalog state must be checked independently.

X Series customer import and update: Customers have a CSV/XLSX import with column mapping and conflicts. Changing customer_code in the spreadsheet creates duplicates instead of renaming the code.

X Series customer export: Export list may be filtered; accounts exceeding 1,000 customers need the linked full-list procedure. Do not mistake the displayed subset for a complete export.

Documented workflow for this direction

Prepare the Lightspeed Retail S Series source

Obtain Stock Items Export with Variants and Export Customers separately. Retain Item UUID and Customer Record ID in the crosswalk. Export Center does not supply every customer, gift-card or deposit dataset.

Load the Lightspeed Retail X Series records

Use the X Series product and customer import templates. Preserve Shopify links where present. Do not change customer_code as an update shortcut. Check destination quantities and import results per outlet before accepting the stock load.

Validate this retailer’s relationships

Keep the S Series UUID crosswalk separate from X Series IDs and handles. Group only the retailer’s actual sellable variants, preserve barcode text and inspect existing Shopify links before creating X Series families. Customer codes and balances require separate decisions.

Obtain authorized samples securely, agree source corrections and exclusions, and compare destination identities, stock and rejects with expected results before launch. These are documented planning methods, not evidence of prior Sqquid delivery. History, orders and liabilities need a separate approved method or archive.