Wave to QuickBooks Converter: Convert Wave Accounting Exports to QBO

Export from Wave, then split the data by type. Transactions convert to a .qbo file and go in through Bank Feeds. Lists such as the chart of accounts, customers and vendors go in through QuickBooks' own Import Data screen. Nothing moves in one file, and the table above shows which route each piece takes.

The order matters more than most guides admit. Set up your QuickBooks chart of accounts first, because every transaction you import has to land somewhere. If you import a year of Wave activity into an empty account list, you get a year of Uncategorized Expense and a much longer cleanup than the migration itself. Bring in accounts, then customers and vendors, then transactions last.

Go to Settings, then Other, then Data Export, choose CSV or XLS, and Wave emails you a compressed zip. The accounting portion arrives as four separate files. For a narrower pull, run the Account Transactions report, filter it to the date range you want, and export that instead.

Two limits catch people. Viewer and Editor user roles cannot run a data export at all, so if you are the bookkeeper rather than the owner you may need the owner to run it or to raise your role first. And an export only covers the business profile you are currently inside. If the Wave account holds three businesses, that is three separate exports, one per profile, and mixing them into a single import is how two companies end up in one QuickBooks file.

Wave Connect, Wave's Google Sheets add-on, is the other way out. Extensions, Wave Connect, Download, then pick the data type, and the rows land in a sheet you can save as CSV. It is useful when you want to look at the data before it leaves, or when the emailed zip has not arrived.

Yes, but not as the raw Wave file. QuickBooks Online's bank upload accepts .csv, .txt, .qbo and .ofx, and a CSV has to be reduced to three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit), in English, under 350 KB and under 1,000 transactions. A Wave export meets none of those constraints out of the box.

Converting to .qbo removes the reshaping work and the row cap in one move. The path inside QuickBooks Online has shifted recently depending on the account: newer layouts route through All apps, then Accounting, then Bank transactions, then Link account and Upload from file, while older ones still show Transactions and then Bank transactions. Either way you pick the account, choose the .qbo, and QuickBooks reads the account and date range straight out of the file instead of asking you to map columns.

No. QuickBooks Desktop cannot import bank or credit card transactions from a CSV in any version, including Enterprise. Its only transaction import routes are a .qbo Web Connect file through Bank Feeds or an IIF file. This is the single hardest wall in a Wave to Desktop move, and converting to .qbo is the way through it.

The Import Excel and CSV Toolkit that ships with Desktop confuses this constantly. It handles exactly four list types: customers, vendors, items and the chart of accounts. It does not touch transactions. Bookkeepers lose whole afternoons discovering that, usually after they have already cleaned a Wave CSV into what they assumed was the right shape.

IIF is the other Desktop route, and it is worth knowing what you are choosing. A .qbo lands in the Bank Feeds review queue where you accept or reject each row and QuickBooks matches against what is already there. An IIF posts straight to the ledger with no undo. For a migration you are going to want the review queue. If you specifically need the list-and-journal side, the CSV to IIF converter covers that format.

A .qbo import is protected against re-importing itself. Every transaction in an OFX or .qbo file carries a FITID, unique within the account, and QuickBooks skips any FITID it has already seen, even after you delete the transaction. A plain CSV has no transaction identifier at all, so QuickBooks cannot tell a repeat upload from new activity.

The duplicate risk in a Wave migration comes from a different direction: connecting the live bank feed at the same time you import history. The bank feed pulls the last 90 days from the bank, your Wave export probably covers the same 90 days, and the two sets carry different identifiers because they came from different systems. Import your Wave history for the period that ends the day before the bank feed starts, and the overlap never happens.

As far back as Wave holds it, if you convert to .qbo. The 1,000 row and 350 KB caps that limit a QuickBooks Online CSV upload apply to CSV files, so several years of activity that would need to be sliced into a dozen CSV chunks converts and imports as .qbo files instead.

Whether you should is a separate question. Most US firms bring in one to two closed years plus the current year, because that covers the comparative period on the financial statements and the window a tax preparer is likely to ask about. Older than that, a summarized opening journal entry is usually cleaner than thousands of individual rows nobody will ever look at.

MM/DD/YYYY for a US QuickBooks company file. This trips people up because the Intuit help article Google surfaces most for CSV formatting is the global edition, which recommends DD/MM/YYYY. Follow it on a US file and every transaction dated the twelfth or lower silently lands in the wrong month.

Opening the Wave CSV in Excel before importing adds a second layer of risk. Excel reinterprets dates on the way in and out: a two-digit year from 00 to 29 becomes 2000 to 2029 while 30 to 99 becomes 1930 to 1999, and a workbook moved between Windows and Mac shifts every date by four years and a day because Windows defaults to the 1900 date system and Mac to 1904. The converter reads the file directly, so the safest move is not to open it in Excel at all.

Convert them separately and import them into the credit card account, not a bank account. The sign convention flips on cards. In a single amount column a bank row is positive for money in and negative for money out, but on a credit card a purchase is a positive charge. Import card rows into a bank account and every balance runs backwards.

Use a minus sign for negatives, never parentheses. Accounting exports and spreadsheet formatting both like to render a negative as (125.00), and QuickBooks reads that as text rather than a number. If you are moving several card accounts, the credit card CSV to QuickBooks converter walks through the account-type side in more detail.

Customers, vendors and the chart of accounts import cleanly through QuickBooks' own Import Data screen on Online, and through the Import Excel and CSV Toolkit on Desktop. Invoices import natively on QuickBooks Online but have no CSV path on Desktop, so those either go in through IIF or get entered by hand.

A practical shortcut most migrations miss: you usually only need the open invoices and unpaid bills, not the whole history. Closed, paid invoices are already reflected in the transactions you are importing and in the opening balances. Bringing in a paid invoice on top of the deposit that paid it creates work rather than saving it. Export the aging reports from Wave, bring in what is still outstanding, and let the rest sit in the archive.

Not for a typical single-entity small business. Conversion houses earn their fee on complex files: multi-currency, inventory, job costing, payroll history, several years of detail that has to tie out exactly. A Wave file with one or two bank accounts, a card, and a customer list is well inside what one person can move in an afternoon.

The honest dividing line is whether anyone will audit the result. If a lender, an acquirer or an IRS examination might look at the converted books, the reconciliation trail matters more than the money you save, and a specialist doing it with a signed scope is worth the cost. If it is your own books and you can reconcile the bank accounts yourself, the export, convert and import route gets you there for the price of the conversion.

Reconcile every account in Wave through your cutover date, then pick that date and stop entering transactions in both systems. Set up the QuickBooks chart of accounts before anything imports. Then export from Wave, convert the transaction files to .qbo, and import accounts and lists before transactions.

Choose a cutover that lands on a period end, ideally the start of a quarter or a fiscal year. Mid-month cutovers force you to explain to yourself, six months later, why March exists in two systems. And set up your QuickBooks bank rules before the first import rather than after: rules categorize rows on the way in, which is the difference between reviewing a few hundred pre-coded transactions and coding them one at a time.

Keep the original Wave export zip. Not on the desktop of the laptop you are working on, but somewhere it will still be in three years. It is the only copy of the source data once the Wave account closes, and it is what you will reach for the first time a converted balance looks wrong.

The conversion side is small. Three conversions run with no account and no card, and a free signup covers unlimited conversions capped at 100 transactions per file with a watermark on the output. Paid plans start at $49 a month, or $24 a month billed yearly, for 100 full conversions. Full-service migration firms charge in the hundreds to low thousands.

The cost that actually bites is the cleanup you create by importing into an unprepared file. Every uncategorized row is a decision someone has to make later, and at a bookkeeper's hourly rate a few thousand miscoded transactions cost more than any converter or migration service on the market. Time spent on the chart of accounts before the first import is the highest-return hour in the whole project.

Most of the traffic on this route is US small businesses that have grown past what Wave covers. The common triggers are hiring the first employees and needing real payroll, taking on inventory, needing class or location tracking, or a lender or accountant asking for QuickBooks specifically. Wave stays genuinely good at what it does; businesses leave it because their requirements changed, not because it broke.

The other half is bookkeepers and accounting firms standardizing a client base. A practice running eight clients across four systems spends more time remembering which is which than doing the work, and consolidating onto QuickBooks pays for itself in the first quarter. That group converts in volume, one client file after another, which is why the transaction step needs to be a two-minute job rather than an afternoon of column mapping.

Four failures account for most of the pain. The first is importing transactions before the chart of accounts exists, which turns a migration into a coding project. The second is running the bank feed and the history import over the same dates, which produces a duplicate for every transaction in the overlap.

The third is date drift, from the DD/MM/YYYY global help article or from opening the CSV in Excel. It is quiet, which is what makes it expensive: nothing errors, the rows just sit in the wrong months and the reconciliation refuses to clear. The fourth is discovering the QuickBooks Desktop CSV wall halfway through, after the files are already cleaned, and having to start the transaction step over as a conversion.

All four are avoidable in the planning, and none of them are avoidable once the data is in. Reconcile, prepare the file, convert, then import in the order accounts, lists, transactions.

Upload the Wave transaction CSV at the top of this page and the converter reads the columns, normalizes the dates and signs, and returns a balanced .qbo you can open in QuickBooks Online or QuickBooks Desktop. Balances are checked against the file before it downloads, so you know the totals tie before anything reaches your books.