Skip to content
Kuberan AI Help

Import

Open Import Client Data

Overview

Kuberan AI Books has two distinct import paths, used for very different jobs:

  1. 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.
  2. 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.
Screenshot coming soon
Import Client Data: upload a ZIP, name the new client, and pick the modules to bring across.

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

The importable modules are whatever the ZIP’s manifest contains, drawn from the full set of Books modules: Chart of Accounts, Bank Accounts, Customers, Vendors, Products & Services, Tax Rates & Settings, Invoices, Bills, Payments, Bank Transactions, Journal Entries, Documents, Reconciliations, Transfers, Deposits, Credits & Memos, Estimates, Purchase Orders, Sales & POS, Fixed Assets, Bank Rules, Recurring Templates, Fiscal Periods, and Client Settings.

Steps

  1. Upload — drag the .zip file in, or click to browse. The file must be a Kuberan client-data export (.zip only, up to 500 MB). Non-ZIP files are rejected.
  2. Preview & configure — the page reads the ZIP and shows the export’s source client, export date, total record count, and whether document files are included. Enter a New Client Name (it is pre-filled as “[source name] (Import)”).
  3. Select modules — tick the modules to import (each shows its record count). Use Select All / Select None to toggle quickly.
  4. Click the import button (it stays disabled until you have entered a name and selected at least one module). A progress bar tracks each step.
  5. Complete — when finished, click Open Client to jump into the new client, or Import Another.
New Client Name

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

Open the Import Data action from the Bank Accounts page’s row menu, then:

  1. Choose whether to import Bank Accounts or Transactions, then upload a .csv, .xlsx, .xls, or .json file.
  2. For transactions, pick the Target Account — an existing account, “Use account ID from file”, or + Create New Account to add one inline.
  3. Map columns (CSV/Excel only; JSON skips this) — the importer auto-matches columns to fields; confirm or adjust the mapping. Date, Description, and an Amount (or separate Debit + Credit) are required.
  4. Preview — see how many rows are new versus already present. Duplicates (matched by record ID) are highlighted and skipped.
  5. Import — transactions import in batches of 500 with a progress bar; a summary reports imported, skipped, and any per-row errors. A JSON file that also carries linked payments and journal entries can bring those across with an Include payments & journal entries option.

A separate, simpler Import CSV button on the Bank Accounts toolbar handles CSV-only statement uploads (up to 10 MB) and auto-detects the common Canadian bank formats (RBC, TD/EasyWeb, BMO, Scotia, CIBC) — see Bank Transactions for the full walkthrough.