Platform planning

Retail Pro Migration Guide

Retail Pro Prism, Retail Pro 9 and older deployments need edition-specific planning before a receiving method is selected.

Check my migration
Your next system

Moving into Retail Pro

Understand destination requirements before preparing your records.

Your current system

Moving from Retail Pro

Start with your edition, available exports, and the data you need.

Identify the actual deployment

Record the version, subsidiaries, stores, server owner and any custom modules. An internal Retail Pro upgrade, Prism replication and a move to another vendor are different projects. Ask the implementation partner which tools are supported for the installed version.

Do not treat a resource export as a universal importer

Retail Pro documents resource export/import tooling in its Prism feature history, including dependencies on other resources. Its purpose includes initialization and replication. This does not establish that an arbitrary third-party catalog can be loaded unchanged.

Preserve subsidiary and matrix relationships

Keep subsidiary, store, style/matrix and sellable-item identifiers distinct. Review serials, price levels and customers shared across locations. A duplicate SKU in different subsidiaries needs a deliberate match rule, not an automatic merge.

Choose the evidence for acceptance

A representative sample should show a complete matrix, a unique or serialized item, stock at two stores and a customer with a balance. Agree the receiving specification and an accessible history archive. A written field map must explain which relationships remain operational.

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.

Retail details, carefully reviewed.

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.