Migrate from AI Works to Odoo ERP

AI Works User records map to Odoo res.users. We match by email address as the dedupe key and carry over display_name, login, and active status. Access groups and security roles in AI Works require a manual mapping step during scoping because Odoo's access-rights model (record rules, groups per app) is configured in Settings > Users > Access Rights and must align with the Odoo apps the customer purchases.

AI Works Account records map to Odoo res.partner, with company-type distinction (is_company flag) separating vendors from customers. address fields (street, city, state, country) map to Odoo's address fields using standard CSV column headers. The account_type field in AI Works determines whether the Odoo partner is created with customer=True, supplier=True, or both. Partners are imported before any related Invoice or Purchase Order records to satisfy foreign-key constraints.

AI Works Invoice records map to Odoo account.move with move_type distinction: customer invoices map to out_invoice, vendor bills to in_invoice, credit notes to out_refund and in_refund. The invoice_date maps to date, invoice_number to name, and amount_total to amount_total with tax handled separately via Odoo's tax-code mapping. Line items map to account.move.line with account_id resolved from the AI Works line-account field to an Odoo account. If AI Works stores multi-currency, we configure Odoo's multi-currency on the res.currency and set rate locks on the migration date.

AI Works Purchase Orders map to Odoo purchase.order. PO status (Draft, Sent, Confirmed, Received) maps to Odoo's state field (draft, sent, purchase, done). Vendor account lookup resolves to the res.partner record created from the AI Works Account. PO lines map to purchase.order.line with product_id resolved from the Product mapping and qty_ordered mapped to product_qty.

AI Works Product records map to Odoo product.product (the stockable variant object) and product.template (shared attributes). We separate product_name, description, and list_price onto product.template while handling multi-variant products as separate product.product records with their own product_tmpl_id. If AI Works stores product_type (goods vs service), it maps to Odoo's type field (product vs service). Cost price maps to standard_price for inventory valuation.

AI Works inventory balances map to Odoo stock.quant records, with location_id resolved to the destination warehouse (or the default stock warehouse if AI Works uses a single-location model). quantity maps directly to Odoo's inventory_quantity or qty field. We configure the inventory valuation method (Standard Price, Average Cost, FIFO) before import because Odoo locks valuation entries at product.template level. Lot/serial number tracking requires additional mapping if AI Works stores these attributes.

AI Works custom fields on any core entity require registration as Odoo module fields. We create a Python model inheriting the target Odoo model (res.partner, account.move, etc.) with the field defined at the ORM level, and add the field to the corresponding XML view using xpath inheritance. This ensures custom fields persist across Odoo version upgrades. We document each custom field's Odoo type mapping (Char, Integer, Float, Selection, Many2one, etc.) during the scoping phase before writing any module code.

AI Works approval chains and document workflows are not migrated as Odoo automated actions. We audit every active approval chain, document its trigger conditions, approver assignments, and downstream actions, and deliver a written map recommending equivalent Odoo Studio or server action configurations for the customer's admin to implement post-migration. This is a documentation deliverable, not a data migration.

AI Works contacts attached to an Account merge into Odoo res.partner records with parent_id set to the company partner. If AI Works stores contact role or department, we preserve these in custom fields on the contact partner. phone and email map to phone and email fields; a dedicated function field maps to the partner's formatted address block.

AI Works tax rates map to Odoo account.tax records with the correct tax_scope (sale, purchase, none), amount_type (fixed, percent, group), and children taxes for compound tax structures. We configure fiscal positions (account.fiscal.position) to handle tax mapping differences for vendors and customers in different jurisdictions before any Invoice or PO import begins.