Octagotech · Certified Odoo Ready partner · octagotech.com · sales@octagotech.com · USA +1 917 254 9416 · India +91 8153897751

Guide · Migration checklist

The QuickBooks to Odoo migration checklist

By Octagotech TeamUpdated

Every step from the first decision to cutover, in the order we run them: what to export, what to clean, the order to load, how to reconcile, and how to go live without two systems fighting over the books.

Book a discovery call

Save as PDF opens your browser's print dialog. Your ticks print with the page.

4phases, from kickoff to go-live1opening entry, not years of history30-dayhypercare

This guide

What is inside

Stages
6, from decisions to cutover
Checks
39, each one tickable
Use it
Before anyone exports a file
Time to read
About 10 minutes
Your ticks
Saved in this browser only
Cost
Free, no email gate

0 of 39 done · ticks stay in this browser

Stage 1

Decide before you export

Five decisions set the size of everything that follows.

0 of 5
  • Ideally the fiscal year-end, and always a date that matches a reconciled close in QuickBooks. A mid-period cutover leaves partial-period transactions in two systems and a painful year-end.

  • One accountant-reviewed journal entry on the go-live date captures assets, liabilities, equity, open receivables and open payables. Historical transactions stay in QuickBooks, accessible for reference through the audit retention period.

  • Auditing is fast; cleaning needs decisions from business owners, and those take calendar time.

  • Someone who can make data decisions and escalate blockers the same day, not someone giving the migration 20% of their week. Every deferred decision is a delay.

  • Budget a dedicated week for chart of accounts mapping with your controller or CFO in the room, not delegated to a junior accountant. Every mapped line needs their sign-off.

Stage 2

Export from QuickBooks

What to pull out, and the Odoo record each one becomes.

0 of 7
  • Becomes account.account. Account types get remapped to Odoo's structure, so export them with the accounts.

  • Becomes res.partner. Include payment terms and tax status; both get mapped before import.

  • The same res.partner model as customers, loaded with supplier_rank > 0.

  • Becomes product.template. Categories, units of measure and costing methods are defined in Odoo before these load.

  • Becomes account.move. Unpaid and partly paid documents only; paid invoices are covered by the opening balance.

  • The trial balance becomes the opening journal entry. The receivables and payables aging reports are the numbers Odoo's open balances must match.

  • Decide how they come across: recreate them in Odoo with the correct received quantities, close them in QuickBooks first, or bring only the truly open ones. Partly received orders need procurement, finance and operations in the same meeting.

Leave behind

  • Historical transactions. Weeks spent migrating them are wasted when, after go-live, people just open QuickBooks to look things up.
  • Paid invoices and bills. The opening balance already covers them.
  • Attachments and scanned documents, usually. High effort, low return: archive them in cloud storage and link as needed.

Stage 3

Clean before you import

Every problem fixed here is one you do not reconcile later.

0 of 6
  • QuickBooks collects "ABC Corp", "A.B.C. Corp" and "ABC Corporation" over the years. Merge them first; every transaction that points at the wrong version becomes a reconciliation error that compounds.

  • Retire redundant product records before they reach Odoo, not after.

  • A country on every contact is not mandatory in Odoo, but it is strongly recommended because taxes and address formats depend on it, and your old system may never have asked for one.

  • Merge duplicate accounts, retire the ones created for projects that ended, and remap account types to Odoo's structure, with finance sign-off on every line.

  • Odoo sets the costing method (standard, FIFO or average cost) on the product category, not the product. Import 5,000 products without categories and each one gets re-categorized by hand, with inventory valuation and cost of goods sold wrong downstream.

  • QuickBooks tax codes do not map one-to-one to Odoo. A "tax exempt" customer becomes a fiscal position that swaps standard taxes for zero-rate taxes on every document. Skip the mapping and whole customer segments get the wrong tax from day one.

On our migrations, we provide the cleanup templates and checklist; your data owners make the calls.

Stage 4

Load in this order

Each load depends on the one before it: products need their categories, and open invoices point at contacts and products that must already exist.

0 of 8
  • Build and validate the import scripts in a staging environment, with no production data touched. Run at least two full dry-runs: one early, and a final one on near-production data no more than a week before go-live.

  1. The cleaned, mapped structure everything else posts to.

  2. The category carries the costing method each product will use.

  3. Loaded into categories that already exist.

  4. De-duplicated, with fiscal positions and payment terms mapped.

  5. Dated the cutover date, and reviewed by your accountant.

  6. Last, because they reference the accounts, contacts and products loaded before them.

  • Compare each import with its expected record count, and spot-check records against the QuickBooks file.

Stage 5

Reconcile before you sign off

Go-live waits until the numbers agree, or every difference is explained.

0 of 7
  • Accounts, categories, products, contacts and open documents, one by one.

  • Run a trial balance in both systems for the same period and reconcile the difference to zero, or document every intentional adjustment.

  • Customer balances that do not match your AR aging report are a classic day-one surprise. Catch them here.

  • Go-live is not confirmed until that signature is on file.

  • A business stakeholder, not only the IT lead, reviews the migrated records and confirms they look right.

  • Sales order to invoice, vendor bill to payment, purchase order to inventory receipt. Log every discrepancy and resolve it before go-live sign-off.

  • Five to ten reports the business relies on weekly, run for the same period. They need not match exactly, but every variance is explained.

Stage 6

Cut over

One system of record from the cutover date, with a way back if you need it.

0 of 6
  • A cold cutover makes QuickBooks read-only from day one. It works when the migration was thorough, testing is complete and support is on hand at go-live.

    A parallel run doubles data entry, so keep it for when regulation demands it, when a rough first day is unaffordable, or when you expect reconciliation issues to catch in real time. For most projects, we recommend the cold cutover.

  • Timestamps, named owners and go/no-go points, plus the last moment you can still revert to QuickBooks and who makes that call.

  • At the end of the fiscal month, matching the reconciled close in QuickBooks.

  • History and audits are answered there, through the audit retention period. New transactions go into Odoo only.

  • Integrations on production credentials, security roles, email, scheduled actions, training and a timed restore drill: the 12-point pre-go-live checklist.

  • Priority response through the first month for questions, fixes and training gaps. On our migrations, the support team watches the system for those 30 days.

The five rules

  • Opening balance, not transaction history
  • De-duplicate before import, not after
  • Categories and costing before products
  • Cut over at month-end, never mid-period
  • Fiscal positions mapped before the first invoice

Ready to leave QuickBooks?

A 30-minute call on your data, your workflows and a realistic migration timeline.

Book a discovery call

When we run it

How the checklist maps to our four phases

Four phases from kickoff to go-live, each mapped to the checklist stages.

Odoo upgrade and migration services
  1. Phase 1

    Audit

    Stages 1 and 2. The full data set extracted, every quality issue logged, and workflows mapped to standard Odoo apps. You leave with a signed migration blueprint and a fixed-scope plan.

  2. Phase 2

    Map

    Stage 3. Categories, costing methods, fiscal positions, payment terms and journals defined, and import scripts validated in staging. No production data is touched.

  3. Phase 3

    Migrate

    Stage 4. The production load in order, each import checked against record counts. Your accountant signs off the opening balance while training runs in parallel.

  4. Phase 4

    Validate

    Stages 5 and 6. End-to-end scenarios in production Odoo, every discrepancy resolved before sign-off, then 30 days of hypercare.

Plan your move off QuickBooks

The first call takes 30 minutes.

Or email sales@octagotech.com