Retail data, considered

POS Gift Card Migration

List the complete redeemable identifier, currency, remaining balance, issue/expiry context and any customer link.

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 card identity from its liability

List the complete redeemable identifier, currency, remaining balance, issue/expiry context and any customer link. A report ID or code ending is not necessarily enough to redeem a card in another system. Keep card data out of the general enquiry form.

Check the actual source and destination rules

Shopify’s standard gift-card CSV masks the full code and cannot recreate the original cards on its own. Lightspeed X Series documents a gift-card import, while R Series describes a separate manual workflow. These are not evidence that any source code is accepted unchanged.

Agree the customer-facing treatment

Choose an approved transfer, reissue, retained redemption system or exclusion before final cutover. Track the mapping from old card to replacement without leaving two independent spendable balances. Explain any changed redemption process to the retailer for approval.

Reconcile at the final cutoff

Compare card counts and balances by currency, include redemption after the rehearsal export and test an agreed card in the intended workflow. Record rejected identifiers and duplicates. A successful catalog import says nothing about gift card liabilities.

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.