A retail data migration
Lightspeed Retail R Series→Runit
Moving from Lightspeed Retail R Series to Runit starts with a sample review of item matrices, custom SKUs, vendor details, and stock by store. The plan must show how those records will fit Runit 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 R Series to Runit
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 | R Series inventory export with matrix/item identity and store quantities; customer extraction reviewed separately. | Vendor-confirmed receiving fields and import method, agreed with the Runit implementation owner. |
| Identifiers and existing records | Retain matrix and individual item IDs so size/color grouping can be reconstructed and checked. | Inbound catalog method, matching behavior and quantity semantics need explicit confirmation. |
| 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. |
R Series matrices into Runit styles
Preserve the R Series matrix and item identifiers during extraction. Ask the Runit implementation owner to confirm how style, size and color fields are received, including how existing destination styles are matched. An outbound report does not establish an inbound Runit importer.
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.