Migrate from Epicor Eclipse to Odoo ERP

Eclipse customer records stored in UniVerse file dictionaries with dynamic array address fields map to Odoo Contact records. Eclipse's multiple ship-to addresses per customer become separate Contact records under the same parent Contact. Customer-specific pricing tiers, salesperson assignments, and credit limits transfer to Odoo Contact fields and res_partner properties. Customer ERP customer ID becomes the Odoo external ID for cross-reference.

Eclipse vendor records include PO history, rebate terms, EDI capabilities, and buying codes stored as MultiValue fields. We extract the vendor master, normalize buying codes to Odoo Supplier Pricelists, and preserve vendor terms and EDI flags as Contact properties and Purchase configuration fields. Vendor account numbers map to Odoo Contact reference fields.

Eclipse part records contain dynamic attributes, substitute and replacement chains, warehouse-specific stocking data, lot/serial tracking, and substitute relationships stored as dynamic arrays. We flatten these into Odoo Product Templates with Variants (if attribute-based sizing applies), extract warehouse-level quantities to Odoo quant records, and flag user-defined dictionary fields that do not map to standard Odoo product fields. Product ERP ID becomes the Odoo external ID.

Open orders link to customer, part, pricing, and warehouse records. We extract order headers and line detail with order-specific discounts and notes, preserving the original order number as the Odoo name. Eclipse order-specific pricing and customer-specific contract prices map to Odoo Sale Order Lines with manual price override where applicable. Warehouse assignment per line maps to Odoo's multi-warehouse picking rules.

PO records include vendor terms, line items, and receiving status. We extract open POs, map them to Odoo Purchase Orders, and flag partially-received orders that require line-level status preservation. PO line taxes from Eclipse tax jurisdiction assignments migrate to Odoo fiscal positions or line-level tax selection based on vendor country.

Eclipse tracks on-hand, allocated, and on-order quantities per warehouse per part using MultiValue fields. We extract warehouse-level quantities per bin/location to Odoo Stock Quants with location_id resolved per warehouse. Lot and serial number tracking migrates to Stock Production Lot. Allocation status from Eclipse maps to Odoo reservation state on quants.

Eclipse account structures use non-standard numbering and can embed divisions and cost centers in a single field. We extract the account master, segment per Odoo's chart of accounts structure (account type, account code, parent_id), and map external account references to Odoo account codes. If Eclipse uses cost centers as part of account numbering rather than standalone entities, we propose an Odoo analytic account plan for cost center tracking post-migration.

Outstanding invoices and vouchers are extracted with full aging data, customer/vendor references, payment terms, and apply-to information. We preserve open invoice totals, aging buckets, and partial payment allocations in Odoo Account Moves with reconciled link tracking. AR aging from Eclipse maps to Odoo Account Aged Trial Balance; AP aging maps to Odoo Vendor Bill reconciliation.

Sales history, purchase history, and invoice history spanning 2-5 years migrate as locked Odoo Account Moves. We scope historical volume during discovery to avoid surprise extraction volumes, noting that Eclipse does not auto-purge unlike most SQL-based ERPs. Invoice PDF references migrate as Odoo ir_attachment records linked to the corresponding Account Move where available.

Open Eclipse quotes migrate in full detail as Odoo Draft Sale Orders. Quote lines with configuration and pricing migrate to Sale Order Lines. Closed quote statistics (total quoted, won/loss counts, average close time) migrate as summary records in a custom Odoo model or as analytic entries for reporting. Quote expiration dates map to Odoo validity_date on Sale Orders.

Eclipse tax jurisdiction assignments tied to customer ship-to locations map to Odoo Account Tax records with country-based fiscal position assignment. Tax rate values migrate to Odoo tax amounts. Any tax calculation logic embedded in custom UniBASIC programs is flagged in the handoff inventory as requiring redevelopment in Odoo using Python tax computation or an Odoo fiscal position rule.

Eclipse organizations may use cost centers as part of the account structure rather than standalone entities. We extract department definitions, map them to Odoo HR Department for organizational structure, and propose an Analytic Account plan for cost-center tracking across orders and invoices post-migration. If Eclipse cost centers are purely financial and not HR-related, we recommend using Odoo Analytic Accounts exclusively.