A retail data migration
Lightspeed Retail R Series→Retail Pro
A move from Lightspeed Retail R Series to Retail Pro needs an explicit map from a matrix with several sellable sizes, an existing item and separate store quantities to the receiving records.
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.
Assess the Lightspeed Retail R Series source
R Series inventory and item/matrix identity, with separate customer and liability data.
R Series item imports can add stock to existing quantities. A repeated import must be reconciled rather than treated as a replacement snapshot.
Keep an untouched original and a record of account, edition, location coverage and extraction time. The customer must provide full authorized access and be able to access their own data. Do not infer missing fields or access from a vendor family name.
Plan the Retail Pro destination
Edition-specific Retail Pro receiving specification and resource dependencies, approved by the implementation partner.
Prism initialization/replication tooling is not a universal third-party importer. Subsidiary and item identity must remain distinguishable.
Inspect existing receiving records before choosing create, match or update behavior. An exported internal ID should remain in a reconciliation crosswalk unless the receiving specification explicitly accepts it.
Directional data decisions
| Dataset | Lightspeed Retail R Series evidence to preserve | Retail Pro decision to confirm |
|---|---|---|
| Products and variants | Complete grouping, source IDs, sellable combinations and item status | Equivalent parent/variant structure and supported receiving fields |
| Identifiers and prices | SKUs, full barcode text, unit and price context | Matching rule, permitted identifier representation and accepted price behavior |
| Customer contacts | Source identity and duplicate candidates, separately from liabilities | Receiving method, existing-profile rules and rejected-row report |
| Location stock | Store/warehouse map, quantity type, unit and snapshot time | Correct receiving location and set-versus-add operation |
| History and commitments | Required receipts, gift cards, credit, loyalty and open orders listed individually | Native receiving method, approved transformation, archive or exclusion for each |
A representative test for this direction
Use a matrix with several sellable sizes, an existing item and separate store quantities. In the receiving Retail Pro setup, also inspect a subsidiary-specific matrix and serial-tracked piece with stock at two stores. Use these illustrative examples to plan your project’s sample and agree expected results before a production import.
Write expected identities, grouping and quantities before the sample load. Compare returned records and rejected rows, approve exceptions and capture changes made after the stock snapshot. Test any proposed history or balance operations separately so an item import cannot silently create a second liability or stock movement.
What remains to be confirmed
- Identify Prism versus legacy version, obtain partner-approved extraction/receiving specifications, subsidiary matching and dependent resources.
- Confirm exact source/destination editions, authorized full access, included fields, existing destination records and retailer approval of history/balance treatment.
- No prior Sqquid test evidence was supplied. Run a representative controlled test and record actual results before executing this migration; do not publish an exercised-route or all-data guarantee.
This route remains under review. Request an assessment to establish the actual method and scope before booking. We confirm the exact edition pairing and supported fields before booking.
Official references
Migration scope and responsibilities
The standard migration fee is $2,999 USD for the confirmed scope.
Access to both systems
You must provide Sqquid full authorized access to both systems and be able to access your own data. Arrange access through an agreed secure process. Do not put passwords, API tokens, payment information or customer export files into the general enquiry form.
Source data quality
Sqquid is not responsible for migration errors caused by poor data supplied by the customer. Source issues, proposed corrections and exclusions need to be recorded before the transfer is accepted.
Earlier work and guarantee limits
Sqquid does not guarantee a migration that started before Sqquid was hired. Any guarantee is limited to the data migration work performed by Sqquid and expires on the launch date. Record the agreed launch milestone in the written scope; do not assume post-launch guarantee coverage.
Vendor charges and separate work
Vendor charges are passed to the customer in addition to the confirmed migration fee. POS implementation, hardware, payment setup, staff training and ongoing integrations have separate responsibilities and scope. A Sqquid software subscription is not required for the migration service.
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.