A retail data migration
Lightspeed Retail X Series→Runit
We review your X Series products, variant relationships, identifiers, customer records, and location inventory against the requirements of the proposed Runit setup.
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.
Map products to your next retail setup
We review your X Series products, variant relationships, identifiers, customer records, and location inventory against the requirements of the proposed Runit setup.
The first step is a sample review. We confirm the available exports, destination fields, and inbound method before accepting the migration.
Keep customer balances visible in the plan
In X Series, gift cards, loyalty, and store credit follow different workflows. Store credit is not included in a regular customer export, so a contact list alone is not a complete record of customer balances.
We identify the additional reports or vendor assistance needed, then agree how each dataset will be transferred or retained. Historical sales also require separate assessment.
A clear migration scope
The $2,999 flat fee covers the confirmed data migration scope. Your plan includes preparation, a test import, the final transfer, and reconciliation, with responsibilities for Runit implementation and existing integrations made clear before the move.
Directional data plan: Lightspeed Retail X 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 | X Series products and variant identity with outlet stock; separate customer and liability records. | Vendor-confirmed receiving fields and import method, agreed with the Runit implementation owner. |
| Identifiers and existing records | Retain source IDs, grouping fields and outlet names; verify export coverage against source counts. | 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. |
X Series variants into Runit styles
Retain the source X Series IDs, SKUs and outlet map. Confirm the Runit inbound method and grouping requirements with the implementation owner before committing to a catalog transfer. Treat X Series credit, loyalty and gift cards as separate obligations.
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.