Retail data, considered

POS Custom Field Migration

For each field record its name, meaning, example value, type, allowed values and the screens or reports that use it.

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.

Build a field dictionary

For each field record its name, meaning, example value, type, allowed values and the screens or reports that use it. The label season could mean a campaign, a date or an internal purchasing code. Do not map it from the name alone.

Choose a destination by meaning

Use an equivalent native field where suitable, an approved custom field when supported, a reference archive or an explicit exclusion. A long note can preserve characters without preserving search, filtering or validation behavior.

Check field support for the exact import

Shopify documents particular customer metafield types for CSV import. That does not imply every customer custom field or a related object can be loaded through the same file. Confirm the receiving definition and method before including it.

Test difficult values and dependencies

Use blanks, long text, non-ASCII characters, dates and values referenced by another record. Confirm the data type, search behavior and exports after import. Keep transformations and excluded values in the mapping log for retailer approval.

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.