Retail data, considered

POS Store Credit Migration

Distinguish positive store credit from customer debt, deposits, gift cards and loyalty rewards.

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.

Define the liability and identity

Distinguish positive store credit from customer debt, deposits, gift cards and loyalty rewards. Record the customer source ID, currency, balance date and owning account. Decide whether credit is shared across stores or restricted.

Match people before moving value

Two household members may share an email but have separate credit balances. Use a reviewed customer crosswalk, and hold uncertain identities for a retailer decision. A contact import should not be assumed to carry credit.

Account for changes during the move

An illustrative customer has $80 in the rehearsal export and spends $25 before cutover. The opening liability is $55 if no other movements occur. Retain the movement evidence instead of reloading the earlier balance.

Validate the receiving credit operation

Identify the supported balance-creation and redemption method for the exact edition; R Series documents a manual process separate from customer import. Compare expected and actual balances by customer and currency and resolve exceptions before launch. No native compatibility is assumed.

Migration scope and responsibilities

The standard migration fee is $2,999 USD for the confirmed scope.

Tailored to your retailer data

Every migration is unique. Your catalog, barcodes, orders and customer information are unique and proprietary to your business. We work closely with you to tailor the migration for the best possible outcome, agree the included records and define acceptance checks for your stores.

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.