Migrate from Blue Link ERP to Odoo ERP

Blue Link Customer records map directly to Odoo res.partner with the customer flag set to True. Contact details, multi-currency settings, credit limits, and payment terms transfer as partner fields (property_payment_term_id, property_supplier_payment_term_id, credit_limit). Credit status from Blue Link's AR module is preserved in a custom field for reconciliation after migration. Multi-address customer records in Blue Link map to multiple res.partner address records linked by parent_id.

Blue Link Vendor records map to Odoo res.partner with supplier flag set to True. Address, payment terms, and multi-currency flags transfer directly. Vendor-to-PO linkage is preserved as a mapping note; the customer reconciles vendor references after Purchase module activation in Odoo. Vendors without an active PO relationship are imported as inactive partners for reference.

Blue Link inventory items map to Odoo product.product records. Blue Link's kit configurations map to Odoo's product type = 'consu' or 'product' with a linked mrp.bom (bill of materials). Multi-UOM items require consolidation strategy: if Odoo's unit of measure conversion is active, we preserve all UOM variants; if not, we consolidate to a primary SKU and flag secondary UOM records for manual re-entry. Reorder points from Blue Link transfer to Odoo's rule-based replenishment (stock.replenishment).

Blue Link lot numbers and serial numbers map directly to Odoo stock.lot records linked to product.product. Lot traceability at the shipment line level is preserved using stock.move.line records with lot_id and lot_name mapped from Blue Link's lot assignment fields. For regulated distributors (pharma, food), we validate that the Odoo lot's use_date (expiry) and removal_date fields are populated from Blue Link's lot metadata if available.

Open sales orders are migrated last, just before Go-Live, per Blue Link's migration documentation recommendation. We extract order headers and line items, map order status to Odoo sale.order state (draft, sale, done), and preserve partial-shipment status in a custom field. Any order placed between the initial extraction and the final migration delta requires a targeted re-extract within 24 hours of Go-Live. We run a delta validation check to catch orders placed in the overlap window.

Open purchase orders map to Odoo purchase.order with vendor_id resolved from the Vendor mapping. PO line items map to order lines with product_id, product_qty, and price_unit from Blue Link. Receipt linkages from Blue Link do not transfer automatically; we flag them in the migration runbook for manual reconciliation against stock.picking records in Odoo after Go-Live.

Blue Link AP records (vendor invoices, payment terms, cash requirements) map to Odoo account.move records in the vendor bill context. Unpaid and partially paid invoices require status reconciliation: Blue Link's invoice status (open, partial, paid) maps to Odoo's account.move state (draft, posted, reconciled). We flag any invoice with a remaining balance for manual review because Odoo's payment reconciliation workflow differs from Blue Link's AR/AP aging view.

Blue Link AR records (invoices, collections tracking, credit checks, cash application) map to Odoo account.move in the customer invoice context. Collections history does not transfer as activity log entries; we document the last collection date as a custom field on the partner record. Credit check history migrates as a note or custom field on res.partner rather than a native Odoo credit management record.

Blue Link's Chart of Accounts hierarchy maps to Odoo account.account with account type mapping (receivable, payable, liquidity, other). Custom segments or departmental cost centers in Blue Link require reconfiguration in Odoo: either as separate account codes (recommended) or as analytic account tags. Account numbers that conflict with Odoo's reserved number ranges (1-9 for system accounts) are flagged and remapped during schema deployment. We deliver a written account remapping table as part of the migration runbook.

Blue Link multi-warehouse and bin-level tracking maps to Odoo's stock.warehouse (location type view) with child stock.location records for bins and sub-locations. Bin-level assignments from Blue Link transfer to Odoo stock.location with location_complete=True. If the destination Odoo instance does not have the Inventory app activated, warehouse and location records are held for post-activation import. We flag any bin records exceeding Odoo's 64-character location name limit for truncation during migration.