Migrate from ERPAG to Odoo ERP

ERPAG Items map to Odoo Product records. We preserve SKU, product description, standard cost, sale price, and stock levels. ERPAG's per-warehouse stock levels require multi-warehouse activation in Odoo and map to stock.quant records tied to the correct stock.location. ERPAG's barcode field maps to product.barcode. Stock-keeping unit type (stockable, consumable, service) carries over as product.type. Multi-warehouse item assignments require location-based lookups during import rather than a direct field-to-field transfer.

ERPAG Customer records map to Odoo res.partner with the customer flag set to True. We transfer contact name, billing address, shipping address, payment terms, and financial overview fields. ERPAG's B2B portal assignment (Advanced plan only) does not migrate because the portal configuration is ERPAG-specific; we document the customer portal access list as a reference for the customer's Odoo administrator to configure in Odoo Portal post-migration. ERPAG's financial overview balance fields map to receivable account fields in Odoo Partner accounting properties.

ERPAG Supplier records map to Odoo res.partner with the supplier flag set to True. We preserve contact data, purchasing terms, and the double-SKU cross-reference fields that map ERPAG's internal SKU to the supplier's own SKU. This supplier-SKU mapping is critical for Purchase Order automation in Odoo and is stored in Odoo's seller_ids on the Product record. ERPAG's payment terms on Supplier records map to Odoo's property_supplier_payment_term on res.partner.

ERPAG Sales Orders map to Odoo sale.order with line items, pricing, order status, and payment status preserved. ERPAG's payment_status column from the XLS export maps to Odoo's order state (sale_order_state or invoice_status depending on the Odoo configuration). ERPAG linked documents and custom fields on Sales Orders require file export from ERPAG and re-upload to Odoo as ir.attachment records linked to the sale.order. Packing list associations migrate as delivery order references.

ERPAG Invoices map to Odoo account.move records of type out_invoice. ERPAG's invoice status (issued, paid, credit note) maps to Odoo's state and invoice_payment_state fields. ERPAG credit notes map to Odoo account.move of type out_refund. Tax amounts and currency codes from ERPAG carry over to Odoo's tax line structure and currency settings. Historical paid invoices retain their payment records in Odoo accounting. ERPAG e-invoice formats (Norway EHF is supported in ERPAG) require separate configuration in Odoo through a localization module.

ERPAG Purchase Orders map to Odoo purchase.order with supplier reference, line items, and fulfillment status. Goods received state from ERPAG maps to Odoo's delivered quantity on purchase.order.line. ERPAG's double-SKU supplier entry maps to the seller_ids on the Odoo Product record during import. Purchase Order attachments migrate as ir.attachment records. If ERPAG's Advanced Automation triggers purchase orders automatically, that logic is documented separately for Odoo purchase procurement rules rebuild.

ERPAG Quotations map to Odoo sale.order records in the draft (quotation) state. Validity dates, line item pricing, and custom fields carry over. ERPAG quotation-to-Sales-Order conversion references are noted in the migration inventory as Odoo sales team may want to create follow-up opportunities from these records. Odoo merges quotation and order into a single model; ERPAG separates them, so quotation history is preserved as Odoo sale.order records with state=draft.

ERPAG Work Orders map to Odoo mrp.production (manufacturing orders). BOM references, production status, and cost data transfer including ERPAG's estimated versus actual cost fields. Production scheduling dates from ERPAG map to Odoo mrp.production date_planned_start and date_finished. ERPAG work order dependencies and routing sequences require mapping to Odoo mrp.workorder if the customer's ERPAG setup uses multi-step routing. Status values (pending, in progress, completed, cancelled) map to Odoo's confirmed, progress, done, cancel states.

ERPAG warehouses map to Odoo stock.warehouse records with independent tax, currency, and price list configurations. Multi-warehouse activation in Odoo must be enabled before import. ERPAG's per-warehouse price lists map to Odoo's product.pricelist records associated with each warehouse's location hierarchy. Geo-location data from ERPAG warehouses maps to Odoo stock.location records within the warehouse. Each warehouse must be configured in Odoo with corresponding incoming and outgoing picking types before stock quant import begins.

ERPAG BOMs map to Odoo mrp.bom records. Multi-level BOM nesting (BOM referencing sub-assemblies that are themselves BOMs) preserves structure in Odoo's product.product and mrp.bom hierarchy. BOM type (kit versus manufacturing) maps from ERPAG's BOM type selection. ERPAG BOM cost data transfers to Odoo's Product standard cost field, with estimated versus actual cost preserved as metadata on the mrp.production record. ERPAG BOMs associated with Items export from the Items endpoint and require cross-reference resolution to establish the Odoo product-product BOM linkage.

ERPAG user records and role-based permission assignments map to Odoo res.users with internal user type. We export all active and inactive users from ERPAG and map their role assignments to Odoo access rights groups (Inventory User, Manufacturing User, Sales User, etc.). ERPAG document restriction rules map partially to Odoo's record rules (ir.rule) but permission sets are destination-specific and require rebuild by the customer's Odoo administrator. Active versus inactive status carries over to user.active in Odoo.

ERPAG custom field definitions on Items, Sales Orders, Customers, Suppliers, and Work Orders are enumerated during scoping. ERPAG custom fields use Administration > Custom Fields for document-linked and arbitrary value types, with up to 15 custom fields per document. We map these to Odoo Properties (ir.property) for cross-model fields or create custom field columns (ir.model.fields) via Odoo Studio or direct SQL migration for object-specific fields. Document-linked ERPAG custom fields export as file attachments and re-attach in Odoo to the corresponding record.