Migrating from Odoo

What the Migration Cockpit does with an Odoo export: account types converted to the five kinds, vendor, customer and product hints, the default currency, warnings at the check, and invoice numbers kept as a reference under ZATCA.

• Platform › Legacy Migration › Migration Cockpit: Work out the mapping proposes Odoo’s columns as “Suggested: … Confirm before loading.”
• Accounts: Odoo’s account_type is converted to asset, liability, equity, revenue or expense (asset_cash → asset, liability_payable → liability, income_other → revenue, expense_depreciation → expense, and Odoo’s display names likewise). off_balance is refused by name: leave memorandum accounts out of the export.
• Vendors and customers: ref becomes the number, email is lower-cased, Country should be exported as the code (AE, not the name), and payment terms such as 30 Days become days.
• Products: default_code becomes the item number; Storable/Goods, Consumable and Service are mapped, and units such as Units → EA.
• Invoices: export the Type field (move_type); customer and vendor invoices and credit notes are told apart by it.
• Columns with no home here (vat, company_id, the Odoo id) are named at the check; the Odoo id is kept as the row’s legacy reference.
• Currency when the file does not say fills a missing or blank currency.

Check the rows now warns, without refusing, when a field takes its default on every row because its column is not mapped, or when a value is not one the map converts and the field takes the column default. A required field with an unknown value refuses that row: add the value to the map, or leave the row out. Rehearse the load works for open items too.

Invoice numbers under ZATCA

For a company not under ZATCA, Keep the ones from Odoo keeps numbers such as INV/2026/00412. Under ZATCA the invoice, credit note and debit note series are numbered by the system only, so each migrated invoice is numbered here (a draft number now, its tax invoice number when issued) and the Odoo number is kept as the invoice’s reference and against its migration row. The check, the rehearsal and the load all say so.