Migrate from MRPeasy to Odoo ERP

MRPeasy Vendors map to Odoo res.partner records with partner_type set to vendor. We extract vendor name, code, contact information, address, and purchase terms from MRPeasy's vendor export. MRPeasy's purchase terms per vendor-item pair map to Odoo's vendor price lists on the Product form under the Purchase tab. This is the first object imported because Items in MRPeasy reference vendor purchase terms and Odoo Product suppliers must exist before supplierinfo records are created.

MRPeasy Items are the core stock record and map to Odoo product.product (storable products). We map part number to default_code, item name to name, unit of measure to uom_id (with UoM category matching), cost from MRPeasy's cost_price to Odoo's standard_price, and sale price to list_price. MRPeasy's item_type (make-to-order, make-to-stock, assembly) maps to Odoo's route selection (MTO vs MTS). For matrix BOM items (Professional+), we set the product as a phantom BoM in Odoo. MRPeasy's 3000-line CSV cap requires chunking for large catalogs; we split item exports into multiple files and track import completion to avoid duplication.

MRPeasy BOMs map to Odoo mrp.bom records. The parent manufactured item maps to Odoo's product_id, component items map to bom_line_ids with product_id and product_qty. MRPeasy multi-level BOMs (BOM referencing sub-assemblies that are themselves BOMs) map to Odoo's multi-level BoM structure using the same parent-child hierarchy. Co-product BOMs from MRPeasy Professional+ map to Odoo by-products on the BOM form. We create BOM records after all component Items exist in Odoo to satisfy product_id foreign key constraints.

MRPeasy Routings define the production operation sequence and map to Odoo mrp.routing with mrp.routing.workcenter lines for each operation. We map MRPeasy operation sequence to Odoo sequence, workstation to mrp.workcenter (which we pre-create from MRPeasy workstation data), and labor times to duration computation. Overlap and parallel execution flags from MRPeasy Routings map to Odoo's workorder overlap field. MRPeasy Routings without a linked Workstation cannot be created in MRPeasy; we ensure Odoo Workcenters exist before importing Operations by pre-running a workstation migration pass. Piece-payment operations map to Odoo mrp.workorder time tracking fields.

MRPeasy MOs map to Odoo mrp.production as the parent manufacturing order. For each MO with an associated Routing, Odoo auto-generates mrp.workorder child records (one per operation). We map MRPeasy MO status (New, In Progress, Done, Canceled) to Odoo state (draft, confirmed, progress, done, cancel). MRPeasy's Dynamic Rescheduling engine recalculates dates on any BOM or Routing change; we flag open/active MOs during scoping, advise customers to close or freeze orders before import where possible, and document any post-import reschedule delta. Historical MOs migrate as read-only records. Closed and canceled MOs preserve their production history.

MRPeasy Customers map to Odoo res.partner records with partner_type set to customer. We map customer name, code, contact information, billing and shipping addresses, tax ID (mapped to Odoo's vat field for VAT compliance), and payment terms. MRPeasy's price list assignment per customer maps to Odoo res.partner property_product_pricelist. MRPeasy customer-specific pricing from price list lines maps to Odoo product.pricelist.item records linked to the customer. We resolve MRPeasy's customer code as an external identifier in Odoo for dedupe on re-import.

MRPeasy Price Lists (customer-specific and product-specific) map to Odoo product.pricelist records. Each price list line maps to product.pricelist.item with product_id, min_quantity, and fixed_price or percentage mapped from MRPeasy's price and discount fields. Currency from MRPeasy's multi-currency price list maps to Odoo pricelist currency. We create pricelists before customers and before importing sales orders so that pricing is active at go-live.

MRPeasy inventory levels per storage location map to Odoo stock.quant records linked to stock.location and product.product. MRPeasy's 3000-line CSV import cap applies to inventory uploads; large warehouses with 10,000+ SKUs require four or more chunked import passes. We segment the inventory export by storage location to respect both the line cap and MRPeasy's requirement that Storage Locations exist before inventory can be assigned to them. MRPeasy's qty_on_hand, qty_reserved, and qty_available map to Odoo's reserved_qty, quantity, and available_quantity fields on stock.quant.

MRPeasy Stock Lots with batch traceability map to Odoo stock.production.lot records linked to product.product. We map lot/batch number to name, expiry date to product_expiry_tracking and removal_date, and quantity to the linked stock.quant record. MRPeasy's lot status (Received, etc.) is informational; we do not attempt to map it to Odoo's internal lot state. MRPeasy serial number tracking (Professional+) maps to Odoo lot tracking with the serial number field as lot name, enabling full lot traceability in Odoo's lot traceability report.

MRPeasy Transfer Orders between sites and storage locations map to Odoo stock.picking records with picking_type_id set to internal transfer. We map source location and destination location to Odoo's location_id and location_dest_id, product quantities to move_lines, and Transfer Order status to stock.picking state. MRPeasy's 'Received' status does not auto-complete in MRPeasy; we set Odoo moves to done state based on the MRPeasy received status flag. In-transit Transfer Orders from MRPeasy land in Odoo as confirmed or assigned moves pending the customer's warehouse team confirmation.

MRPeasy user records from Settings -> User management map to Odoo res.users. We extract active users, their email addresses (used as the Odoo login), name, and role/permission group assignment. MRPeasy role names map to Odoo access groups (Manufacturing / Sales / Inventory / Administration). We match MRPeasy owners on manufacturing orders and inventory records to Odoo users by email for OwnerId resolution during MO and quant import. Inactive MRPeasy users are exported as inactive Odoo users to preserve audit trails.