Migrate from Syscom ERP to Odoo ERP

Syscom ERP GL accounts map to Odoo Accounting's account.account table. Account codes, names, and types (Asset, Liability, Equity, Revenue, Expense) migrate directly. We extract the active chart of accounts hierarchy and map parent-child relationships to Odoo's account.group structure. Active versus inactive status is preserved. If Syscom ERP uses a different chart of accounts structure for unrealized currency gains and losses in a multi-currency setup, those accounts are flagged as a required decision point before the load phase.

Syscom ERP item master records (SKU, description, unit of measure, standard cost, sales price) map to Odoo product.template with product.product variants generated for each unique attribute combination. Barcode, product category, and routing references migrate to product.product fields. We preserve Syscom ERP's cost and pricing tier data in Odoo's seller IDs and pricelist.line records. Custom fields on items require pre-migration schema deployment in Odoo before the product load phase.

Syscom ERP BOMs store multi-level product structures with component items, quantities, and operation routing. We extract the full BOM hierarchy and map it to Odoo's mrp.bom (Bill of Materials) and mrp.bom.line records. BOM versions and alternative BOMs require explicit version mapping in Odoo since there is no native versioning field on mrp.bom — we set the active BOM flag based on Syscom ERP's effective date. Multi-level BOMs are decomposed and resolved top-down so that sub-assemblies are loaded before their parent BOMs.

Syscom ERP customer records (billing address, shipping address, contact details, credit limits, customer-specific pricing) map to Odoo res.partner records with customer_rank set to 1. We extract the primary contact as the partner record and additional contacts as child res.partner records linked via parent_id. Customer-specific pricing migrates to Odoo product.pricelist rules scoped to the specific partner. Address and contact fields map to Odoo's street, city, state_id, country_id, phone, and email fields.

Syscom ERP vendor records (contact information, payment terms, bank details, lead times) map to Odoo res.partner records with supplier_rank set to 1. Vendor-specific notes migrate to the partner's internal note field. Payment terms from Syscom ERP map to Odoo's account.payment.term records and are linked via property_payment_term_id on the vendor partner. Bank details migrate to res.partner.bank records on the vendor partner.

Syscom ERP sales order headers and line items migrate to Odoo sale.order and sale.order.line. We preserve order number, order date, requested delivery date, and order state so that open orders can be continued and historical orders remain in Odoo as read-only records. Pricing, taxes, and discounts on lines migrate directly. Odoo requires the product variant to be resolved before line import, which we handle in the pre-load phase. Ship-to addresses map to sale.order's picking_policy and partner_shipping_id. We batch sales order loads by API call to respect Odoo's RPC rate limits.

Syscom ERP purchase order headers and lines migrate to Odoo purchase.order and purchase.order.line with vendor reference, expected delivery date, and line-item detail preserved. PO state (RFQ, Purchase Order, Received, Invoiced, Cancelled) maps to Odoo's state field (draft, sent, purchase, done, cancel). We resolve the vendor partner record before PO header import and the product variant before line import. Invoicing status from Syscom ERP (Not Invoiced, Partially Invoiced, Fully Invoiced) maps to Odoo's invoice_status field.

Syscom ERP work orders track production status, quantities, component consumption, and operation routing against a BOM. We map these to Odoo mrp.production records. The production state in Syscom ERP (Released, In Progress, Completed, Closed) maps to Odoo's state field (draft, confirmed, progress, done, cancel). Components consume from stock based on Syscom ERP's material allocation data, and we set mrp.production's bom_id, product_uom_qty, and component moves during migration. Operation routing from Syscom ERP maps to mrp.workorder records if the destination uses Odoo's detailed work order tracking.

Current on-hand inventory balances extract from Syscom ERP at the warehouse and bin level. We map these to Odoo stock.quant records linked to stock.location records (internal locations, partner locations, or virtual locations depending on the Syscom ERP location type). Multi-warehouse setups are supported by creating parent stock.warehouse records and child stock.location records in Odoo before inventory load. We migrate on-hand quantities and unit costs; transaction history (stock moves, adjustments) does not migrate as individual records but is summarized in the opening inventory valuation.

Syscom ERP user accounts (login, roles, permissions) map to Odoo res.users records. We extract user records by email match as the primary key. Roles and permission sets from Syscom ERP are reconciled against Odoo's access-control list (ACL) model; Odoo groups (Sales / Technical / Administration) provide the closest structural mapping. Any Syscom ERP user without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import resumes. We do not migrate Syscom ERP employee HR data as that falls outside Odoo's standard manufacturing and distribution module scope.

Syscom ERP custom objects and user-defined fields vary by module and customer configuration. We identify all custom fields during discovery and pre-deploy Odoo custom fields (ir.model.fields with track_visibility, selection options, or relational types) before any data load. Custom object schemas from Syscom ERP map to Odoo custom model records if the destination Odoo instance uses the Studio or developer mode to define new models, or to existing standard objects with extension fields. This phase requires the most pre-migration schema coordination and is scoped separately from the standard object mapping pass.