Platform planning

Oracle Retail Xstore Migration Guide

Identify the Xstore/Xstore Office version and the system that owns merchandise before selecting a loading interface.

Check my migration
Your next system

Moving into Oracle Retail Xstore

Understand destination requirements before preparing your records.

Your current system

Moving from Oracle Retail Xstore

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

Inventory central and store-side ownership

List the authoritative merchandise, customer, price and inventory systems, plus the organization and store identifiers. The checkout application may consume centrally distributed data rather than own every required record.

Use the installed version’s deployment specification

Oracle’s Xstore Office Cloud administration guide documents data loading through administration tools, deployment files and integration interfaces. Treat these as version-specific mechanisms, not a promise that a retail CSV can be uploaded unchanged.

Map distribution as well as fields

A correctly formed item record can still reach the wrong stores. Agree organization/store mapping, deployment sequencing, receiving acknowledgments and rollback responsibility with the enterprise implementation team. Keep payment and fiscal configuration separate from merchandise loading.

Inspect central and receiving-store results

Use an existing item, a new variant group and store-specific prices. Compare the intended central state with actual store acceptance and rejected records. Confirm how further updates are owned after cutover; a one-time data load is not the entire enterprise rollout.

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.