Platform planning

NCR Voyix Retail Migration Guide

NCR Voyix is a product family, not a single retail database format. Record the actual checkout application, release and back-office owner. Keep Counterpoint separate, and do not apply restaurant Data Sharing documentation to an unspecified retail installation.

Check my migration
Your next system

Moving into NCR Voyix Retail

Understand destination requirements before preparing your records.

Your current system

Moving from NCR Voyix Retail

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

Identify the NCR Voyix retail application before mapping data

NCR Voyix is a product family, not a single retail database format. Record the actual checkout application, release and back-office owner. Keep Counterpoint separate, and do not apply restaurant Data Sharing documentation to an unspecified retail installation.

The vendor documentation directory helps locate the relevant application documentation. A product overview identifies a family; the project lead still selects the edition’s supported access and receiving interfaces after the retailer identifies the installation.

Keep the retail relationships explicit

  • Merchandise: POS cache versus authoritative item/pricing owner
  • Customers: Local profiles versus centrally owned customer records
  • Stock: Store availability versus physical/on-hand quantity
  • Transactions: Retail receipts versus central reporting or audit feeds

A useful acceptance case

Trace one sale from its POS item identifier back to the authoritative merchandise record, store and customer owner. Use that trace to decide which system supplies each migration dataset and which records remain an archive.

This is an illustrative planning case, not a claimed customer result. Sqquid’s project lead selects the retailer’s actual records and compares expected identities, dependencies and quantities with the receiving result.

What belongs to your engagement

We offer this assessment subject to retailer-specific feasibility. Confirm the deployed product, authorized access, required fields, existing data and supported receiving operation before booking. Decide separately how history, cards, credit, loyalty and open orders are imported, archived or excluded.

The project lead documents the cutoff, rejected records, acceptance and any required reversal plan. A platform guide does not certify every edition or establish native support for all data.

Migration scope and responsibilities

The standard migration fee is $2,999 USD for the confirmed scope.

Tailored to your retailer data

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.

Routes offered subject to feasibility

We offer the currently listed migration routes subject to retailer-specific feasibility and an agreed scope. This includes POS migrations into Runit.

A project lead for your migration

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.

Retailer-provided ERP and finance approvers

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.

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.

Corrections before launch

We correct errors in our own migration work at no additional charge before launch.

Refunds for errors caused by Sqquid

If a migration error occurs and Sqquid is at fault, we will refund the fees the retailer paid us.

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.