Understand POS and ERP Migration Scope

Define the two deliverables

A POS migration moves agreed records into a receiving retail system. An ERP implementation also establishes companies, item behavior, purchasing, accounting and wider operations. An accepted item file is not acceptance of all those workflows.

Name the receiving decisions

For each dataset record the destination object, identifiers, required related records and create/update behavior. Companies, subsidiaries, warehouses and dimensions need named owners. Keep ordinary products distinct from serial/lot tracking and financial opening entries.

Assign approval before data loading

The retailer’s ERP implementation lead approves the retail subset and method; finance approves balances, posting treatment and reconciliation. For example, Business Central documents first-time configuration packages, while other systems have their own import mechanisms. Do not assume a method for an empty company is safe in a trading tenant.

Use a scoped illustrative test

A source shirt style may become ERP items/variants while posting configuration, purchasing units and company assignment still need review. Test a complete style, an existing customer and stock in two locations. Compare identity and quantities, and obtain separate approval of any values or obligations.

Keep the commercial boundary explicit

The standard fee applies only to the confirmed data scope. ERP setup, finance policies, vendor fees and ongoing integrations need explicit owners and separate decisions. Request an assessment with the target edition and implementation lead; no full ERP conversion or unlimited data support is implied.

Official references

• Business Central company configuration packages
• NetSuite inventory worksheet import method
• SAP Business One 10.0 DTW and opening-balance distinctions

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.