Migrate from Info.Net to Odoo ERP

Info.Net Items (finished goods, raw materials, components) map to Odoo product.product records with product.template as the shared name/description layer. We preserve SKU, description, unit of measure, standard cost, and any custom fields. Where Info.Net uses a specific uom_code not native to Odoo we create the corresponding uom.uom record during schema setup. Multi-unit Items (each with its own SKU) create separate product.product records sharing the same product.template.

Info.Net BOMs with component lines and revision versions map to Odoo mrp.bom records. Odoo distinguishes bom_type: 'kit' (phantom BOM that explodes components on a manufacturing order) versus 'normal' (standard build). We determine the correct type from Info.Net's BOM structure. Multi-level BOMs (sub-assemblies referencing their own BOMs) are resolved in dependency order: sub-assembly BOMs are imported first so parent BOMs can reference them via mrp.bom.line product_id resolution. Routing steps from Info.Net's production process map to mrp.routing.workcenter lines on the Odoo BOM.

Info.Net Production Orders track manufacturing jobs with status, quantity, scheduled dates, work center assignment, and completion metadata. We map them to Odoo mrp.production records preserving the original scheduled date, finished date, and scrap quantity. Production Order status (Draft, Confirmed, In Progress, Done, Cancelled) maps to Odoo's state field with the corresponding state machine transitions enforced at import time. Parent Work Orders reference the parent mrp.production record via the production_id foreign key.

Info.Net Work Orders assign production tasks to employees or work centers with start/end dates and labor estimates. We map them to Odoo mrp.workorder records linked to their parent mrp.production via production_id, and to the corresponding mrp.routing.workcenter via workcenter_id. We preserve the full work order lifecycle including status transitions, actual labor consumed, and any work center-specific notes. Work order timestamps carry forward as Odoo's date_start and date_finished fields.

Info.Net QC logs hold inspection results, pass/fail flags, and measurement data linked to production lots. Odoo does not have a native QC inspection object in standard Manufacturing, so we map QC records to a custom stock.production_lot record (tracking the lot or serial number) with measurement values stored in custom fields on the lot or a linked qc.measurement model. Pass/fail flags become lot stock_state or custom lot_quality_status fields. Field naming conventions differ between ERPs; we run a field-level audit during discovery to match each Info.Net measurement field to an Odoo target.

Info.Net Customer records include billing addresses, shipping addresses, and credit limits. In Odoo, customers live in res.partner with type='contact' for addresses. Multi-address accounts (ship-to and bill-to) use separate res.partner records with parent_id pointing to the main customer record. We map Info.Net address fields to Odoo's street, city, state_id, country_id, zip, and phone fields. Credit limits migrate as custom fields or to account.move.line-based credit management if Odoo Accounting is deployed.

Vendor master records from Info.Net (contact details, payment terms, lead times) map to Odoo res.partner records with supplier_rank > 0 to flag them as vendors. Payment terms from Info.Net's terms_code map to Odoo account.payment.term records created during schema setup. Multi-contact handling creates separate res.partner contact records under the vendor parent. Lead time data migrates as a custom field on the vendor partner record or to the product.supplierinfo table if lead times vary per product-vendor combination.

Info.Net inventory movements (receipts, issues, adjustments, transfers) carry timestamps, quantities, locations, and cost values. We map these to Odoo stock.move records (the movement log) and stock.quant records (on-hand quantity state). Post dates are preserved as stock.move.date. Location pairs (from_location_id, to_location_id) map to Odoo's stock.location records which we pre-create or reference by name match during import. Cost values attach to stock.move.valuation or stock.quant unit_cost depending on Odoo inventory valuation method configured.

Info.Net supports custom fields on Items, Customers, and Vendors. We extract the full custom field definition set (field name, data type, required flag) during discovery. For each Info.Net custom field we create the corresponding Odoo ir.model.fields record, using x_ prefix for custom fields in Odoo standard. Custom field values are appended as extra columns during the respective object import (Items, Customers, Vendors). Any Info.Net custom fields with no matching Odoo target are flagged in the discovery report for the customer's admin to decide on disposition.

Info.Net User accounts carry role assignments and permission sets tied to manufacturing workflows. We map roles to Odoo's access groups (res.groups) during schema setup. Password hashes cannot migrate between systems; we flag all users for password reset on first Odoo login. Active/inactive status from Info.Net maps directly to Odoo's active flag. Users without an email in Info.Net are held in a reconciliation queue since Odoo requires an email for res.users login.