Lightspeed Retail Migration: Move Catalog & Order Data Without Losing Trust
Migrate into Lightspeed Retail with an inventory, field map, pilot import, dual-run week, and validation — so history survives and operators trust the new system.
Quick answer
Migrate into Lightspeed Retail with an inventory of items, inventory, customer directory, and location settings, a field map, a pilot import, a dual-run week, and validation with the people who live in the data — so history survives and the team trusts the new system.
- Inventory source objects
- Map fields before bulk load
- Pilot one site / one role / one team
- Dual-run for a week
- Validate with sceptic users
Lightspeed Retail migration rules
- Inventory first — Typical objects: items, inventory, customer directory, and location settings.
- Pilot beats big-bang — Prove a small Lightspeed Retail import before you move everything.
- Integrations after the pilot — Research names PayPal, QuickBooks, Xero, and Zapier on the Lightspeed Retail side — confirm the connectors your commerce loop depends on.
- Do not migrate the wrong job — Lightspeed Retail is omnichannel POS + online store. Do not import a CRM pipeline or a marketing course catalogue and expect it to become omnichannel POS + online store.
Lightspeed Retail migration map
1. Inventory and map
List items, inventory, customer directory, and location settings. Map required fields and owners. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/lightspeed-retail/. Worked example: Harbor Retail (specialty store adding omnichannel) discovers duplicate SKUs or customer IDs in the spreadsheet before the first import — and fixes identity before volume.
2. Pilot import
Import one site, one role, or one team. Run ring an in-store sale on X-Series, sync the SKU to Lightspeed eCommerce, and see inventory match online on the pilot set. Worked example: Harbor Retail (specialty store adding omnichannel) will not schedule a cutover until the pilot can a store associate rings a sale and the website stock updates without a spreadsheet.
3. Dual-run and cutover
Run old and new in parallel for a week. Spot-check records sceptic users care about, then freeze the legacy source. Worked example: Harbor Retail (specialty store adding omnichannel) keeps the old store or spreadsheet until Lightspeed Retail matches for seven consecutive days.
Lightspeed Retail checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1Inventory source objectsitems, inventory, customer directory, and location settings
- 2Run a pilot importOne segment first; fix mapping before bulk.
- 3Validate with operatorsSpot-check records they care about before cutover.
4. Inventory what must move into Lightspeed Retail
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Brick-and-click retailers who need POS + inventory as the system of record migrates active records only and archives the rest as read-only exports.
5. Run parallel cutover with a rollback path
Keep the old system read-only until Lightspeed Retail passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Brick-and-click retailers who need POS + inventory as the system of record caps parallel run at two weeks with daily checkpoint notes.
6. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists PayPal, QuickBooks, Xero, and Zapier for Lightspeed Retail. Confirm which are native vs API before go-live.
7. Inventory what must move into Lightspeed Retail
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Brick-and-click retailers who need POS + inventory as the system of record migrates active records only and archives the rest as read-only exports.
8. Run parallel cutover with a rollback path
Keep the old system read-only until Lightspeed Retail passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Brick-and-click retailers who need POS + inventory as the system of record caps parallel run at two weeks with daily checkpoint notes.
9. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists PayPal, QuickBooks, Xero, and Zapier for Lightspeed Retail. Confirm which are native vs API before go-live.
10. Inventory what must move into Lightspeed Retail
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Brick-and-click retailers who need POS + inventory as the system of record migrates active records only and archives the rest as read-only exports.
11. Run parallel cutover with a rollback path
Keep the old system read-only until Lightspeed Retail passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Brick-and-click retailers who need POS + inventory as the system of record caps parallel run at two weeks with daily checkpoint notes.
12. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists PayPal, QuickBooks, Xero, and Zapier for Lightspeed Retail. Confirm which are native vs API before go-live.
Frequently asked questions
Can we skip the dual-run?
Only if the dataset is tiny and reversible. Most SMB/mid teams regret skipping a week of parallel use.
What if history will not map cleanly?
Import active records first. Archive messy history as files rather than poisoning the new system of record.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.