Migrate from AltheaSuite to Odoo ERP

AltheaSuite Items map to Odoo product.template for the base product definition and product.product for variants (if serial-controlled or lot-controlled). Item code maps to product.default_code, Item name maps to product.name, and standard cost maps to product.standard_price. Custom Item fields discovered from the vendor-mediated schema export map to custom fields on product.template using Odoo Studio field types. Reorder levels from AltheaSuite map to product.rule_ids (stock.route_rule) if the Odoo Reordering Rules app is active.

AltheaSuite custom fields on Items (dropdown, text, numeric types) are discovered during schema profiling by requesting the full custom field definition list from the customer and verifying against the live system during the profile walkthrough. We create equivalent custom fields in Odoo using ir.model.fields with the matching field type (selection for dropdown, char/text for text, float for numeric). Field labels, help text, and placeholder values are preserved. Type mismatches (e.g., AltheaSuite numeric string vs Odoo float) are handled with explicit cast transforms before import.

AltheaSuite Customer records map directly to Odoo res.partner with customer_rank set to distinguish from Vendors. Customer name, contact email, phone, and address fields map to the corresponding res.partner fields. If AltheaSuite stores multiple contacts per customer account, we create a primary res.partner record for the account and additional contact records linked via parent_id.

AltheaSuite Vendor records map to Odoo res.partner with supplier_rank set. Vendor contact info, addresses, and supplier-level flags (vendor-managed inventory indicator) preserve as boolean properties. Purchase vendor code maps to product.supplierinfo for use in Purchase Orders.

AltheaSuite Purchase Orders map to Odoo purchase.order (header) and purchase.order.line (line items). PO number, date, and vendor reference map to their Odoo equivalents. Line item quantities and unit costs map to product_uom_qty and price_unit. Multi-currency fields in AltheaSuite require mapping to the Odoo currency_id on the PO header. Landed cost fields do not migrate directly; we flag these for manual setup in Odoo Purchase Configuration.

AltheaSuite Sales Orders map to Odoo sale.order and sale.order.line. Order number, order date, and customer reference preserve. Fulfillment status (partial vs. complete) maps to the Odoo delivery state via picking_ids. Delivery assignments linked to the Sales Order in AltheaSuite create linked stock.picking records in Odoo via the sale.order.picking_ids relation.

AltheaSuite Work Orders map to Odoo mrp.production (the production order) and mrp.workorder (individual routing steps). The source Item linked to the Work Order becomes the mrp.production.product_id. Production status from AltheaSuite (pending, in-progress, complete) maps to mrp.production.state. Step-level labor and machine time entries migrate as a child table to mrp.workorder time-tracking records if the Odoo Timesheets or Manufacturing Timesheets app is active.

AltheaSuite multi-level BOMs (nested sub-assemblies) are flattened during migration mapping: each BOM level becomes a separate mrp.bom record in Odoo. The top-level BOM references the finished product; sub-assemblies reference their respective intermediate product as product_id, with bom_line_ids pointing to component Items. We preserve the quantity-per-unit at each level in mrp.bom.line.product_qty. Routing operations (work centers, cycle times) map to mrp.routing.workcenter records linked to the BOM if the Odoo MRP Routing or Work Orders app is active.

AltheaSuite serial number assignment records map to Odoo stock.lot. Each stock.lot record stores the lot_name (serial number), product_id (linked to the migrated Product), and the ref field for any supplier or manufacturing lot reference. The serial-to-item linkage is preserved by resolving the parent Item to the correct product.product in Odoo. We extract the full serial-to-item mapping as a child table during the pre-migration dump and re-associate each lot record at the destination. Orphaned serial records (no parent Item) are flagged for manual resolution before finalizing the import.

AltheaSuite lot-controlled Items with lot number and expiry date metadata map to Odoo stock.lot with lot_name set to the lot number and shelf_date set to the expiry date. We migrate lot assignment records with their parent Items and preserve expiry date fields for destinations running FEFO (First Expired First Out) logic in Odoo Inventory. Lot traceability reports in Odoo (track.productionLot) use stock.move.line records linked to the lot to reconstruct the full genealogy.

AltheaSuite reorder level automation per Item maps to Odoo stock.warehouse.orderpoint records (Reordering Rules). We extract the reorder point quantity and minimum/maximum quantities from AltheaSuite Item settings and create corresponding orderpoint records per warehouse in Odoo. If the destination Odoo instance does not have the MRP Multi-Level or Stock apps active, reorder rules are preserved as a configuration inventory document for the customer's admin to set up post-migration.

Vendor-specific cost prices in AltheaSuite map to product.supplierinfo records linked to the Vendor (res.partner) and the Product. Standard selling price lists map to Odoo product.pricelist records. Multi-currency vendor costs in AltheaSuite require mapping to the corresponding Odoo currency on the product.supplierinfo record. We flag any pricing rules that use AltheaSuite-specific discount logic for manual conversion to Odoo Pricelist Rules.