Lightspeed R Series to Acumatica Data Migration

Define the retail subset for Acumatica

The proposed data work concerns stock/nonstock items, customers, warehouses, branches and enabled attributes/subitems. 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.

Use the exact tenant release’s implementation and data-integration documentation to select an approved import scenario or interface. The documentation portal is a starting point, not evidence that a generic scenario fits every configured tenant.

Review Lightspeed Retail R Series identity and coverage

R Series item/matrix identity and store quantities, with a separate customer extract and explicit liability requirements.

An item import can add quantities to existing stock. Confirm the specific operation before repeating a partial 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

Item class, unit, warehouse and organizational relationships must be configured by the ERP lead. Ongoing commerce synchronization is separate from an approved one-time retail opening position.

• Tenant release, features and permitted interface
• Item types/classes, units and attributes/subitems where used
• Branches, warehouses and existing customer identities
• Scenario mappings, error reports and finance-approved opening position

Proposed mapping and acceptance matrix

Proposed representative test

Start with a matrix with multiple sizes, an existing item and location-specific quantities. In Acumatica, verify one stock and one nonstock item, a warehouse-specific quantity and an existing customer in the approved branch. 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 matrix reconstruction, customer receiving rules and whether the chosen inventory operation adds or sets quantities.
• Obtain tenant-version import/interface specification, enabled features and the implementation lead’s item/customer/warehouse map. Approve any opening stock/value operation and finance responsibilities.
• 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 R Series item import and stock behavior
• Acumatica 2025 R2 documentation portal; select the tenant version

What the vendor documentation establishes

R Series item import/export: New records leave System ID blank; existing records retain it. Store Quantity on Hand adds inventory rather than replacing it. Matrices and serials have separate rules.

R Series customer import: Customer templates go through Retail Imports. Custom fields are excluded; confirm actual supported characters and columns before preparing data.

R Series customer data: Customer exports and identity management are distinct from item exports.

Acumatica 2025 R2 import scenarios: Import scenarios specify target form, provider, object and mapping. Portal existence is no longer the only evidence, but the tenant scenario and owner approval are still missing.