Retail data, considered
Record the source product/variant ID, file or URL, intended destination product and display order.
Check my migrationReview the records, identifiers, relationships, and export options.
Map supported fields and decide how to handle existing data.
Review a sample, compare agreed counts, and record the exceptions.
Record the source product/variant ID, file or URL, intended destination product and display order. Verify that the retailer is authorized to reuse the images. Keep source originals and avoid recompressing repeatedly while preparing the transfer.
A URL can work for a logged-in user and fail for an importer. Test the selected receiving method with permitted sample images and keep the source available until copies are verified. An expiring or authenticated link is not proof of a persistent destination asset.
An illustrative style has one shared front image and a separate navy photograph. Match the navy image to the correct variation without replacing the parent image for every color. Decide how missing photographs and duplicate filenames are treated.
Open the receiving product and each color variation, check image order and resolution, and confirm copied assets remain available independently of the old account. Shopify’s QuickBooks connector documentation lists images separately from its core transfer; do not infer image coverage from imported products.
The standard migration fee is $2,999 USD for the confirmed scope.
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.
We offer the currently listed migration routes subject to retailer-specific feasibility and an agreed scope. This includes POS migrations into Runit.
Sqquid assigns a project lead to each migration. The lead is responsible for migration correctness and oversight of the entire migration dataset, including planning and managing data reversal when needed. The reversal method, dependencies and acceptance checks are agreed for your retailer’s systems and data.
For ERP-related work, the retailer must provide an ERP approver and a finance approver. They approve the receiving requirements, included retail data, financial treatment and acceptance results within their responsibilities. Sqquid’s project lead coordinates the migration with them; full ERP implementation remains separate work.
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.
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.
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 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.
We correct errors in our own migration work at no additional charge before launch.
If a migration error occurs and Sqquid is at fault, we will refund the fees the retailer paid us.
Your systems. Your next chapter.
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.