Import
Overview
Kuberan AI Books has two distinct import paths, used for very different jobs:
- Import Client Data (whole-client ZIP) — recreate an entire client in a workspace from a Kuberan export ZIP. This is for backup restore and moving a client between workspaces or environments. It brings across every module you select — chart of accounts, customers, vendors, items, invoices, bills, transactions, journal entries, documents, and more.
- Bank import (CSV / Excel / JSON) — bring bank transactions (and optionally bank accounts) into an existing client. This is the day-to-day path for loading a bank’s transaction export. It is documented in detail under Bank Transactions; this page summarises it for orientation.
Import Client Data (ZIP)
This restores a complete client from a .zip file produced by Export Client Data. The ZIP holds a JSON file per module plus, optionally, the document files themselves.
What it imports
Every module the export contained, including: Chart of Accounts, Bank Accounts, Customers, Vendors, Items & Item Categories, Tax settings, Invoices, Bills, Payments, Bank Transactions, Journal Entries, Documents, Reconciliations, Transfers, Deposits & Customer Deposits, Credit Memos & Vendor Credits, Estimates, Purchase Orders, Sales Receipts & Daily Sales, Fixed Assets, Bank Rules, Recurring Templates, Fiscal Periods, and Settings.
Steps
- Upload — drag the
.zipfile in, or click to browse. The file must be a Kuberan client-data export. - Preview & configure — the page shows the export’s source client, export date, and total record count. Enter a New Client Name.
- Select modules — tick the modules to import (each shows its record count). Use Select All / Select None to toggle quickly.
- Click Import as “[name]”. A progress bar tracks each step.
- Complete — when finished, click Open Client to jump into the new client, or Import Another.
Required. The name the imported client is created under. The import creates a new client; it does not overwrite an existing one.
Bank Import (CSV / Excel / JSON)
To load transactions into an existing client, use the bank import on the Bank Accounts page rather than the client-data ZIP import.
What it imports
- Bank Accounts — from CSV, Excel, or JSON.
- Bank Transactions — from CSV, Excel, or JSON (JSON can also carry linked payments and journal entries).
How it works
- Choose whether to import Bank Accounts or Transactions, then upload a
.csv,.xlsx,.xls, or.jsonfile (max 10 MB for transactions). - For transactions, pick the Target Account (or create a new account inline).
- Map columns (CSV/Excel) — the importer auto-matches columns to fields; confirm or adjust the mapping. Date, Description, and an Amount (or separate Debit + Credit) are required.
- Preview — see how many rows are new versus already present. Duplicates (matched by ID) are highlighted and skipped.
- Import — large files are processed in batches with a progress bar; a summary reports imported, skipped, and any per-row errors.
A simpler Import from CSV flow auto-detects the common Canadian bank formats (RBC, TD/EasyWeb, BMO, Scotia, CIBC) and verifies column order against the running balance — see Bank Transactions for the full walkthrough.
Related
- Export — Produce the ZIP that Import Client Data restores
- Bank Transactions — Full bank CSV import walkthrough and duplicate handling
- Bank Accounts — Where the bank import modal is launched
- Chart of Accounts — Accounts created/matched on import