POS to Acumatica

Shopify POS to Acumatica Data Migration

Define the retail records your Acumatica environment needs before planning the transfer.

Review my ERP migration

Shopify POSMapping reviewAcumatica

Records to assess

ItemsCustomersOpening inventory

Conceptual migration planning. Record support is confirmed before booking.

Before loading retail records

Destination requirements

Review required fields, identifiers, and relationships.

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 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 Shopify POS identity and coverage

Separate product/variant, customer and location-stock exports, preserving Shopify identities and existing online product links.

If ecommerce stays on Shopify, preserve its existing product/variant identities and assign the ongoing stock owner.

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

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 an existing online product, two variants and stock at two Shopify locations. 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 product/customer matching, receiving IDs and the exact location-stock operation; contacts do not carry history or liabilities.
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

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