Odoo to QuickBooks Enterprise: a staged migration playbook

An Odoo-to-QuickBooks Enterprise move fails without a planned cutoff, settled multi-currency and inventory decisions, and a validated trial import.

Odoo and QuickBooks Enterprise keep books on different models, so this job is a conversion rather than a copy. Our engineers run it as a fixed sequence: fix a cutoff, export, settle the hard questions, prove the result in a trial company, then cut over. Every phase below ends at a point you can retreat from.

Scope the move and fix the cutoff date

Aim for a fiscal year end, or a month end if the business cannot wait that long. The cutoff should fall on the last day of a closed Odoo period, with nothing in flight. Then decide how much history crosses: full years, or a cutoff balance plus open items. Write the decision down, because every later step refers back to it.

Volume decides the effort. Count transactions, customers, and vendors, and name the target Enterprise version. Those figures also scope a handled job: our Odoo to QuickBooks conversion service is sized from exactly those inputs. Rollback point: nothing here is irreversible until exports begin.

Export the master records

Pull the chart of accounts, customers, vendors, and items into staging spreadsheets. Expect to reshape rather than translate. QuickBooks caps customer and vendor names at 41 characters and item names at 31, so shorten long Odoo names by rule, not by hand. A partner who both buys and sells becomes two records; QuickBooks forbids the same name on the customer and vendor lists.

Map every account to a QuickBooks type before anything imports. Receivable and payable accounts need exact counterparts, or the aging reports arrive empty. Rollback point: the staging sheets are disposable until the first load, so revise freely.

Export transactions from the cutoff forward

Take invoices and refunds, bills and credits, payments, bank lines, and journal entries from the day after the cutoff. Use the start of history instead if you chose full years. Keep Odoo's document numbers in a reference field so any imported transaction traces back.

Payments should land in undeposited funds by default, then group into deposits the way QuickBooks expects. Odoo's automatic postings, such as accruals and exchange gains, need a ruling: import them as journals, or rebuild them the QuickBooks way. Decide once and apply the rule everywhere.

Settle multi-currency before the company file exists

Two settings are permanent: the home currency, fixed when the file is created, and multi-currency, which cannot be turned off once on. Decide both before the first import. If the target stays multi-currency, set up currency gain and loss accounts and expect timing differences in when gains land.

If the target will be single currency, convert foreign balances into the home currency at the cutoff, keeping original amounts in a reference field. Our engineers treat currency setup as the one decision here that cannot be revisited. If multi-currency is already on in an existing QuickBooks file, turning multi-currency off in QuickBooks is a service job, not a preference.

Settle inventory valuation and item types

Odoo values stock at FIFO or moving average by warehouse, with lots and serials in the core product. QuickBooks Enterprise values inventory parts at weighted average cost and adds locations, lots, and serial numbers through its Advanced Inventory module. Cost of sales can differ on the same sale, so do not try to make history agree line by line.

The workable pattern imports the item list and open sales orders, then loads quantities and total value at the cutoff with one inventory adjustment. The inventory asset account then ties without replaying every stock move. Clear negative quantities in Odoo first, because QuickBooks costing degrades badly below zero. Kits and bills of material become assembly items only if you will keep building them in QuickBooks.

Run the trial import

Load into a disposable trial company, never into the file you intend to keep. Import in strict order: accounts, then names, then items, then cutoff balances, then transactions by date. This phase exists to break things cheaply.

When an import fails, fix the export and reload from the top. Never patch a half-loaded trial company; afterwards you cannot tell a real discrepancy from a partial load. Rollback point: the trial company itself. Delete it and start clean whenever doubt creeps in.

Validate the trial company

Run the built-in verification utility first and clear anything it flags. Then compare four reports against Odoo at the cutoff date. Check the trial balance account by account, receivables aging by customer, and payables aging by vendor. Add the inventory valuation summary against Odoo's stock valuation.

Every difference needs an explanation you can state in one sentence. Enter a week of test transactions and re-run the comparison before you trust the file.

The live cutover

Freeze entry in Odoo, snapshot the database, and run the final export from the frozen copy. Import into production using the sequence proven in trial, then back the file up before anyone else logs in. Keep Odoo read-only for lookups and audit questions.

Rollback point: if validation fails here, restore the backup, unfreeze Odoo, and return to the trial phase. The frozen snapshot is the ultimate retreat; it holds a complete set of books at the moment of cutover.

The signs of a clean cutover

A clean outcome is checkable, not a feeling. The trial balance at the cutoff ties to Odoo to the cent, or to a documented rounding. Aging reports match by name, not merely in total. The inventory asset account agrees with the item valuation summary and with Odoo's valuation at the cutoff. The file passes verification. New invoices, bills, and payments post and report normally. Odoo sits archived and unedited, able to answer for every year before the cutoff.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.