FEWVIEW POS

MOVE YOUR RECORDS WITH CONFIDENCE

Bring your shop history.

Use an export from your current system. FEWVIEW maps columns and validates the data before saving.

Supported open files

CSV, TSV, TXT, XLSX, XLS, ODS, JSON, JSONL, NDJSON, XML and ZIP containing these files. Use UTF-8 text, the first worksheet, values instead of formulas, one record per row and clear column names. Limits: 8 MB per input, 10,000 records and 100 columns. Split larger exports into files.

JSON accepts an array of flat records or records inside a named collection. XML accepts named fields in record, row or item elements. A ZIP can hold one supported file, or a file named after the selected import type.

A safe order for migration

  1. Make a backup of both systems and retain the original export files.
  2. Choose the correct country and currency before importing.
  3. Import products and the current physical stock. Import customer and supplier contacts.
  4. Import sale and purchase invoice lines, then their payments. Import expenses, returns and refunds in their matching sections.
  5. Use opening balances only for debts that do not already appear in the imported invoice history.
  6. Import old stock movements as an archive. They do not change current stock again.
  7. Supply the original buying costs for historical profit. A saved profit-summary report is kept separately for comparison.
  8. Compare stock quantities, sales, tax, customer debts, supplier balances and profit with the old system before live trading.

Export from your old app

Vyapar → Tally master export ↗

Export Master.xml for stock and party masters. Export detailed transaction tables for history; voucher accounting needs separate reconciliation.

Tally export ↗

Use XML masters or flat Excel/CSV tables. Standard Sundry Debtors and Sundry Creditors ledgers are recognised.

Zoho Books export ↗

Export each relevant module as CSV or Excel, including item-level invoice data and payment references.

QuickBooks Online export ↗

Export lists and detailed reports to Excel. A summary report alone cannot reconstruct invoice lines or their original costs.

Odoo export ↗

Export the required fields as CSV or Excel, keeping document references and line identifiers.

Other shop portals

Download their item, customer, supplier and detailed transaction exports, then map the columns in FEWVIEW. The exact export must be checked; matching a file extension alone does not guarantee complete recovery.

PDFs and pictures can be kept as source documents, but are not automatically posted into the accounts. Encrypted or proprietary app backups, including unknown portal backups, need an open export from that system. FEWVIEW never guesses missing costs or silently executes an imported file.

Check the preview

Confirm the source-system name, original reference, dates, item lines, currency, tax and original costs. Use the supplied templates where an export needs rearranging. Repeated identical imports are skipped; changed records with the same reference stop for review. Keep one small reconciled trial before bringing a large history.

Installation and updates →