A retail data migration
Square for Retail→Shopify POS
A move from Square for Retail to Shopify POS needs an explicit map from a variation with a leading-zero SKU, a location-specific price and an existing customer to the receiving records.
Plan this migration Data migration: $2,999. Scope confirmed before booking.The records we review.
- Products & variants
- Style, size, and color relationships
- SKUs & barcodes
- Identifiers used across your stores
- Customers
- Supported fields and matching decisions
- Opening inventory
- Quantities mapped to each location
- Existing destination records
- Products and customers already in your next system
The decisions
we make first.
Source access
Review representative exports and the available extraction method.
History & balances
Assess sales history, gift cards, loyalty, and credits separately.
Test & acceptance
Agree the records and checks before the final transfer.
Choose the Square-to-Shopify workflow
Shopify documents a Store Migration app and a mapped CSV route for Square products and customers. Use the method that fits the actual account and catalog. With the app, keep the source CSV unchanged as instructed; with the manual CSV route, work from a copy mapped to Shopify’s receiving headers. Do not mix the two file-preparation procedures.
The documented app treatment needs review: imported selling status, a single price selected from differing location prices, unit-priced items and variants beyond the importer’s supported limits can require corrections. These are importer-specific constraints, not a claim about every Shopify import method.
Build the directional field map
| Square source | Shopify receiving decision | Acceptance evidence |
|---|---|---|
| Item and variation identity | Product grouping, variant SKU and barcode; retain a separate source-ID crosswalk | Find and scan two similar variations without duplication |
| Location prices and selling status | Review the selected price and draft/active status after import | Compare expected price and publication state before selling |
| Customer directory fields | Customer CSV or eligible app method, with explicit duplicate/overwrite rules | Reconcile created, matched, skipped and unresolved customers |
| Quantity at each Square location | For the documented app, review name-based location matching; for manual work use the approved location inventory workflow | Compare each variant/location pair and new location details |
| Orders, gift cards and customer value | Separate method, archive or exclusion | Approve the exact outcome rather than inferring it from contacts |
Test the exception-prone records
Choose a unit-priced item, a variation with different prices at two stores and a duplicate customer candidate. Check expected variant structure and active status before comparing totals. For locations, verify names, addresses and stock instead of accepting an automatically created location without review.
Confirm scope and approve the result
Sqquid offers managed preparation, mapping, a representative test, the agreed transfer and reconciliation for the confirmed scope. We confirm the selected method against your actual records before booking. The project includes a representative test and retailer acceptance before production.
Before booking, provide full authorized access to both systems and demonstrate access to your own data. Agree the included core fields and separately assess history and liabilities. Retain existing destination IDs, keep source data issues visible and complete acceptance checks before launch. Check my migration with the editions, locations and required records; do not send credentials or exports in the general enquiry.
Official references
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.
From the first export to the final review.
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.