A retail data migration

Lightspeed Retail X Series→Retail Pro

A move from Lightspeed Retail X Series to Retail Pro needs an explicit map from a variant family, an existing product link and quantities across two outlets 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 X Series source

X Series product/variant records and outlet quantities, with separate customer and liability exports.

X Series new-record IDs and product grouping cannot be inferred from source internal IDs. Standard historical sales import is limited; gift cards need a separate workflow.

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 X 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 variant family, an existing product link and quantities across two outlets. 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.

Official references

What the vendor documentation establishes

X Series product import: Product and variant imports have ID/handle/SKU rules. Shopify-linked handles need preservation; receiving stock and existing catalog state must be checked independently.

X Series customer import and update: Customers have a CSV/XLSX import with column mapping and conflicts. Changing customer_code in the spreadsheet creates duplicates instead of renaming the code.

X Series customer export: Export list may be filtered; accounts exceeding 1,000 customers need the linked full-list procedure. Do not mistake the displayed subset for a complete export.

Retail Pro Prism release features: Current release material includes data-import tooling but does not specify the complete external route or establish legacy-version equivalence.

Planning this direction with your project lead

Lightspeed Retail X Series source records

Preserve product handles, actual variant rows, outlet quantities and the separate customer export. Reconcile source filters and the full-customer export procedure rather than assuming the displayed list is complete.

Retail Pro receiving records

For Prism, select the installed server’s documented resources and partner-approved load sequence. Preserve dependent records and plan a controlled window for customer writes. Internal replication or Retail Pro-to-Prism conversion tooling is not proof of a generic external CSV importer; legacy 8/9 needs its own method.

Resolve the transformation before loading

This planning path uses Prism evidence. Preserve subsidiary scope and dependent identity records; do not equate a Prism SID with a Shopify handle, a Lightspeed System ID or another vendor’s item key. Have the partner select the installed-version stock operation and load order. An 8/9 estate is assessed separately rather than assumed equivalent to Prism.

Acceptance is specific to your retailer

Use the representative case above with the retailer’s actual catalog, customer matches and store quantities. Record the intended result, extraction cutoff, rejects and recovery steps before loading. History, gift cards, credit, loyalty and open orders each need an agreed native method, archive or exclusion. Required account access, sample approval and launch milestones are engagement checks—not a claim of past Sqquid delivery or universal support.

Official method references

Migration scope and responsibilities

The standard migration fee is $2,999 USD for the confirmed scope.

Tailored to your retailer data

Every migration is unique. Your catalog, barcodes, orders and customer information are unique and proprietary to your business. We work closely with you to tailor the migration for the best possible outcome, agree the included records and define acceptance checks for your stores.

Routes offered subject to feasibility

We offer the currently listed migration routes subject to retailer-specific feasibility and an agreed scope. This includes POS migrations into Runit.

A project lead for your migration

Sqquid assigns a project lead to each migration. The lead is responsible for migration correctness and oversight of the entire migration dataset, including planning and managing data reversal when needed. The reversal method, dependencies and acceptance checks are agreed for your retailer’s systems and data.

Retailer-provided ERP and finance approvers

For ERP-related work, the retailer must provide an ERP approver and a finance approver. They approve the receiving requirements, included retail data, financial treatment and acceptance results within their responsibilities. Sqquid’s project lead coordinates the migration with them; full ERP implementation remains separate work.

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.

Corrections before launch

We correct errors in our own migration work at no additional charge before launch.

Refunds for errors caused by Sqquid

If a migration error occurs and Sqquid is at fault, we will refund the fees the retailer paid us.

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.