Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/How to migrate products from lightspeed to shopify 2027
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

How to Migrate Products from Lightspeed to Shopify (2027)

Source: Shopify•November 19, 2026 at 12:01 AM

How to Migrate Products from Lightspeed to Shopify (2027)

Migrate product catalog data from Lightspeed to Shopify with steps for export, field mapping, import QA, and go-live planning.

A Lightspeed to Shopify product migration is as much a catalog-cleanup project as a platform move. The process includes exporting product data, restructuring it for Shopify’s format, and checking that variants, images, and inventory still match after import.

For brands selling across retail and ecommerce, catalog accuracy affects much more than just product pages. It affects search filters, merchandising, stock visibility, and the data used across sales channels—all of which, in turn, affect your customers’ ability to find and buy your products.

This guide explains how to prepare the catalog, choose an import method, and launch with fewer product data issues.

Setting up shop has never been easier

Move your store and start selling in record time with Shopify’s migration checklists, platform-specific guides, and simple tools.

Why migrate product catalog data from Lightspeed to Shopify?

Migrating from Lightspeed to Shopify is a change from a fragmented catalog to a single commerce core. It allows brands to treat Shopify as the system of record for products, orders, customers, and inventory.

Fragmented data creates operational friction. Lightspeed documentation indicates that ecommerce settings like visuals, shipping, and marketing are managed separately from the retail back office, which can lead to split product records.

Brands using Shopify’s unified commerce capabilities report up to 150% growth in omnichannel gross merchandise value (GMV) and 22% lower total cost of ownership (TCO). But that’s not all; centralized product data can also help with growth in the following ways:

  • Establishing a central system of record: Consolidating data during a migration removes the need to manage ecommerce settings and retail back-office data across multiple systems. It supports a unified commerce strategy where inventory and product information remain consistent across all touchpoints.
  • Building for modern discovery and AI: Product data performs tasks beyond simply displaying a product page. Shopify Search & Discovery, for example, uses product attributes and image data to provide semantic search results. Clean titles, descriptions, and structured fields help consumers find products through natural language search, so customers are more likely to find your products even if their wording does not match your description very precisely. A migration is also your chance to normalize tags and attributes so your catalog is ready for AI-enhanced search.

A clean migration also leads to operational outcomes such as:

  • Fewer feed errors: Required product data is present and syncs to Google and social channels without disapprovals.
  • Faster merchandising: Retailers bulk-manage product attributes in the Shopify admin to update storefront filters and search recommendations.
  • Reduced support volume: Consumers see the correct images and stock levels for every variant, which reduces order inquiries.
  • Omnichannel consistency: Shopify tracks inventory across multiple store locations and fulfillment apps from one central hub, so customers can have access to in-stock products regardless of where they shop.

Bared Footwear moved to Shopify after their custom-built website and Lightspeed POS system failed to handle high-volume sales.

During one promotion, their payment gateway crashed as 100 people attempted to check out per second. The Lightspeed system could not sync inventory fast enough to keep up with online orders, which forced the brand to close their retail stores during sales to avoid overselling.

By unifying their online and retail operations on Shopify, Bared Footwear now runs concurrent promotions across all channels. Retail stores represent more than 30% of their total annual sales.

Alexandra McNab, chief operating officer at Bared Footwear, says the brand no longer has to deal with inventory discrepancies or maintaining separate systems. "It's a lot easier when all commerce data is flowing through Shopify," Alexandra says.

The future of retail: why unified commerce is no longer optional

New research shows businesses using unified commerce platforms like Shopify POS see 22% better total cost of ownership and 20% faster implementation. Learn what this means for your retail strategy.

Get the report

What product data can (and can’t) be migrated automatically?

Most core catalog fields can be migrated from Lightspeed to Shopify when the source data maps to Shopify CSV requirements.

You can move product titles, descriptions, vendors, tags, and image URLs through the Shopify product CSV. Lightspeed exports contain these core fields, which is why they fall within the automatic migration scope.

These fields typically migrate automatically:

  • Product titles and descriptions
  • SKUs and barcodes
  • Prices and cost
  • Inventory quantities
  • Images (via URLs)
  • Variants (within Shopify’s limits)
  • Tags and categories

However, within these categories there are a few components that may require additional review after migration:

Variant structures that exceed options limits

Shopify supports up to three product options (such as size, color, and material) per product. If a Lightspeed catalog uses a variant matrix with four or more options for variables such as size, color, material, and fit, the data requires restructuring.

Products that exceed Shopify's standard variant limits may require restructuring or a custom migration approach.

Inventory mapped to multiple locations

Shopify also manages inventory by location. Quantities move via CSV, but the data requires validation after import.

Discrepancies can occur when source inventory doesn't map to a specific Shopify location, or when SKUs don't match exactly. Treat inventory as a separate validation workflow to ensure stock levels are accurate after the store goes live.

Broken images URLs and missing variant image assignments

Images move via URLs included in Lightspeed exports. Broken links or missing variant associations require a post-import review.

Image imports can fail if product identifiers like the SKU or handle contain errors. Some variant images require manual assignment if they don't map during the initial import.

Tags and categories

Tags transfer to Shopify, while categories can require remapping to Shopify’s product taxonomy or collection structure.

Lightspeed category structures don't always map to Shopify automated collections or the Shopify category taxonomy. Refine these elements in Shopify so filters and channel data function correctly.

Field-by-field Lightspeed to Shopify migration

Premigration checklist

When migrating your product catalog from Lightspeed to Shopify, the actual technical transfer is just a single step. However, there is word to be done beforehand, because the quality of the source data determines whether the transition is successful.

Data issues can cause replatforming delays that impact revenue and operations. Common import failures stem from formatting errors, missing identifiers, and inconsistent product structures.

This checklist provides important steps to organize your catalog and clean up your data, to reduce errors and prevent delays during the final import.

1. Set a catalog freeze window

A freeze window prevents data drift between the final export and the Shopify import. During this period, staff stop making edits to pricing, descriptions, or inventory levels in the old system. Without taking this step, important late changes can be lost when you go live on Shopify.

When preparing for the freeze:

  • Select a final date and time for all catalog edits.
  • Communicate the restriction to all staff members.
  • Use the resulting export as the baseline for post-import reconciliation.

2. Audit SKUs and barcodes

Duplicate identifiers can cause significant issues because Shopify uses SKUs and barcodes to map variants and inventory. If a file has duplicate rows, the Shopify admin can’t determine which data to prioritize.

Complete these important steps before exporting:

  • Deduplicate all SKUs.
  • Remove repeated barcodes.
  • Flag blank values or temporary placeholders.

3. Standardize naming conventions

Inconsistent data affects how collections and filters work. If naming conventions vary, automated workflows may miss certain items.

Apply these standards to the export file:

  • Use one format for capitalization and punctuation.
  • Standardize option names, such as using only "Color," never "Colour" or "Shade."
  • Normalize vendor values so reporting remains accurate.

4. Assign unique variant SKUs

Shopify has a variant-based structure. This means every combination of size, color, or material needs a distinct identifier.

Reusing a parent SKU for multiple variants stops the system from validating inventory correctly. Ensure every variant has a unique SKU.

5. Define organization rules

Shopify uses product types, vendors, tags, and collections to organize the catalog, and automated collections depend on those values being structured consistently. Define your approved list of product types.

6. Choose your collections strategy

Shopify supports manual and automated collections. Manual collections are useful for hand-curated assortments. Automated (or “Smart”) collections use rules based on tags, price, or inventory to include products.

When choosing a strategy:

  • Use manual collections for specific, curated lists based on your selling strategy.
  • Use automated collections for easy rules-based groups.
  • Avoid recreating old collections if they don't support current goals.

7. Map product metafields

If your store needs product data beyond the standard fields, define metafields up front rather than leaving important attributes trapped in descriptions or spreadsheet notes.

Metafields are designed for specialized information not normally captured in the admin, such as:

  • Materials
  • Dimensions
  • Compatibility
  • Care instructions
  • Part numbers
  • Technical specs

These definitions enforce validation rules and keep values consistent. If a product attribute matters for filtering, merchandising, PDP content, or future integrations, map it into Shopify as structured data.

8. Record baseline counts

Capturing totals before the migration provides a control point. You can compare these numbers against the Shopify import to ensure no data was lost.

Here is a simple template you can use to log premigration counts so that you can compare them after:

Export products from Lightspeed

Exporting product data from Lightspeed is the first step toward migrating to Shopify. This process involves extracting your catalog and inventory records into a format that you can clean and reformat for your new store.

Export from Lightspeed X-Series

Lightspeed Retail (X-Series) allows store owners to export product lists from the catalog. They recommend filtering your list before you begin the export to ensure the file only contains the products you intend to migrate.

To export your products:

  • Navigate to Catalog > Products in the Lightspeed admin.
  • Apply filters to isolate active products.
  • Click Search.
  • Choose Export List.
  • Select your file format and download.

Lightspeed to use XLSX for lists up to 5,000 products to maintain data integrity. For larger lists, they recommend using the CSV format. Using XLSX prevents spreadsheet software from removing leading zeros from your SKUs, which can happen when you open a CSV in Excel. Be sure to check for these changes if you do end up using a CSV.

Export from Lightspeed R-Series

  • From your Lightspeed R-series admin, go to Inventory > Item Search.
  • Filter the data that you want to export using the search filters. Click Search to apply the filters. Only the products in the search are exported.
  • Click Export.
  • Save the file to your computer.

Validate your data with these steps:

  • Confirm row counts. Match the number of rows in your spreadsheet to the product count in your Lightspeed admin.
  • Verify variant rows. Ensure each size or color option appears as a distinct record with a unique SKU.
  • Check column structure. Confirm that required columns like Price, SKU, and Name exist and contain the correct type of data.
  • Audit SKU formatting. Look for SKUs where leading zeros were stripped or numbers were converted to scientific notation.

If you find corrupted rows, edit the product description in Lightspeed and run the export again. Once the file is clean, you can begin the import process in the Shopify admin.

Choose an import method: Shopify CSV vs. Matrixify

Frame the decision between Shopify CSV and Matrixify around your catalog requirements.

A CSV import works for standard structures where the team wants a built-in workflow in the Shopify admin. Matrixify supports migrations that include more than standard fields, like bulk media, metafields, and multi-location inventory.

Shopify CSV for standard catalogs

The Shopify CSV tool handles small catalogs that use standard fields. This native workflow supports core data like titles, handles, descriptions, SKUs, and image URLs. It's a strong option for one-time moves where data already matches Shopify’s requirements.

Use the native CSV tool when:

  • The catalog is small or midsize
  • Products fit the standard Shopify data structure
  • Metafields aren't required for the initial migration
  • The team prefers a built-in Shopify workflow

Matrixify for complex data and bulk updates

Matrixify is often the better choice when migration work includes cleanup cycles, richer product data, or repeated imports. It manages bulk updates for tags, categories, and SKU-based logic, and handles migrations involving large media volumes or store-copy tasks.

Choose Matrixify when:

  • Products have complicated variant logic
  • The migration includes large volumes of images or media
  • Metafields are part of the core product model
  • The team needs to perform repeat imports with corrected data
  • You need detailed job logs and error reviews

Note: Field mapping determines the success of an ecommerce migration. Data quality depends on how legacy structures translate into Shopify’s architecture.

Whether you’re using a CSV or Matrixify, make sure your fields for products, variants, inventory locations, images, and SEO are mapped correctly. If the data doesn't match the expected structure, the import might complete, but your store might experience missing images and broken product relationships.

Import into Shopify and run QA

Quality assurance (QA) is the difference between “imported” and “migrated.”

Product imports can succeed technically while still producing issues with variants, images, or field formatting. Until counts reconcile and images load, the catalog isn't ready for shoppers. Following these steps helps you identify and fix these errors before they affect your launch.

1. Run a controlled test import

Start with a small batch of products rather than your full catalog. A staged approach lets you check publication behavior and states without cluttering your store. If the test products don’t display correctly, you can fix the source file and re-run the process.

2. Reconcile product and variant counts

Count reconciliation is the first gate in the QA process. If the number of products in the Shopify admin doesn't match your source export, data was likely lost or merged.

When validating counts, check these areas:

  • Product totals: Ensure every product handle exists in the new store.
  • Variant totals: Shopify’s CSV structure is row-based for variants and depends on mapped option columns.
  • Missing records: Investigate gaps to see if handles were skipped or duplicates were merged.

3. Audit a 20-SKU sample

Manual reviews catch category-specific issues that automated count checks miss. Inspect at least 20 SKUs across different categories to verify their appearance on the live storefront.

Review samples like:

  • Variant-heavy products: Check that sizes, colors, and materials are mapped to the correct rows.
  • Multi-image products: Confirm that every image is associated with the correct variant.
  • Special attributes: Verify that compare-at prices and custom tags display as intended.

4. Verify multi-location inventory

Pick a sample set of products and confirm their location-level assignments. Verify that your total quantities match and that stock sits in the correct warehouse or retail location.

5. Iterate and re-run after fixes

If you find errors during your 20-SKU audit or count reconciliation, update the source file and re-run the import until it passes every check.

For a final migration audit, check for the following conditions:

  • Product counts: Total products match the source.
  • Variant counts: All variant rows imported without collapsing.
  • Image rendering: Pictures appear on the live product pages.
  • Inventory logic: Stock levels are correct for every location.
  • URL handles: Product URLs match your migration plan.

Build a go-live plan

The moment customers can purchase from your new Shopify store is the moment you’ve been working toward.

A go-live plan is the final sequence of tasks required to move a store from staging to a live Shopify environment. It marks the transition from migration development to active commerce.

Start the go-live process by pausing all product, pricing, and inventory edits in Lightspeed. After freezing the catalog, perform a final delta import. This involves exporting only the records that changed since the initial migration.

Next, complete these steps:

  • Reconcile final counts: Verify products, variants, and active SKUs match.
  • Implement 301 redirects: Upload the redirect file for any changed handles.
  • Reconnect Google: Confirm the Google & YouTube channel is active and syncing.
  • Reconnect Meta: Ensure the Facebook and Instagram catalog sync is live.
  • Spot check product pages: Review live URLs, images, and variant behavior.
  • Place a test order: Run an end-to-end checkout via Bogus Gateway or Shopify Payments test mode.

Moving from Lightspeed to Shopify puts all your products, orders, and inventory into one system so you don't have to manage them in multiple places. For a successful migration, follow the steps above to clean your data, pick the right import tool, and QA your system before you go live.

Shopify POS offers 22% lower TCO

See how Shopify POS reduces retail operating costs and increases revenue better than the competition, based on real data and research conducted by an independent consulting firm.

Get the report

Migrate products from Lightspeed to Shopify FAQ

How do I import products from Lightspeed to Shopify?

Export the product list from Lightspeed, clean and map the fields to Shopify’s product CSV format, then import the file in Shopify admin under products. Shopify supports bulk product imports by CSV and using third-party apps like Matrixify.

Is Shopify better than Lightspeed?

Shopify is the stronger fit when a brand wants ecommerce and POS on one platform. Shopify says retailers using Shopify POS saw 22% lower total cost of ownership than competitors on average.

← All articles

What this article says

More in RetailTech & E-Commerce

All →
7 Influencer Database Options and How to Choose (2026)
Shopify

7 Influencer Database Options and How to Choose (2026)

10 Questions With August Tang on Interfaces and Internet Nostalgia
Squarespace Commerce

10 Questions With August Tang on Interfaces and Internet Nostalgia

Product catalog management with commercetools: A complete guide
Commercetools

Product catalog management with commercetools: A complete guide

Self-Service, Punchout and Hosted Catalog: The Three B2B Ecommerce Flows and How They Work
Vtex

Self-Service, Punchout and Hosted Catalog: The Three B2B Ecommerce Flows and How They Work

No internet connection, no problem: Building offline resilience into the unified POS system
Commercetools

No internet connection, no problem: Building offline resilience into the unified POS system

Markup vs Margin: Key Differences, Formula & Examples
Lightspeed

Markup vs Margin: Key Differences, Formula & Examples

More from Shopify

7 Influencer Database Options and How to Choose (2026)
Shopify

7 Influencer Database Options and How to Choose (2026)

Get Your Marketing Holiday Ready with Campaign Autopilot (2026)
Shopify

Get Your Marketing Holiday Ready with Campaign Autopilot (2026)

Business Capital Loans: 6 Types & How They Work (2026)
Shopify

Business Capital Loans: 6 Types & How They Work (2026)

Types of Natural Fabrics for Clothing (2026)
Shopify

Types of Natural Fabrics for Clothing (2026)

Generative AI for Business: Complete Guide (2026)
Shopify

Generative AI for Business: Complete Guide (2026)

The Entrepreneur Effect in the UK: When more people build, everyone benefits (2026)
Shopify

The Entrepreneur Effect in the UK: When more people build, everyone benefits (2026)