Moving from Zoho Books to Odoo for Canadian organisations

List every Zoho Books organization, legal entity, branch, module, custom field, reporting tag, tax rule, currency, warehouse and connected app. Record which features are used in practice rather than merely enabled, the historical period to move, what will be retired and who can approve the extraction and final balances.

Collect trial balances, contacts, items, open invoices and bills, credit and debit notes, advance and unapplied payments, inventory adjustments, bank accounts and reconciliation reports. Include custom fields and API/export names because a visible label may not be the machine identifier needed for repeatable loading.

Reviewed 6 November 2026. Revalidation owners: migration lead, accountant, application owner, data reviewers and bank/inventory reviewers before later use.

• Organization and entity identifiers: __________
• Modules, custom fields, tags and warehouses: __________
• History and systems to retire: __________
• Export and financial approvers: __________

Use an external ID composed of organization, record type and source identifier so it remains unique across Zoho entities and years. Preserve the source ID in the mapping even if the visible name changes. Store Odoo ID, run version and status beside it to support a later audit or controlled rerun.

Write the import order for organizations and currencies, accounts, parties, items and warehouses, followed by documents, payments, bank transactions and stock. When a parent is rejected, stop its dependants or invoke the documented repair rule. Do not let an invoice, payment or credit note bind to an unintended party because of a fuzzy name match.

• External-ID composition and uniqueness check: __________
• Dependency order and parent rejection rule: __________
• Rejected row, cause, repair and rerun: __________

Run a representative batch twice and compare created, updated, rejected and skipped counts. A rerun must update only the intended records and never create another customer, invoice, credit note, payment or stock movement.

Reconcile item type, unit of measure, tracking, quantity, unit cost and value by warehouse and cut-off date. Compare the inventory report with the ledger and explain any presentational difference between Zoho and Odoo. Service items and non-inventory items must not acquire stock quantities by mapping accident.

Odoo 19 landed costs can allocate eligible freight, insurance, duties and other charges. Verify AVCO/FIFO prerequisites where required and treat Standard Price as a separate validation path. Rehearse an imported purchase with receiving, a partial sale before freight arrives and a second sale afterwards.

Record before/after values, allocation basis, entry, remaining quantity and financial statements. Test returns, transfers and a stock count. Quantity without value, an unsupported cost distribution or a late-cost adjustment without an owner blocks sign-off.

Decide which Zoho modules and integrations stop, when entry freezes, which final exports are approved and who can authorize cutover. Keep read-only access to Zoho Books with retention responsibilities, and document how an old feed cannot recreate unapproved records. Include a transaction arriving during the freeze and its handling.

Prepare English/French role cards for sale, purchase, credit, payment and close. After migration, reconcile the first period, open documents, inventory and banks, and track defects to closure. If rollback is required, preserve the run evidence and prevent a live integration from reintroducing records while the decision is reviewed.

Continue with the CAD reconciliation workbook, the tax and bilingual discovery workbook, the branch/POS checklist and the bilingual training plan. Oakland is an official Odoo Gold Partner delivering remotely from the UAE around agreed Canadian time zones; bring one representative Zoho export to discovery, assign an owner for every residual and agree the next rehearsal.