Integrations / CSV & QBO Import
Moving in is a file drop.
Bring customers, vendors, items, invoices, bills, and bank history from spreadsheets or QuickBooks. Map the columns once; Bokeping reports every row it touched.
CSV for anything tabular
Contacts, items, invoices, bills, bank lines — if it fits in a spreadsheet, it imports.
QBO for QuickBooks
Bring your QuickBooks history over without retyping a single transaction.
Nothing silently dropped
Every row and every column is accounted for in the import report — landed, skipped, or flagged, with the reason.
No lock-in, either direction
Nothing is written until you confirm the preview, your file stays your file, and everything you import can be exported back out. Moving in shouldn’t mean being kept in.
The mapping screen
Your columns, our fields, one honest preview
Every export names its columns differently — “Client,” “Customer Name,” “Bill To.” Drop the file in and Bokeping guesses which column is which, shows you the guesses, and lets you correct any of them from a dropdown. Then it previews real rows as they’ll actually land. A column with data that maps to nothing gets called out with a warning — not quietly discarded. Nothing is written until you say so.
- Column mapping guessed, then shown for approval
- A live preview of real rows before anything posts
- Unmapped columns with data are flagged, never dropped
- Cancel at any point — the books are untouched until you confirm
The import report
Every row gets a verdict, with a reason
When the import finishes, you don’t get a shrug and a spinner — you get a report. This many rows landed. These twelve were skipped as duplicates of rows you already have. These three were flagged, each with its row number and what was wrong: a date that isn’t a date, an amount with a stray character. Fix them in the file and re-run it, or enter them by hand — either way, you can verify instead of trust.
- Landed, skipped, flagged — every row in one of three lists
- Skips name the duplicate they matched
- Flags carry row numbers and plain-English reasons
- One bad row never blocks the other five thousand
How it works
Export from the old tool
A CSV from your spreadsheet, or a QBO file from QuickBooks. Ten minutes, tops.
Drop it in and map columns
Bokeping guesses the mapping and shows a preview. You confirm before anything is written.
Read the report
What landed, what was skipped as a duplicate, what needs a look — every row accounted for.
FAQs
Fair questions
Customers, vendors, items, invoices, bills, and bank transaction history — each from its own file, in any order. Most businesses start with contacts and items, then documents, then bank history.
Imports comfortably handle files with thousands of rows — years of history in one go. If an export is enormous, split it by year and run the batches separately; duplicate detection means an overlap between batches lands once, not twice.
Yes — that’s the intended workflow. Fix the flagged rows in your file and drop the whole thing back in. Rows that already landed are skipped as duplicates; only the corrected ones post. The report proves it either way.
No. The importer detects rows it has already seen and skips them, listing each skip in the report so you can verify rather than trust.
Yes. Customer and vendor balances, open invoices, and bank balances post to the right accounts, so day one in Bokeping agrees with the last day in the old system.
Bad rows are flagged with row numbers and reasons instead of silently vanishing — fix them in the file or in Bokeping afterward. One bad row never blocks the rest of the import.
Bring your books over
Import is free on every plan — most businesses are moved in by end of day.
Ready to know your money?
We’re ready when you are. Free to start, up and running in minutes.