Platform planning

KORONA POS Migration Guide

Choose KORONA’s data-exchange format and receiving object before mapping a source spreadsheet.

Check my migration
Your next system

Moving into KORONA POS

Understand destination requirements before preparing your records.

Your current system

Moving from KORONA POS

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

Confirm the Data Exchange configuration

KORONA documents Data Exchange for CSV/Excel files and a product CSV template. Select the intended object and format in the actual back office. Check header and encoding settings so the first data row is neither lost nor mistaken for a heading.

Keep mapping decisions visible

Map product identity, barcode, supplier reference, units and price separately. Retain source IDs in the reconciliation record. A saved mapping format can make repeated work consistent, but it does not prove that changed source columns still mean the same thing.

Separate stock from ticketing and customer obligations

Identify stores and warehouses before deciding which quantity is opening stock. If the tenant also uses admission or ticketing workflows, list those separately. Customer contacts, cards, credit and historical sales require explicit outcomes beyond product creation.

Check a representative sample and rejected rows

Use a supplier-coded product, a unit/pack example and stock in two locations. Locate returned records and compare expected fields and quantities. Keep errors and exclusions with the retailer’s acceptance rather than treating a completed file upload as proof of usable 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.

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.