FinAccounting Get started

Import / Export Module

Importing & Exporting Data

Bring historical records in from a spreadsheet or another system via CSV or Excel, or pull what’s already here back out — a guided, four-step wizard for imports, a one-click download for exports.

Format CSV or Excel (.xlsx / .xls) Import creates new records — it doesn’t update existing ones Access requires the Import / Export module on your role

Start here

1Before you start

Thirteen kinds of record can be imported, and most of them reference another one by name — a Sales Invoice references a Customer, a Stock Level references a Product and a Warehouse. Anything a file references has to already exist before you import that file; a referenced record can’t appear later in the same import (the one exception is Accounts’ own Parent Account Code, which can point at an earlier row in the same file).

The recommended order:

Accounts → Contacts → Products → Warehouses → Employees → then Income / Expenses / Bank Transactions / Sales Invoices / Purchase Bills / Salaries / Stock Levels / Transfers, in any order relative to each other.

Bank accounts have no CSV entity

Create your bank accounts directly in Banking first — nothing here can create one.

Import a file

2Choose what to import

Pick the record type from Import Into. The required and optional columns for that type appear immediately below it — click Download CSV Template for a blank file with exactly those headers already in place. Then upload your CSV or Excel file (.xlsx, .xls, .xlsm, .ods) — if it’s a workbook with more than one sheet, you’ll be asked which sheet to use.

Column headers don’t need to match exactly — auto-detect handles close matches in the next step, and anything else can be mapped by hand.

3Match your columns

Line each column in your file up against the field it corresponds to. For a grouped entity (Sales Invoices, Purchase Bills — see below) you’ll map header fields and line-item fields separately; header values are expected to repeat identically on every row belonging to the same invoice or bill.

4Preview & validate

A dry run — nothing is created yet. Every row is checked against the same rules the real import will use: required fields, valid numbers, and every cross-reference (a bank account name, a customer, a SKU) actually resolving to a real record.

Rows with errors are listed with the specific reason. Fix your file and re-upload, or move on and import only the rows that are already valid — invalid rows are simply skipped, not blocking.

5Import the valid rows

Click Import N Rows. Each row is created through the exact same real save logic its target module’s own form uses — so every default, validation rule, and side effect that would apply to typing it in by hand still applies here.

This runs row by row, not as one transaction — a row that fails at this stage (for a reason validation couldn’t predict, like a duplicate account code) doesn’t block any of the others. You get a final count of records created and records skipped, with the reason for each skip.

Export data

6Download existing data as CSV

The separate Export existing data panel is always visible alongside the import wizard. Pick what you want and click Export CSV — it downloads immediately, built directly from what’s already stored for the active company.

Most import entities can be exported the same way, with one difference worth knowing: an exported Employees file leaves the four compensation columns blank, since pay history lives in a separate record, not as flat fields on the employee.

Import from Akaunting

Guided Akaunting migration

Moving your whole company’s history over from Akaunting is common enough to get its own guided flow. Switch to Import from Akaunting at the top of this page instead of the standard wizard above.

From Akaunting, export your Chart of Accounts, Customers, Vendors, Items, Transactions (or Payments and Revenues), Transfers, Manual Journals, and Invoices/Bills if you use them — CSV or Excel both work. Akaunting exports long lists page by page, so you may have many files of each kind: upload them all. The wizard works out what each file is by name and tells you plainly what it skipped and why. Files that aren’t Akaunting exports at all (spreadsheets saved in other apps, or a Dolibarr file dropped into the same folder) are flagged and left out.

Tell it how your organisation works

Before importing, a short setup step asks three questions. The usual answers:

  • A non-profit, church or ministry: Items → What I earn from and spend on (no stock); money received → Record as Income; money paid out → Record as Expenses. Offerings, tithes and donations come in as income, and nothing is created in Sales, Products or stock.
  • A service business (e.g. web design, hosting, consulting): Items → Services I sell (no stock), with Income and Expenses as above. Only choose the Sales/Purchases option if your Akaunting export really contains your invoices and bills with their line items.
  • A shop that sells and stocks goods: Items → Products.

What it sorts out for you

  • Overlapping exports — pages exported twice, and Transactions vs Payments/Revenues describing the same money, are counted once.
  • Genuinely repeated payments — two identical payments on the same day (two salary payments, two fuel purchases) are both kept; only true duplicates from re-uploading a file are dropped.
  • Manual journals — their real debit and credit lines go to the right accounts (even when an income and an expense account share a name). Where a journal also appears as a payment, the two meet in a “Journal Clearing (Akaunting import)” account that nets to zero, so nothing is counted twice.
  • Categories post to the matching account in your Chart of Accounts, and each bank or cash account gets its own ledger account.
  • Contacts who both pay you and are paid by you become one contact marked as both customer and supplier.

Each section gets its own preview and an explicit Import N button; nothing commits until you approve it, and large sections import in small batches with a progress count. Re-running a section after a partial failure is safe — rows already created are skipped rather than duplicated.

What Akaunting’s export can’t give us

Akaunting doesn’t export opening balances, so accounts start at zero and are built up from your full history. Its export also leaves out the line details of some later manual journals — the wizard lists those so you can add them by hand if needed.

Danger Zone — undo a duplicated import

A collapsible Danger Zone panel sits below the wizard on every screen. Pick which record types to check, optionally set a cutoff date/time, preview exactly what would be deleted, then type DELETE to confirm. It’s a real delete (it also unwinds the ledger and account balance effect), not the reversible Delete button elsewhere — use it to clean up after committing the same import twice, not as an everyday undo.

Import from Dolibarr

Guided Dolibarr migration

Dolibarr’s own export shape is different enough from Akaunting’s to get its own guided flow. Switch to Import from Dolibarr at the top of this page instead of the standard wizard above.

From Dolibarr, export your Third Parties, Products and Services, Bank/Cash Ledger, Customer Invoices and Vendor Invoices (each with their line items and payments), Salaries, Users, and — if you keep stock — Warehouses, Stock per Warehouse, Stock Movements and your product Categories. Upload everything; the wizard recognises each file by name and tells you what it skipped and why (the activity log, for example).

Tell it how your business works

  • A shop or trading business: Products & Services → Things I sell or keep in stock; customer invoices → Money received from customers; vendor invoices → Money paid to suppliers. You get Products (with variants, cost prices, stock and categories), Sales and Purchases with their payments.
  • A ministry, NGO or simple service business: Products & Services → What I earn from and spend on (no stock); customer invoices → Record as Income; vendor invoices → Record as Expenses. Each payment becomes an Income or Expense entry on the day and account the money moved, and Dolibarr’s products become Income and Expense items — nothing goes into Products, Sales or Purchases.

What it sorts out for you

  • Variants — Dolibarr stores each colour or size as its own product (ref PARENT_RED); these come in as real variants of one product, with their own SKU, cost and stock, and invoice/bill lines point at the right variant.
  • Cost prices come from Dolibarr’s weighted average price, and stay a weighted average as you receive new stock.
  • Categories — a product can have several, and parent categories are added too (a product in “Men’s Watches” also appears under “Watches”).
  • Stock — current stock per warehouse is set from Dolibarr’s stock file; past stock movements come in as history without changing your counts.
  • Customers and vendors — a third party used both ways becomes one contact with both types.
  • Internal transfers are detected by matching a debit on one of your accounts to the same credit on another, same day.
  • Salaries import as Payroll expense entries linked to each employee’s contact, so you can see what each person was paid.
  • Genuinely repeated payments are all kept; only true duplicates are dropped.
  • Website links — a product’s “Public URL” is kept, so Products → Get photos from your website can bring in its picture.

Each section gets its own preview and an explicit Import N button; nothing commits until you approve it. Re-running a section after a partial failure is safe — rows already created are skipped rather than duplicated.

Danger Zone covers Invoices and Bills too

The same collapsible Danger Zone panel sits below this wizard — with Sales Invoices and Purchase Bills (and their recorded payments) included in what it can undo, in addition to Transactions, Transfers, Bank/Cash Accounts, Chart of Accounts, Contacts, and Items. Its own duplicate-detection memory is kept entirely separate from the Akaunting wizard’s.

Common tasks

Migrating a whole company’s history

Bringing over years of records from another system.

  1. Import your foundation records first

    Accounts, Contacts, Products, Warehouses, Employees — in that order, since almost everything after references one of these.

  2. Import your transactional history

    Income, Expenses (or the unified Bank Transactions if your old system exports both together), Sales Invoices, Purchase Bills, Salaries, Stock Levels, and Transfers — these can go in any order relative to each other.

  3. Choose safe statuses for historical rows

    For Purchase Bills, “billed” is usually the right default for old records rather than “received” — “received” can trigger a real Inventory stock movement if a line resolves to a Product with a Warehouse mapped, which you may not want for history that’s already accounted for elsewhere.

  4. Reconcile stock last

    Import Stock Levels after Products and Warehouses exist — it sets each product’s on-hand quantity per warehouse as an absolute count, not an addition, so it’s safe to re-run if a number needs correcting.

Importing invoices or bills with line items

Sales Invoices and Purchase Bills are grouped entities — one CSV row per line item, not per invoice. Every row belonging to the same invoice repeats the same Invoice Number (or PO / Bill Number) and the same header fields (customer/vendor, dates, status); only the line-specific columns (description, quantity, unit price) differ row to row. This is the same shape most accounting systems’ own invoice-and-line exports already use, so a direct export from your old system often maps in with little rework.

Avoiding double-counted transfers

If you’re importing both a Transfers file and a Bank Transactions / Income / Expenses file from the same source, the same real-world transfer can appear in both — once as a transfer, once as a bank movement on each side. Check for matching reference numbers between the two files first and import only one side of each; this isn’t detected automatically, and importing both double-counts the movement.

Reference

What can be imported

EntityShapeNotes
ContactsFlatCustomers, vendors, leads, employees, or other.
ProductsFlatProduct, service, or bundle. An optional Stock on Hand column turns on stock tracking and puts that stock into Inventory as opening stock (first warehouse, or a new “Main store”), like typing it on the Products form.
AccountsFlatChart of Accounts — Parent Account Code can reference an earlier row in the same file.
WarehousesFlat 
EmployeesFlatLeaving Employee Code blank creates a new employee; a code matching an existing employee overwrites that record instead.
Income / ExpensesFlatReal Banking transactions — separate files, mirroring most exports.
Bank TransactionsFlatA unified Income + Expense file with a Type column, for systems that export both together.
Sales Invoices / Purchase BillsGroupedOne row per line item — see above.
SalariesFlatPayslip history only — creates no GL journal or cash movement (see below).
Stock LevelsFlatSets an absolute on-hand quantity per product/warehouse, not an addition. If the product’s import (or form) already put its opening stock in another warehouse and it hasn’t moved since, that line is replaced, not added to, so stock isn’t doubled.
TransfersFlatMoves both account balances immediately, even at “pending” status.

What this module doesn’t do

Create-only — never updates existing records

Every import creates new rows. The only exceptions: an Employee Code matching an existing employee overwrites that employee, and a Stock Level for a product/warehouse pair that already has one updates it in place. Everything else creates a duplicate if you import the same file twice.

No undo

There’s no bulk “undo this import” — a bad commit has to be cleaned up by deleting the created records individually in their own module.

Salaries import posts no GL entry

Importing payslip history is a plain record insert — it never posts to the ledger or moves cash, unlike a real Payroll run’s Approve & Post. Historical cash movement is expected to come from a separately-imported Bank Transactions/Transfers file, so this deliberately doesn’t double up on that.

Stock Levels, Salaries, and Bank Transactions can’t be exported

Their stored shape doesn’t map cleanly back to the flat CSV format (stock is keyed by warehouse ID, payroll rows have no single “amount” field, and Bank Transactions would just re-export the same rows Income/Expenses already cover).

FinAccounting — Import / Export Reference Guide Back to top ↑