Case study · Migration

QuickBooks Desktop to Odoo for an engineering contractor's two project entities

Two sets of books, one desktop accounting program and a tax authority that now wants invoices filed electronically. We moved both entities into Odoo and agreed every opening balance to the old trial balance before cut-over.

The client

An international engineering contractor with two project entities in Pakistan, each keeping its own books in QuickBooks Desktop. We do not name clients on this site; we are happy to talk about the work in detail on a call.

What needed to change

  • Two entities on QuickBooks Desktop, each on its own machine.
  • Sales tax invoices that had to be reported to FBR electronically.
  • Lists of customers, vendors, items and accounts built up over years, with duplicates.

What we built

No.PartWhat it means in practice
01Lists out of QuickBooksCustomers, vendors, items and the chart of accounts exported to Excel, cleaned and de-duplicated before anything was loaded.
02Mapped, then loaded through the APIEach list mapped to Odoo's structure and loaded through Odoo's API rather than by hand, so the load could be repeated on a fresh database until it was right.
03Opening balances tied outOpening balances for each entity agreed to the QuickBooks trial balance at the cut-over date. Differences were explained, not posted to a suspense account.
04FBR e-invoicingSales tax invoices set up to file with FBR, so the first return after go-live comes from Odoo and not from a spreadsheet.

How it runs now

Both entities keep their books in Odoo. The method used here is the one on our QuickBooks Desktop page: read the books first, load into staging, agree everything, then cut over.

Built with: QuickBooks Desktop, Odoo, Odoo external API, Excel, FBR digital invoicing.

WhatsApp

Book a meeting

Free 30-minute call