Lightspeed X Series to NetSuite Data Migration

Define the retail subset for NetSuite

The proposed data work concerns item types, subsidiaries, locations, customers and any required inventory detail. The ERP implementation owner must approve the objects, dependencies and permitted method before a migration is accepted. This is a scoped retail data assessment within a wider implementation.

Oracle documents CSV and inventory worksheet import workflows with permission and mapping requirements. The implementation lead must select the operation for the actual item types and enabled features; a worksheet is not a universal opening-stock method.

Review Lightspeed Retail X Series identity and coverage

X Series product grouping, individual variant IDs and outlet stock; retain customers and balances as separate records.

Product identity rules and grouping differ from the source. Standard bulk historical-sales import is limited and cannot be inferred from a product load.

Keep source IDs, field definitions, unit/currency context and the chosen extraction time with the map. Review duplicates and missing source values with the retailer rather than silently inferring replacements.

Destination decisions that change the result

An existing item, subsidiary assignment and inventory detail can have dependencies that a flat catalog does not express. Keep quantity acceptance separate from inventory value and financial opening entries.

• Item type and internal/external ID crosswalk
• Subsidiary, location and currency ownership
• Any serial/lot/bin requirements and receiving operation
• Separate finance-approved valuation and opening balances

Proposed mapping and acceptance matrix

Proposed representative test

Start with a variant family, an existing product link and stock across two outlets. In NetSuite, verify one variant family, an item already in NetSuite, stock at two locations and any approved tracked inventory. These are illustrative test choices. Use an approved test environment and record the expected identities, quantities and exceptions before loading.

The ERP lead accepts master data and relationships. The retailer’s finance owner independently accepts any values or liabilities. Check the possible effects on posting, notifications, stock and connected systems before treating a test as safe to repeat.

Confirm before booking

• Confirm grouping and receiving-ID rules, the customer method, outlet quantities and individual history/balance outcomes.
• Approve NetSuite account/features, item types, subsidiaries/locations, receiving operation and required inventory detail; finance must approve any opening-value or liability treatment.
• Name the ERP implementation owner and obtain approval of the exact retail subset, receiving method, dependencies and acceptance criteria.
• Have finance approve any balance date, valuation/posting operation, company/currency treatment and reconciliation; no full ERP or ledger implementation is included.
• Confirm full authorized source/destination access, existing-record behavior, representative test environment and the launch milestone.

Share the editions, locations, implementation lead and required retail records through Check my migration. Hardware, training, full ERP configuration and ongoing integrations remain separate work. Scope eligibility is confirmed before accepting the standard migration fee; no complete ERP conversion is implied.

Official references

• Lightspeed X Series product importer
• Lightspeed X Series bulk historical-sales restriction
• NetSuite inventory worksheet import method
• NetSuite opening-balance responsibilities

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.

NetSuite inventory adjustment import: Inventory adjustments have required fields and inventory-detail dependencies; account item types/features and finance-approved operation remain implementation decisions.