Migrate from WinMan ERP to Odoo ERP

WinMan maintains a fully integrated financial module with chart of accounts, journal entries, and AP/AR. We map accounts 1:1 using account codes, preserving cost-centre assignments where WinMan uses multi-entity structures. WinMan's account hierarchy maps to Odoo's chart of accounts structure (account.account model). Odoo's Accountant app requires configuration of debit/credit account types and tax mapping, which we set up during the schema-design phase before any data loads.

WinMan Items with Bills of Materials map to Odoo Product Templates with associated BOM records (mrp.bom model). WinMan's BOM type (kit, single-level, multi-level) maps to Odoo BOM type (kit, manufacturing). We export the full product hierarchy including component links and preserve the bom_line parent reference through explicit linkage. Odoo's product type (stockable, consumable, service) is assigned based on WinMan item type during the mapping phase.

WinMan's product configurator stores feature/option matrices with rules and dependencies. Where configured products are represented differently in Odoo, we decompose the configuration into its component BOM lines and map them individually, preserving the parent-child relationship through explicit product variant linkage. The original WinMan feature/option matrix is documented in a custom Odoo field for admin reference. Odoo's optional_product_configurator module handles this natively in later versions, and we use it where the customer's target Odoo version supports it.

WinMan customer records including addresses, contact details, and credit terms map to Odoo Partner records (res.partner) with the customer flag set. WinMan's customer-to-site mapping translates to Odoo delivery addresses on the partner record. Multi-currency assignments on WinMan customers map to Odoo's currency property on the partner. We preserve the customer code as an external reference field for reconciliation.

WinMan vendor records with purchasing terms and lead times map to Odoo Partner records with the supplier flag set. Vendor-specific price lists from WinMan map to Odoo product supplierinfo records (purchase.pricelist). Lead times map to the seller_delay field on the product's supplier info. We map vendor addresses as delivery addresses on the supplier partner record.

Open and historical sales orders map to Odoo sale.order records. WinMan guidance specifies that live orders migrate last, near go-live; we honour this sequencing explicitly. We export a snapshot of open orders immediately before cutover, then replay any delta orders that occurred during the final testing window. Sales order lines map to sale.order.line with product, quantity, and pricing. WinMan's delivery commitments map to Odoo's commitment_date on the order.

WinMan purchase orders and associated goods-received notes map to Odoo purchase.order and stock.picking records. Where purchase orders reference configured BOMs, we preserve the item-link relationship during migration by resolving the product template and variant references in Odoo before the PO import. Odoo's RFQ-to-PO workflow is documented for the customer's purchasing team during training handoff.

WinMan work orders with routing steps, labour allocations, and work-centre assignments require field-level mapping to Odoo's mrp.production model. WinMan's work order structure varies by manufacturing mode (job, batch, repetitive), and Odoo's MRP app supports all three modes with workcentres and work order tracking. We map WinMan work-centre codes to Odoo mrp.workcenter records and preserve the routing sequence. WinMan labour allocations map to Odoo's workorder time-tracking fields.

Current stock levels, bin locations, and batch/serial numbers map to Odoo stock.quant records. WinMan's warehouse-zone assignments map to Odoo's warehouse and location hierarchy (stock.location model). We preserve the unit of measure from WinMan and map it to Odoo's uom.uom model. For stock valuations, we map WinMan's cost method to Odoo's inventory valuation configuration (manual, automated, periodic).

Traceability links between batch/serial numbers, incoming materials, and finished goods require careful sequencing. WinMan stores traceability graphs linking raw material lots to production batches and finished goods. We map these to Odoo stock.production.lot records and preserve the traceability graph through Odoo's lot tracking reports. Odoo's 'lot_on_product_form' and 'block_tracking' traceability settings are configured during the schema-design phase to match the customer's regulatory requirements.

WinMan supports user-defined fields on standard objects. We extract custom field definitions and map their values to equivalent custom fields in Odoo using the ir.model.fields model. Where Odoo does not have an equivalent field type, we flag the field for manual review and note the value in a migration reference column in the imported data. Odoo's technical settings or a custom module handles field creation before data import begins.

WinMan user accounts with role-based permissions can be exported, but role definitions vary between ERP systems. We extract WinMan user records and map them to Odoo res.users. WinMan role names and access scope are mapped to Odoo access rights groups (res.groups). We flag any security differences between WinMan and Odoo permission models during discovery. Odoo access rights are rebuilt using Odoo's security groups and record rules rather than replicated as-is.