Migrate from Industry Software to Odoo ERP

Industry Software's Chart of Accounts maps to Odoo's account.account model. We extract the account code, name, account type (Asset, Liability, Equity, Revenue, Expense), and parent hierarchy. Odoo requires a predefined account type from its standard chart-of-accounts template; any Industry Software account types that do not map directly require manual configuration before migration. We flag accounts with non-standard types (e.g., statistical, memo accounts) for the customer's accountant to assign Odoo equivalents.

Industry Software Customer records map to Odoo res.partner with partner_type=customer. The customer name, address, contact details, tax ID, and payment terms migrate as typed fields. We resolve the Customer's primary sales account from the Industry Software AR account code and assign it to the Odoo res.partner property_account_receivable_id. Open AR invoices (unpaid sales invoices) migrate as account.move records in draft state for the customer's accounting team to validate before posting.

Industry Software Vendor records map to Odoo res.partner with partner_type=supplier. Tax ID, payment terms, and the Vendor's primary purchase account migrate as typed fields. Open AP bills (unpaid purchase invoices) migrate as account.move records in draft state. We resolve the Vendor's default expense account from Industry Software's vendor record to assign Odoo property_account_payable_id.

Industry Software open AR invoices (invoice header, line items, payment status) map to Odoo account.move with move_type=out_invoice in draft state. Invoice date, due date, total amount, and outstanding balance migrate. We preserve the original Industry Software invoice number as a reference field. The customer reconciles and posts these in Odoo; we do not post draft invoices because doing so would affect the Odoo accounting period before the customer has validated the opening balances.

Industry Software open AP bills map to Odoo account.move with move_type=in_invoice in draft state. Vendor reference, invoice date, due date, total amount, and outstanding balance migrate. The original vendor invoice number is preserved as the Odoo ref field. As with AR, we leave bills in draft for the customer's AP team to validate, match to purchase orders if Odoo's PO-matching workflow is active, and post.

Industry Software open AR/AP aging balances that represent historical period-end positions require special handling. We create an Opening Balance journal entry in Odoo (a journal entry in the Opening Journal with counterpart lines to the relevant AR/AP accounts) rather than individual invoice records. This is the standard Odoo approach for migrating opening balances from a legacy ERP. The customer's accountant must approve the opening balance amounts before we post the entry.

Industry Software product records map to Odoo product.template (the product definition) and product.product (the sellable/stockable variant). We extract product name, SKU code, description, standard price, cost price, product type (stockable, consumable, service), and the product category. If Industry Software uses attribute-based variants (size, color), we map these to Odoo's product.attribute and product.attribute.value models. UoM (unit of measure) from Industry Software maps to uom.uom with conversion factors preserved.

Industry Software current stock quantities per SKU and warehouse map to Odoo stock.quant. We resolve the Odoo product.product ID, the stock.location ID (internal warehouse location), and the on-hand quantity. Quant ID must be unique per product-location pair; duplicate quants from Industry Software require reconciliation before import. We do not migrate stock moves (transfer history) because Odoo rebuilds move history from the inventory valuation journal entries on receipt and delivery.

If Industry Software includes manufacturing or formulation data, BOMs map to Odoo mrp.bom records. Component products, quantities per finished good, operation steps, and work center assignments migrate. Odoo BOMs support type (kit, manufacturing, subassembly); we set the type based on Industry Software's recipe structure. We flag multi-level BOMs for the customer to validate because Industry Software and Odoo handle BOM explosion differently in the MRP engine.

Industry Software open purchase orders (POs) map to Odoo purchase.order in draft or sent state. Vendor, order date, expected delivery date, PO lines (product, quantity, price), and the PO status migrate. We do not migrate PO history (closed, received, invoiced POs) because Odoo rebuilds PO history through its own receipt and invoice matching workflow. Partially received POs migrate in their current state; the customer completes receipt in Odoo.

Industry Software open sales orders (SOs) map to Odoo sale.order in draft or sale order state. Customer, order date, promised date, SO lines, pricing, and discount structure migrate. Confirmed or shipped SOs migrate as historical records in a locked state. We do not migrate full SO history; Odoo's sale.order history rebuilds through its own pipeline. Partially delivered SOs migrate in their current state for the customer to complete in Odoo.

Industry Software custom fields and extended tables represent the greatest migration risk. We extract custom field definitions during discovery, map them to Odoo ir.model.fields where a typed equivalent exists (char, text, integer, float, date, datetime, many2one, many2many, selection). Fields with no Odoo equivalent (e.g., Industry Software-specific enumerated types) are flagged in the mapping document for the customer to either drop, store as a Char field, or implement as a custom Odoo module. We never assume a custom field is safe to drop; the customer decides on a field-by-field basis.

Industry Software user accounts and employee records map to Odoo res.users and hr.employee. We match by email for users. Active status, name, and login migrate. If Industry Software stores employee-specific data (department, cost center, manager hierarchy), we map this to Odoo's hr.employee model and org structure. We do not migrate user passwords; the customer resets passwords through Odoo's password reset flow after migration.