POS Migration Timeline and Readiness

Schedule dependencies first

List source access, destination setup, extraction, mapping decisions and retailer approval before assigning the final transfer date. Name an owner and prerequisite for each. Waiting for a store to be configured is a readiness issue, not file-upload time.

Reserve time for exceptions

A rehearsal can uncover duplicate identifiers, unsupported fields or missing customer balances. Give the retailer a decision deadline and a retest slot. Do not compress review out of the schedule because an importer finished quickly.

Define the final trading window

Choose a snapshot time and timezone, restrict edits where agreed and capture changes made while stores trade. Multiple locations need explicit opening positions and a shared decision about transfers between old and new systems.

Confirm the launch milestone

An illustrative plan postpones final stock loading until the receiving warehouse exists and customer matches are approved. Record the date that ends Sqquid’s migration guarantee. For phased launches, agree whether a single project date or documented store milestones apply before work starts.

Official references

• Shopify migration methods

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.