QuickBooks to Wave is a data-model compression: inventory, classes, and POs are lost. API migration is viable but complex. Trial balance validation is non-negotiable.
There is no native one-click migration path from QuickBooks to Wave. The fundamental challenge is a structural compression of data models: QuickBooks supports deep inventory tracking, class/location dimensions, job costing, purchase orders, sub-customers, and multi-user access, while Wave is a streamlined freemium tool with flat product structures, no inventory valuation, no purchase orders, and no dimensional tracking. Custom work is required to export data via CSV, IIF, or the QuickBooks API, transform it to fit Wave's simplified schema, and reload it through Wave Connect CSV imports or Wave's GraphQL API—with vendors and bills requiring manual recreation since Wave's API lacks mutations for those entities.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
QuickBooks to Wave migration fails most often at two points
inventory and opening balances. Wave does not calculate or track unit inventory value, and once opening balances are wrong, every downstream report is wrong too. (support.waveapps.com)
As of May 2025, Wave requires an active Pro Plan or Wave Advisors package for third-party
As of May 2025, Wave requires an active Pro Plan or Wave Advisors package for third-party API connections. Full-access tokens still exist for development or personal use. Wave does not provide a separate sandbox — test migrations run inside extra businesses within the same account. (support.waveapps.com)
For a sole proprietor with one year of data, use the CSV import for opening balances
For a growing business with 5+ years of complex transaction history, use a managed service or build a custom API pipeline to preserve relational links.
Run parallel systems for at least one full accounting period after migration
Close the month in both QuickBooks and Wave before decommissioning QuickBooks.
Wave's moneyTransactionCreate mutation is marked BETA and requires isClassicAccounting to be false
Test thoroughly in an extra Wave business before running against production data — Wave does not provide a separate sandbox environment. (developer.waveapps.com)
Do not load payments before invoices
If a payment cannot find its parent invoice, it sits as unapplied income, breaking your accounts receivable reporting entirely.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Scope the ledger, the subledgers and the audit obligations.
Objective Agreed scope across master data, open transactions and historical balances, with finance and audit signed up.
Keep these open
-
Inventory master data and transaction volumes in QuickBooks
Count GL accounts, customers, vendors, items, fixed assets, open AR and AP, and transaction lines by year. Transaction line volume, not header count, is what determines your load time.
Data Profiler Get real record counts instead of estimating from memory -
Decide the history strategy with finance and audit
Choose between opening balances only, open items plus balances, or full transactional history. This is the single biggest scope decision in an ERP migration: full history multiplies effort many times over, and most organisations land on balances plus open items plus a read-only archive.
Full transactional history is rarely worth the cost. Confirm what your auditor actually requires before assuming you need it.
Vendor Evaluator Score Wave against alternatives on weighted criteria -
Consult the external auditor early
The auditor has views on cut-over timing, audit-trail retention and how you evidence that balances carried across correctly. Finding this out after go-live can mean a qualified opinion, so get it in writing now.
-
Review the chart of accounts and decide whether to redesign
A migration is the natural moment to restructure the COA, and also the riskiest one. If you redesign, you need a mapping from old to new for every historical balance, plus a plan to restate comparatives.
Redesigning the chart of accounts mid-migration doubles the reconciliation burden. Treat it as a separate, sequenced project if you can.
-
Catalogue integrations and statutory reporting
List banking feeds, payment gateways, tax filing, payroll, CRM, e-commerce, warehouse and BI. Then list every statutory and tax filing obligation with its deadline — those deadlines constrain your window absolutely.
-
Pick a period-aligned go-live date
ERP cutovers align to a period boundary — ideally the start of a fiscal year, otherwise the start of a clean month. Mid-period cutover means split-period reporting for the rest of the year.
QuickBooks → Wave specifics
- Cost elimination
- QuickBooks Plus costs ~$115/month ($1,380/year). Wave Starter is free; Pro is ~$16/month (~$192/year). For a freelancer or micro-business that only invoices clients and tracks expenses, the savings are real.
- Feature simplification
- Businesses that never used inventory, classes, or purchase orders are paying for unused complexity.
- Desktop sunset pressure
- Intuit ended support for QuickBooks Desktop 2023 in May 2026. Some Desktop users prefer Wave's simplicity over migrating to QuickBooks Online.
- Tax report comparison
- Run a sales tax summary for the same period in both systems.
Don't move on until
- Chart of accounts and master-data counts confirmed
- History strategy agreed: balances, open items, or full transactional detail
- External auditor consulted on the migration approach
02 Data Audit Reconcile the source before you migrate it — you cannot fix a ledger later.
Objective A source ledger that balances, with master data cleansed and every open item agreed.
Keep these open
-
Produce and sign off a source trial balance
Run the trial balance in QuickBooks and have the controller sign it. This is your migration baseline: without a signed pre-migration position you have nothing to reconcile the target against, and any later discrepancy is unarguable.
Without a signed, dated source trial balance you cannot prove the migration preserved the ledger. Do this before anything else.
-
Reconcile subledgers to the general ledger
Confirm AR, AP, inventory and fixed-asset subledgers tie to their GL control accounts. Pre-existing breaks must be resolved in QuickBooks: migrating an out-of-balance ledger makes the break permanently unattributable.
Data Profiler Profile the QuickBooks export for nulls, outliers and type drift -
Clean and deduplicate master data
Deduplicate customers, vendors and items, and identify records that should not carry forward. Duplicate vendors are also a fraud-control weakness, so this has value beyond the migration.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Agree open AR and AP item by item
Every open invoice, credit note and payment on account needs an owner and an agreed amount, including partially-paid items and foreign-currency balances. Open items are what customers and vendors will dispute in week one.
-
Validate export structure, encoding and precision
Check numeric precision and rounding on the export, and confirm dates and currency codes are unambiguous. Precision loss on amounts is silent, cumulative and produces penny differences that take days to trace.
Amounts exported at reduced precision will not re-total. Verify decimal places before you accept the export.
CSV Validator Catch broken headers and ragged rows in the raw export -
Scan for regulated data and produce masked test data
ERP data holds bank details, tax IDs and payroll information. Scan it, restrict who can see it, and generate a masked copy for the sandbox and for any implementation partner.
PII & Compliance Scanner Find regulated fields before they land in a new system
QuickBooks → Wave specifics
- Full historical migration
- Every transaction since inception. Highest fidelity, highest effort.
- Current fiscal year + opening balances
- Import only the current year's transactions and set opening balances for prior periods via journal entries. This is the most common approach.
- Opening balances only
- Enter a single set of opening balances as of the cutoff date. Fastest, but historical transaction detail is lost in Wave.
- Big bang
- Stop posting in QuickBooks at cutoff, finish migration, go live in Wave.
- Opening-balance-only
- Archive full QuickBooks history, move only opening balances and current operations into Wave.
Don't move on until
- Trial balance in QuickBooks balances and is signed by the controller
- AR and AP subledgers reconcile to the GL control accounts
- Master data deduplicated and inactive records identified
03 Field Mapping Map the COA, the dimensions and the subledger structures.
Objective A signed mapping covering the chart of accounts, dimensions, tax codes and currency handling.
Keep these open
-
Map the chart of accounts account by account
Every source account maps to exactly one target account, or to a documented split with agreed proportions. The controller reviews and signs this line by line — an unreviewed COA map is how a balance sheet stops balancing.
Schema Mapper Opens pre-loaded with the QuickBooks → Wave field pair -
Map dimensions, cost centres and analysis codes
ERPs differ structurally here: segments, dimensions, tracking categories and classes are not interchangeable. Confirm how Wave models analysis and whether your existing reporting hierarchy survives the translation.
-
Map tax codes, rates and jurisdictions
Map every tax code with its rate, jurisdiction and reporting treatment, then verify the mapping reproduces your last filed return. Tax errors are statutory exposure, not reporting inconvenience.
A tax-code mapping that has not been tested against a previously filed return is untested. Reproduce a real filing before sign-off.
-
Decide multi-currency and exchange-rate handling
Confirm functional and reporting currencies, and how historical rates are stored. Revaluing historical transactions at current rates rewrites reported results and will not tie to filed accounts.
Historical transactions must retain their original transaction-date rates, or your comparatives will not match filed statements.
-
Map master data and subledger structures
Map customer and vendor records with their payment terms, credit limits and tax registrations, and item records with units of measure and costing method. Costing-method differences change inventory valuation, which changes the balance sheet.
-
Set load order and freeze the spec
COA, then dimensions, then master data, then opening balances, then open items, then any historical detail. Version and sign off the spec with the controller before the pilot.
Don't move on until
- Account-by-account COA mapping reviewed by the controller
- Tax codes and jurisdictions mapped and verified against filings
- Multi-currency and rate handling agreed with finance
04 Test Migration Prove the ledger balances in the target before you trust it.
Objective A sandbox load whose trial balance matches the signed source position to the penny.
Keep these open
-
Configure the Wave sandbox with the agreed structures
Build the COA, dimensions, tax codes, currencies, fiscal calendar and posting rules before loading anything. Every one of these affects how a posted transaction lands, so an unconfigured sandbox produces meaningless results.
-
Load master data and validate it
Load customers, vendors and items first and verify counts, payment terms, tax registrations and costing methods. Transactions cannot post correctly against wrong master data, so this gate comes before any balance work.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Load opening balances and prove the trial balance ties
Load opening balances and run a trial balance in Wave, comparing to the signed source position. It must match exactly — a rounding difference here is a mapping defect, not a rounding difference.
Any variance at all between source and target trial balance must be explained line by line. "Close enough" is never acceptable in a ledger.
-
Load open items and reconcile the subledgers
Load open AR and AP with their ageing intact, then confirm subledger totals tie to GL control accounts and that ageing buckets match. Ageing that shifts means transaction dates mapped wrongly.
-
Run a full period-end close in the sandbox
Execute the whole close: revaluation, accruals, depreciation, tax calculation, and financial statement generation. Compare every statement to QuickBooks for the same period. The close is where structural mapping errors finally become visible.
-
Test transactions end to end and reproduce a tax filing
Post a sales order to cash and a purchase order to payment, then generate the tax return for a previously filed period and compare it to what you filed. If both reconcile, the configuration is sound.
-
Record counts per entity type
Customers, vendors, invoices, products — compare totals between source and target.
QuickBooks → Wave specifics
- Spot-check invoice totals and payment amounts
- Pick 10–20 invoices at random and verify amounts, dates, and line items match.
- Relationship integrity
- Confirm payments are linked to the correct invoices. Confirm line items reference the correct products and revenue accounts.
- UAT with your bookkeeper
- Have the person who actually uses the system verify that their workflow works in Wave.
Don't move on until
- Target trial balance matches the signed source trial balance exactly
- Subledgers reconcile to control accounts in the target
- A full period-end close has been run in the sandbox
05 Cutover Switch the ledger on a period boundary, with balances proven.
Objective Balances and open items live in Wave, transacting resumed, and a signed post-load trial balance.
Keep these open
-
Close the final period in QuickBooks and freeze posting
Complete the period-end close, then lock posting entirely. An ERP freeze is absolute: a single journal posted to the old system after the final export leaves the two ledgers permanently divergent.
One journal posted in the old ERP after the final export breaks the reconciliation permanently. Lock posting at the system level, not by asking people nicely.
-
Publish the cutover runbook with the abort point
A timed, owner-named sequence for load, balance verification, integration switch and go/no-go, with an explicit abort criterion. The trial-balance check is the gate — nothing proceeds until it ties.
-
Load balances and open items into production
Load the final opening balances and open AR/AP into Wave production, following the pilot-proven sequence. Do not improvise the order under time pressure.
-
Reconcile and sign the post-load trial balance
Run the trial balance in Wave and reconcile it to the signed source position, then have the controller sign the result. This signature is your evidence for the auditor and your go/no-go gate.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint banking, payment and tax integrations
Switch bank feeds, payment gateways, tax filing connections, payroll and BI, then process one real low-value payment and one bank reconciliation end to end. Banking errors move real money, so verify with live traffic.
Payment integrations left connected to the old ERP can duplicate real payments. Disable them before switching, not after.
-
Go/no-go, then open for transacting with daily reconciliation
Call the decision on the signed trial balance, open Wave for posting, and reconcile daily for the first two weeks with finance support on hand. Keep QuickBooks read-only for statutory retention — this is an audit requirement, not a preference.
Don't move on until
- Post-load trial balance signed by the controller
- Banking, tax and payment integrations verified live
- Users transacting and the first daily reconciliation clean
06 Validation Prove the statements, the tax position and the audit trail.
Objective Financial statements reproducing the source position, a clean tax filing, and auditor acceptance.
Keep these open
-
Reconcile the full ledger and all subledgers
Reconcile trial balance, AR, AP, inventory, fixed assets and bank against the signed source position. Produce a single reconciliation pack that goes to the auditor.
Migration Validation Tool Reconcile QuickBooks and Wave record-for-record -
Reproduce the financial statements
Generate balance sheet, P&L and cash flow in Wave and compare to the pre-migration statements. Every variance needs a documented explanation traced to a specific mapping decision.
-
Complete and review the first period-end close
Run the first real close in Wave with extra review at every step. Compare its duration and outcome to your historical close, and treat anything unexpected as a live finding.
Data Profiler Prove field completeness held up through the load -
Verify the tax position and file
Generate and review the first tax filing from Wave, reconciling it to the underlying transactions before submission. Have the tax lead review it independently.
The first statutory filing out of a new ERP should be reconciled manually to source transactions before submission.
-
Confirm controls, segregation of duties and audit trail
Verify user permissions, approval limits, segregation of duties and audit logging in Wave. Controls do not migrate, and a control gap found by an auditor is far more expensive than one you find yourself.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Obtain auditor acceptance and retain the archive
Walk the auditor through the reconciliation pack, get written acceptance, and retain QuickBooks read-only for the full statutory retention period. Diarise the retention expiry rather than the contract renewal.
-
Validate after each entity family,
not only at the end. Catching errors early prevents cascading failures downstream.
Don't move on until
- Financial statements match the pre-migration position
- First period-end close completed and reviewed in Wave
- Auditor satisfied and archive retained for the statutory period
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Chart of Accounts | medium | Wave supports standard account types and CSV import via Wave Connect, but QuickBooks account hierarchies and types without Wave equivalents require manual remapping or flattening. |
| Customers | low | Customers can be imported via CSV or created through Wave's GraphQL API, though QuickBooks sub-customer hierarchies will be flattened into a single level. |
| Vendors | high | Wave's GraphQL API does not expose vendor creation mutations, so vendors must be manually created through the UI or CSV import, creating a bottleneck for automated pipelines. |
| Invoices | medium | Invoices can be created via Wave Connect or the API's invoiceCreate mutation, but line-item product references and payment linkages require careful ID mapping to preserve relationships. |
| Bills and Purchase Orders | high | Wave has no purchase order functionality and no bill creation API mutation, so all QuickBooks bills must be manually recreated and purchase order data is entirely lost. |
| Inventory Items | high | Wave does not calculate or track unit inventory value, so all QuickBooks inventory quantities, valuations, and COGS tracking must be abandoned or managed in an external system. |
| Products and Services | low | Non-inventory products and services can be imported via CSV or the productCreate API mutation, though QuickBooks item hierarchies will be flattened to Wave's single-level structure. |
| Journal Entries | medium | Journal entries can be uploaded through Wave Connect, but they require precise formatting and are critical for setting accurate opening balances that all downstream reports depend on. |
| Bank Transactions | medium | Historical bank transactions can be imported as CSV, but live bank feeds must be reconnected from scratch via Plaid in Wave, and prior reconciliation status does not transfer. |
| Class and Location Tracking | high | Wave has no equivalent to QuickBooks class or location dimensions, so all dimensional tracking data must be discarded, embedded in account names, or maintained in an external system. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Inventory Tracking Support
Wave does not calculate or track unit inventory value, meaning all QuickBooks inventory items, COGS calculations, and stock quantities must be flattened into simple products or tracked externally.
Opening Balance Corruption Risk
Incorrect opening balances propagate errors to every downstream financial report, and Wave provides no automated mechanism to pull or validate prior-period balances from QuickBooks.
Dimensional Data Loss
QuickBooks class and location tracking dimensions have no equivalent in Wave, requiring that all dimensional metadata be either flattened into account names, stored externally, or discarded entirely.
Vendor and Bill API Gap
Wave's public GraphQL API does not expose vendor creation or bill creation mutations, forcing vendors and bills to be created manually through the UI or CSV import before they can be referenced programmatically.
Relational Link Breakage
Wave's CSV import ingests flat records without preserving accounting relationships, so payments will not automatically associate with their corresponding invoices and line items will not reference products.
Currency and Geography Constraints
Wave restricts business currency to USD or CAD set permanently at account creation and is available only in the US and Canada, making migration impossible for multi-currency QuickBooks setups or businesses outside those regions.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate QuickBooks inventory data to Wave?
No. Wave does not calculate or track inventory unit values. QuickBooks inventory items must be mapped to standard Wave products/services, and all quantity-on-hand, COGS tracking, and valuation data is lost. Archive your final QuickBooks inventory valuation report before migrating — you'll need it for tax purposes.
Does Wave have an API for importing QuickBooks data?
Wave has a GraphQL API that supports creating customers, accounts, products, invoices, estimates, and transactions. However, it lacks vendor creation mutations and bill creation mutations in the current public schema, and the moneyTransactionCreate mutation is still marked BETA. There is no direct QuickBooks-to-Wave import feature.
What QuickBooks features does Wave not support?
Wave lacks inventory management, purchase orders, budgeting, project/job costing, class and location tracking, audit trails, and time tracking. It also has limited multi-currency support compared to QuickBooks, and recurring bills cannot be migrated.
Should I migrate all historical transactions from QuickBooks to Wave?
In most cases, no. The recommended approach is to migrate the current fiscal year's transactions and set opening balances for prior periods via journal entries. Full historical migration is high-effort and often unnecessary if you archive the QuickBooks file for reference.
Is QuickBooks Desktop harder to migrate to Wave than QuickBooks Online?
Yes. QuickBooks Online has a paginated REST API for extraction. Desktop has no cloud API — you must rely on the QBXML SDK, the Web Connector, or manual CSV/IIF exports. IIF files only export lists, not full transaction history, making Desktop migrations significantly more complex.