Retail data, considered

POS Supplier Data Migration

A product’s vendor name may be a display value rather than a supplier account.

Check my migration
01

Understand the source.

Review the records, identifiers, relationships, and export options.

02

Prepare for the destination.

Map supported fields and decide how to handle existing data.

03

Check the result.

Review a sample, compare agreed counts, and record the exceptions.

Separate a vendor label from a supplier record

A product’s vendor name may be a display value rather than a supplier account. List supplier IDs, contact details, purchasing terms, currency and supplier-specific item codes separately. Determine which receiving records can represent each field.

Map many suppliers without losing the item link

An illustrative product is bought from two suppliers using different pack sizes and supplier codes. Keeping only its first vendor name would lose a purchasing relationship. Retain the product-to-supplier crosswalk and agree the primary supplier rather than discarding alternatives.

Keep purchasing and accounting decisions separate

Open purchase orders, supplier balances and payment terms need individual acceptance. A supplier contact import does not establish an accounts-payable migration. If the destination cannot retain a relationship, agree a reference archive or another purchasing system.

Validate the buying example

Look up a product from each supplier and verify the correct item code, unit/pack conversion and agreed terms. Match an open purchase-order line to its supplier. Reconcile included, duplicate and excluded supplier records in the handover.

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.

Your systems. Your next chapter.

Know what moved. Know what needs attention.

Tell us where your data is today, and where you’d like to go. We’ll help you understand the next step.

Check my migration Retail data migration for $2,999. Scope confirmed before booking.