Migrate from eBIZ SMARTZ Business ERP to Odoo ERP

Direct map: each eBIZ SMARTZ account code becomes an Odoo account.account record with the matching code, name, account_type (asset, liability, equity, revenue, expense), and reconcile flag set. Account codes must be cross-referenced before insertion because eBIZ SMARTZ numeric codes do not map 1:1 to Odoo's account code constraints.

Direct map: eBIZ SMARTZ customer records map to Odoo res.partner with type='customer'. Each partner receives an external ID (x_source_id) for traceability and future delta synchronization. Address records (street, city, state, zip) map to res.partner child records using the contact_address mechanism, and customer-specific fields like payment terms map to property_payment_term_id.

Direct map: eBIZ SMARTZ vendor records map to Odoo res.partner with type='vendor'. Bank account details, payment terms, and fiscal country settings are preserved as partner bank records (res.partner.bank) linked by partner_id, with vendor_rank=1 set to enable vendor-specific filtering in Odoo purchase workflows.

eBIZ SMARTZ product records map to Odoo product.template (for name, uom, type) and product.product variants where the source has attribute-based variants. Product type (stockable, consumable, service) maps to Odoo's product.template.type field. Unit of measure conversions handled via uom.uom mapping, with uom_category matching to ensure dimensional consistency across the product catalog.

eBIZ SMARTZ vouchers map to Odoo account.move with line_ids. Each voucher line maps to account.move.line with matching debit/credit amounts, account_id resolved via the account cross-reference table, and partner_id set when the line references a customer or vendor. Original voucher number stored in move_ref for audit trail and source traceability.

eBIZ SMARTZ sales invoices map to Odoo account.move with move_type='out_invoice'. Invoice lines map to account.move.line with product_id, quantity, price_unit, and tax_ids resolved via the tax cross-reference table. Payment terms from eBIZ SMARTZ map to account.payment.term on the Odoo move, and the original invoice number is preserved in the move name field for reference.

eBIZ SMARTZ purchase invoices map to Odoo account.move with move_type='in_invoice'. Vendor bill lines use the same account.move.line structure with purchase_price_unit and tax_ids mapped from source tax codes. Bill date and due date are preserved from the source, and the vendor partner is linked via partner_id on the move header.

Multi-level cost-center hierarchies in eBIZ SMARTZ map to Odoo account.analytic.account records. Each eBIZ SMARTZ cost-center node becomes one analytic account with its parent_id set to the parent cost-center's Odoo ID, preserving the reporting hierarchy within Odoo's analytic accounting module and enabling cost rollup reports across all levels of the organization.

Direct map: open purchase orders in eBIZ SMARTZ map to Odoo purchase.order records with vendor_id, date_order, and line_ids. Line-level product_id, product_qty, and price_unit map directly to purchase.order.line fields. Purchase order state (confirmed, pending) maps to Odoo's state field, and the Odoo internal reference links back to the source PO number via the name field.

eBIZ SMARTZ inventory stock records map to Odoo stock.quant entries linked to product_id and location_id. Odoo requires stock.location records to exist first; we create a default company location if the source uses a single-warehouse model, and map warehouse codes to Odoo stock.location complete_name for multi-warehouse configurations.

Direct map: eBIZ SMARTZ asset records map to Odoo account.asset with asset name, original_value, depreciation_date, and method fields populated from source data. Depreciation lines are computed by Odoo's asset computation engine using the original values and method migrated from eBIZ SMARTZ, ensuring the same depreciation schedule is produced without manual recalculation or re-entry.

Approval chains defined in eBIZ SMARTZ have no native equivalent in Odoo. We export the approval configuration as a structured JSON document listing document types, user levels, and threshold amounts so your Odoo admin can rebuild the approval sequence using Odoo Studio approval flows or a third-party workflow app.