A retail data migration

Lightspeed Retail X Series→Shopify POS

Moving from Lightspeed Retail X Series to Shopify POS starts with a sample review of variant options, outlets, customer records, and separate balance exports. The plan must show how those records will fit Shopify POS 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 X Series to Shopify POS

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.	Current Shopify product CSV or eligible migration app; customer CSV and inventory workflow are separate.
Identifiers and existing records	Retain source IDs, grouping fields and outlet names; verify export coverage against source counts.	Inspect existing products before selecting create/update behavior; history requires another method.
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 outlets into Shopify locations

Export the intended X Series products and preserve variant grouping and outlet stock. Decide whether Shopify already has linked products; inspect handles and destination IDs before loading another catalog. Use the current Shopify method approved for this account.

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

Documented workflow for this direction

Prepare the Lightspeed Retail X Series source

Preserve product handles, sellable variant rows and outlet quantities; export customers separately. Reconcile filtered exports, including the vendor’s full-list procedure above 1,000 customers.

Load the Shopify POS records

Prepare the current product CSV, customer CSV and location-inventory workflow separately. Compare existing handles and variant IDs before creating or updating records; do not infer order or balance transfer from a contact import.

Shopify’s Lightspeed guide documents a CSV path independently of the early-access migration app. Confirm app eligibility only if that app is selected; it is not a prerequisite for assessing the documented CSV approach.

Agree this retailer’s acceptance

Choose the retailer’s own representative catalog, barcodes, customer matches and any open orders after arranging secure access. Approve the included fields, unsupported records, destination baseline and stock cutoff in writing. Compare expected and returned identities, quantities and rejects before launch; repeat loads need an explicit recovery plan. These documented methods support route planning, not a claim of previously tested delivery or universal data compatibility.

Additional 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.