A retail data migration
NCR Counterpoint→Runit
A move from NCR Counterpoint to Runit needs an explicit map from a customized item, an outstanding customer receivable and store stock with source IDs to the receiving records.
Plan this migration Data migration: $2,999. Scope confirmed before booking.The records we review.
- Products & variants
- Style, size, and color relationships
- SKUs & barcodes
- Identifiers used across your stores
- Customers
- Supported fields and matching decisions
- Opening inventory
- Quantities mapped to each location
- Existing destination records
- Products and customers already in your next system
The decisions
we make first.
Source access
Review representative exports and the available extraction method.
History & balances
Assess sales history, gift cards, loyalty, and credits separately.
Test & acceptance
Agree the records and checks before the final transfer.
Assess the NCR Counterpoint source
Counterpoint version-specific extraction specification and authorized account/database access are still required.
A generic NCR Voyix product page is not evidence for Counterpoint field access, import tooling or custom database relationships.
Keep an untouched original and a record of account, edition, location coverage and extraction time. The customer must provide full authorized access and be able to access their own data. Do not infer missing fields or access from a vendor family name.
Plan the Runit destination
Runit vendor-confirmed style/customer receiving fields and import process for the agreed implementation.
A style must remain linked to its size/color sellable records. Public read APIs or report exports do not establish a supported inbound style importer.
Inspect existing receiving records before choosing create, match or update behavior. An exported internal ID should remain in a reconciliation crosswalk unless the receiving specification explicitly accepts it.
Directional data decisions
| Dataset | NCR Counterpoint evidence to preserve | Runit decision to confirm |
|---|---|---|
| Products and variants | Complete grouping, source IDs, sellable combinations and item status | Equivalent parent/variant structure and supported receiving fields |
| Identifiers and prices | SKUs, full barcode text, unit and price context | Matching rule, permitted identifier representation and accepted price behavior |
| Customer contacts | Source identity and duplicate candidates, separately from liabilities | Receiving method, existing-profile rules and rejected-row report |
| Location stock | Store/warehouse map, quantity type, unit and snapshot time | Correct receiving location and set-versus-add operation |
| History and commitments | Required receipts, gift cards, credit, loyalty and open orders listed individually | Native receiving method, approved transformation, archive or exclusion for each |
A representative test for this direction
Use a customized item, an outstanding customer receivable and store stock with source IDs. In the receiving Runit setup, also inspect a full style with an intentionally absent size/color combination, supplier code and two store quantities. Use these illustrative examples to plan your project’s sample and agree expected results before a production import.
Write expected identities, grouping and quantities before the sample load. Compare returned records and rejected rows, approve exceptions and capture changes made after the stock snapshot. Test any proposed history or balance operations separately so an item import cannot silently create a second liability or stock movement.
Official references
- NCR Voyix current POS product information; not a Counterpoint import specification
- Runit implementation coordination
What the vendor documentation establishes
Counterpoint current help: Current help location found; public response exposed the help/search shell rather than an adequate installed-version migration specification. This is an access limitation, not proof no method exists.
Runit implementation coordination: Implementation coordination does not provide a public complete inbound field specification; request an approved receiving template for migrations into Runit.
Technical method still to establish
Obtain a Counterpoint-version item/customer/by-store-stock export specification with matrix/custom-field identifiers. Map those outputs to Runit; ticket DOC_ID/DOC_GUID troubleshooting notes do not establish the merchandise export schema.
Validate that an illustrative matrix item, customer and two-store quantity can be represented without mistaking ticket or balance records for master data.
Sqquid’s technical reviewer owns this follow-up with vendor support or implementation partners. Account credentials, an actual customer sample, named approvers and a previous completed project are engagement matters, not blanket publication requirements. The offer remains subject to feasibility while the technical planning content is completed.
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.
From the first export to the final review.
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.