Destination requirements
Review required fields, identifiers, and relationships.
POS to Odoo ERP
Lightspeed R Series to Odoo ERP Data Migration
Define the retail records your Odoo ERP environment needs before planning the transfer.
Review my ERP migrationLightspeed Retail R SeriesMapping reviewOdoo ERP
Records to assess
ItemsCustomersOpening inventory
Conceptual migration planning. Record support is confirmed before booking.
Before loading retail records
Existing records
Agree how destination data will be matched and reviewed.
Acceptance checks
Define counts, quantities, and the treatment of exceptions.
Define the retail subset for Odoo ERP
The proposed data work concerns product templates/variants, contacts, companies, warehouses and installed custom models. 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.
Odoo documents import/export, stable external identifiers and related-record mapping. API entitlement and available models depend on the plan/version/database. Select the actual method with the implementation owner rather than assuming every installation exposes the same fields.
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
A product/contact load does not establish inventory locations, POS sessions, accounting configuration or valid opening values. Cross-company links and custom modules need explicit approval.
- Version, edition, hosting and installed modules
- Template/variant and related-record external IDs
- Company, warehouse/location and contact identity
- Approved stock operation and separately owned finance configuration
Proposed mapping and acceptance matrix
| Retail source evidence | ERP decision requiring approval | Acceptance evidence |
|---|---|---|
| Product/variant identities and units | Correct item type, related records, units and existing-record behavior | Trace each included source ID to its accepted receiving record |
| Customer identity and duplicate candidates | Correct customer/business-partner identity and company scope | Created, matched, rejected and unresolved records reconciled |
| Store quantities and movement cutoff | Company/location/warehouse map and approved stock operation | Each item-location quantity checked independently |
| Retail liabilities and opening values | Finance-selected treatment and date; separate from master data | Approved controls by identity, company and currency |
| History and unsupported relationships | Native method, transformed reference, readable archive or exclusion | Known historical lookup and an approved exception register |
Proposed representative test
Start with a matrix with multiple sizes, an existing item and location-specific quantities. In Odoo ERP, verify a product template with two variants, an existing contact and stock in two approved locations. 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.
- Approve Odoo version/modules, access entitlement, external-ID/related-object rules and company/warehouse mapping; confirm inventory and finance methods separately.
- 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
Migration scope and responsibilities
The standard migration fee is $2,999 USD for the confirmed scope.
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.
A defined
data project.
$2,999 for the confirmed data migration scope.
ERP configuration is a separate workstream.
Accounting history and balances need individual assessment.
Confirm my project scope