A retail data migration
Lightspeed Retail X Series→Lightspeed Retail R Series
Moving from Lightspeed Retail X Series to Lightspeed Retail R Series starts with a sample review of variant options, outlets, customer records, and separate balance exports. The plan must show how those records will fit Lightspeed Retail R Series before a transfer is accepted.
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.
Directional data plan: Lightspeed Retail X Series 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 | X Series products and variant identity with outlet stock; separate customer and liability records. | R Series item import template; customer and balance workflow confirmed separately. |
| Identifiers and existing records | Retain source IDs, grouping fields and outlet names; verify export coverage against source counts. | 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. |
X Series variants into R Series matrices
Separate X Series grouping fields from sellable SKUs and map the result to R Series matrices. R Series item-import stock behavior requires an explicit before/after check; a repeated quantity addition must not be mistaken for setting opening inventory.
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.
Confirm the route before booking
The standard fee is $2,999 USD for the confirmed scope. Check my migration with the exact source and destination editions, stores and required records. Authorized extraction access, the receiving method and an accepted sample remain prerequisites; this page does not establish an implemented route.
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.