INTELLIVISIONMIGRATION Back to My Business

Connect your old POS

Move a complete business pack or use a guided vendor connection. IntelliVision previews and reconciles every supported class before writing, preserves every original source row, refuses credentials, and never invents meaning for fields it cannot map.

COMPLETE BUSINESS MIGRATION

Bring the business, not only the product list

Products and batches, detailed sales and returns, customers, suppliers, purchases and payments, accounting, staff, branches, VAT history, loyalty, gift cards, payroll, settings and vendor-specific source rows. Unknown source fields are retained in the migration archive instead of being silently discarded.

Mapped into IntelliVision records

These become structured records that can be reconciled before cutover.

BranchesStaff & rolesProducts & pricesStock & batches Customers & balancesSuppliers & balancesPurchases & GRV linesSupplier payments Sales & receiptsSale item linesTenders/paymentsReturns/credit notes Chart of accountsBalanced ledgerVAT-period historyLoyalty & gift cardsPayrollSettings

Preserved with the source evidence

Old-system records without a safe live destination are kept verbatim and labelled, never guessed into the books.

Open laybysQuotesSales ordersJob cardsBill of quantities Promotions & price rulesBank reconciliationsBudgets & assetsReport definitionsAudit historyOther vendor tables
A complete sales move is not one “Sales total” file. Bring receipt headers, every item line, tender/payment breakdown and returns or credit notes for the full date range. Missing components are shown during preflight; IntelliVision never manufactures them.
No pack selected

Preflight reconciliation — nothing written yet

Every source row is retained locally for audit. Historical sales, returns, purchases, payroll and VAT records are marked as imported history; they do not pretend IntelliVision processed, filed, approved or paid them.

1 · Where are you coming from?

Quick connections are not a full changeover. API routes bring only the classes that provider exposes. Guided exports can do a quick product/customer/sales import, but a complete cutover must use the Complete Business Migration above with every available export and the original source backup.

Export recipe

Follow these steps in your old system, then drop the file into the import portal — it maps this vendor's columns automatically.

    Full cutover checklist — collect every category your old system contains

    Products, prices, costs & stockSales/receiptsReceipt item linesTendersReturns Customers/debtorsSuppliers/creditorsPurchases/GRVsBranchesStaff Ledger & cash bookVAT historyLoyaltyOpen documentsSettings & audit trail

    If your vendor cannot export a class as CSV, include its supported database/SQLite export or have the vendor produce a complete data extract. Unmapped tables are retained in the migration archive and disclosed as “preserved only”; they are not silently discarded or pretended to be live.

    Use Complete Business Migration ↑ Quick products/customers/sales only →

    Paste straight from your spreadsheet

    In Excel or Google Sheets, select your data including the header row (e.g. Name, Phone, Balance — or Name, Price, Stock), press Ctrl+C, then click the box below and press Ctrl+V. You can fix any cell in the preview before importing. Everything stays on this device.
    rows 0 detecting…
    Click any cell to edit it — the grid is what gets imported, not the original paste. Use ✕ to drop a row.
    POPIA: you are importing customer records — by importing you confirm these are your own existing customers, moved for the same purpose you collected them. They stay on this device unless you later enable Connected Mode.
    Books: any Balance column posts a real opening-balances journal to your ledger (debit balances and credit balances each on their correct side) — check the balances in the grid before importing.

    Read your old system's files — right off this machine

    Pick the folder (or files) where your old POS keeps its exports or backups. Everything is read locally in this browser — nothing is uploaded anywhere. We recognize CSV exports, SQLite databases and IntelliVision archives; every file you pick appears below, supported or not.
    scanned 0 importable 0
    Import File Detected as Rows
    POPIA: at least one selected file contains customer records — by importing you confirm these are your own existing customers, moved for the same purpose you collected them. They stay on this device unless you later enable Connected Mode.
    Safe to run again: re-importing the same files writes nothing and re-posts nothing — every row is recognized as already present.

    2 · Connect your account

    not tested
    Your token stays in this page's memory only — it is never saved, never logged by our relay, and you should revoke it in your old system once the migration is done.

    3 · Preview what we found

    Nothing has been written yet. These are live counts from your old account.
    Honest limits: customer account balances don't come across from any of these APIs — customers arrive at R0.00, so NO opening journal is posted (bring balances with a CSV from your old back office). Stock-on-hand comes across from Shopify only; for the others do a stock capture after cutover or import a stock CSV.

    4 · Approve what to import

    Each class of data needs your explicit tick. Unticked data is never pulled into IntelliVision.

    5 · What happened — exactly

    Every row either imported, was rejected with a reason, or was recognized as already in your system. Nothing is ever silent.
    Safe to run again: a re-import of the same data writes nothing and re-posts nothing — every row is recognized as already present.