Skip to content

Integrations / CSV & QBO Import

Moving in is a file drop.

Import customers, vendors, items, invoices, and bills from separate CSV/XLSX files. Bring bank transactions in through CSV/XLSX or bank files such as .qbo. Review the preview and results for each import.

CSV/XLSX for supported records

Import customers, vendors, items, invoices, and bills separately, using the supported fields for each record type.

.qbo for bank transactions

Web Connect files contain bank or credit-card activity, not customer lists, vendor lists, invoices, or a complete QuickBooks company.

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

CSV and XLSX exports name their columns differently — “Client,” “Customer Name,” “Bill To.” Bokeping suggests column mappings for you to review and previews the rows before import. Check required fields and any unsupported data before confirming. Structured bank files such as .qbo have a fixed format: Bokeping reads their transaction fields automatically, without custom column mapping.

  • 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

1

Prepare separate files

Export the lists and documents you need from your old tool as CSV/XLSX. Download bank activity separately from your bank as .qbo or another supported bank format.

2

Choose the matching import

Select the record type and review the preview. Map CSV/XLSX columns to supported fields; .qbo files belong in bank transaction import.

3

Read the report

What landed, what was skipped as a duplicate, what needs a look — every row accounted for.

FAQs

Fair questions

Bring your books over

Import is free on every plan — most businesses are moved in by end of day.

Start for free
The full switching guide →

Ready to know your money?

Free plan, no card needed. Bring your QuickBooks or spreadsheet history, invite your accountant, and start reading your own books today.