Move your POS product catalog with CSV: a safer migration checklist
Move a product catalog to TinyPOS Cloud with a small CSV pilot. Map supported fields, preserve codes, review preview errors, and keep stock and history separate.
A CSV file is a useful bridge between systems, but it is not a complete POS migration. The source and destination may interpret columns differently, and a product catalog does not include every historical record. A controlled TinyPOS Cloud import starts with field mapping and a small, reversible test.
Keep the original export unchanged
Export the source catalog and retain a dated original. Work on a copy so you can trace any renamed columns, removed products, or price changes. Keep sales history and provider payment reports separately where needed.
Decide which products should move now. Importing every discontinued item can clutter a new setup. Do not reuse old product codes for unrelated items simply to shorten the file.
Map columns to the current template
Use the sample or required headers shown by the current Cloud CSV flow. The basic importer requires name, category, and price and supports fields such as SKU and barcode. A file exported by another POS may need preparation before those fields match.
Preserve identifiers as text, check decimal formatting, and use a consistent encoding for product names. Separate prices from currency symbols if the template requires numeric values. Follow preview errors rather than assuming a spreadsheet that opens successfully is ready to import.
| Source information | Check before importing |
|---|---|
| Product name and category | Use readable, consistent text and required headers. |
| Price | Confirm numeric formatting and the intended currency context. |
| SKU and barcode | Preserve leading zeros and check duplicate identities. |
| Stock or quantity | Handle through the appropriate stock workflow; do not assume catalog CSV initializes it. |
Preview a small pilot before the full file
Choose a few rows that include accents, long names, a code with leading zeros, and representative prices. Review the preview and fix every unexpected mapping. Check how the current importer handles existing products before repeating a file.
Inspect the resulting entries in the catalog and on the intended selling device where applicable. Do not assume a basic CSV import reconstructs complex variant relationships, bundles, or recipes from an unrelated system.
Plan the cutover and retain historical access
Schedule the larger import for a quiet period and avoid editing the same products in several places during the change. Keep a record of what was imported and compare a sample against the original export.
Opening stock, customer balances, old receipts, and payment history need their own migration decisions. A catalog import should not be presented as transferring all of them. Keep the old system or its exports available until the new operation has been checked.
- Retain an untouched source export.
- Follow the current template and preview rules.
- Test a representative sample before a larger batch.
- Separate catalog data from stock and historical records.
- Reconcile the result before using it for live sales.
Frequently asked questions
- Will a stock column set opening quantities in Cloud CSV import?
- Do not rely on it. The catalog importer treats stock separately and ignores stock-style columns; use the appropriate inventory workflow and verify the result.
- Can a CSV move my complete history from another POS?
- A product catalog CSV does not establish migration of receipts, customer credit, loyalty balances, or payment settlements. Preserve those records separately and plan each requirement.