A retail data migration
Runit→Lightspeed Retail X Series
We inspect representative Runit exports and review how styles, variants, SKUs, barcodes, and customer records will fit Lightspeed Retail X Series.
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.
Start with your real retail data
We inspect representative Runit exports and review how styles, variants, SKUs, barcodes, and customer records will fit Lightspeed Retail X Series.
Your location map identifies which opening quantities belong in each store or warehouse. Any conflicting identifiers or catalog structures are resolved in the plan before the final transfer.
Review balances and history before booking
X Series supports importing gift card numbers and balances, but that does not establish that every source card is compatible. We check the available Runit data and the intended destination workflow.
Loyalty, store credit, open transactions, and historical sales receive separate review. The standard X Series workflow does not bulk import previous POS sales; any proposed API reconstruction needs additional assessment.
Confirm the service and the outcome
The migration costs $2,999 for the agreed scope. After the sample review, your plan defines the included records, test import, final inventory snapshot, production transfer, and reconciliation.
Directional data plan: Runit to Lightspeed Retail X 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 | Account-authorized reports or a vendor-approved data extract; inspect actual style and SKU fields. | X Series product template for standard/variant records; customer and balance workflow reviewed separately. |
| Identifiers and existing records | API documentation is supplied by request; required fields and access are not verified by the public overview. | Use the correct new/existing record ID treatment and verify outlet quantities and product links. |
| 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. |
Runit size and color into X Series variants
Review the full style-to-variant relationship before preparing the X Series product template. Preserve source IDs for reconciliation and agree the receiving SKU rules. X Series history and balances require their own decisions alongside the product import.
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.