Migrate from Epicor Eclipse to Dolibarr ERP

Eclipse CUSTOMER records map to Dolibarr ThirdParty entries with type=Customer. Eclipse ship-to addresses stored in SHIP.TO files map to Dolibarr address records linked to the parent ThirdParty. Eclipse customer class and price class fields map to Dolibarr price level or category. We flatten dynamic array address fields (street, city, state, zip, country) into standard Dolibarr address table columns and validate against Dolibarr's country and state/province picklists.

Eclipse vendor records from the VENDOR file map to Dolibarr ThirdParty entries with type=Supplier. Eclipse PO history, rebate terms, and EDI capability flags transfer as supplier notes or custom fields. We map Eclipse buying codes (VENDOR.PRODUCT cross-references) to Dolibarr supplier product references so that purchase orders can display both Eclipse part numbers and vendor part numbers.

Eclipse PRODUCT records map to Dolibarr Product entries with type=Product (for physical goods) or type=Service (for non-stocked items). Eclipse dynamic array attributes—warehouse-specific stocking data, substitute chains, product group assignments—require flattening into Dolibarr product custom fields or multi-line text notes. Eclipse UOM definitions map to Dolibarr unit of measure entries. If the customer uses Eclipse's IDW (Industry Data Warehouse) attributes for electrical distribution, we flag these for manual configuration in Dolibarr because IDW is an Eclipse-specific taxonomy with no direct Dolibarr equivalent.

Open Eclipse orders map to Dolibarr CustomerOrder records with status in progress. Eclipse order headers contain customer reference, order date, terms, and salesperson; these map to Dolibarr Order fields directly. Eclipse order lines map to OrderLine records with product reference, quantity, unit price, and discount. We preserve customer-specific pricing and quantity breaks from Eclipse as Dolibarr line-level prices. Eclipse order notes and special instructions transfer as Dolibarr Order notes.

Open Eclipse POs map to Dolibarr SupplierOrder entries. Eclipse PO fields (vendor, terms, line items, receiving status) map to Dolibarr SupplierOrder fields. Partially-received Eclipse POs require careful line-level tracking because Dolibarr's receiving workflow is simpler than Eclipse's multi-stage receiving and inspection process; we flag any partially-received lines that need special handling during cutover validation.

Eclipse INVENTORY records by warehouse map to Dolibarr Stock entries per warehouse. Eclipse bin locations and rankings map to Dolibarr warehouse location fields. On-hand, allocated, and on-order quantities per warehouse per part transfer as Dolibarr stock values. Eclipse multi-value fields that store multiple quantity types per part require unpacking into separate Dolibarr stock entries per status. We validate total inventory value post-load against Eclipse's inventory valuation report.

Eclipse account structures (which may combine division, cost center, and account number in one field) must be segmented and mapped to Dolibarr's accounting chart. Dolibarr's accounting module supports standard chart of accounts templates (PCG82 for France, generic templates for other countries) that we customize with the customer's Eclipse account structure. Eclipse cost center usage determines whether we create Dolibarr cost center dimensions as separate accounts or as analytical dimensions.

Outstanding Eclipse AR invoices map to Dolibarr CustomerInvoice records with status unpaid. Eclipse AP vouchers map to Dolibarr SupplierInvoice (Bill) records. Aging data and payment terms transfer as invoice metadata. Eclipse apply-to information (which payments were allocated to which invoices) requires mapping to Dolibarr payment allocations. We validate that total AR and AP balances match Eclipse's aging report before declaring the migration phase complete.

Scoping determines which historical records migrate. We typically migrate 2-5 years of sales history (orders, invoices, payments, RMAs) per the customer's requirements. Eclipse closed orders older than the retention period are summarized or excluded. Complete invoice and payment history is optional and adds cost because of volume. We document the scope upfront and validate historical totals against Eclipse's period-end reports.

Open Eclipse quotes map to Dolibarr Propal records. Eclipse quote lines with configuration details and quantity break pricing transfer as Dolibarr PropalLine entries. Closed quote statistics (win rate, average value) migrate as summary records in a custom field or note because Dolibarr does not have a native closed-quote history object. Quote expiration dates and status transfer to Propal validity dates and status.

Eclipse tax jurisdiction assignments tied to customer ship-to locations map to Dolibarr tax rules per customer and per product category. Eclipse tax codes embedded in custom UniBASIC programs are flagged for manual configuration in Dolibarr's tax management module. We export the Eclipse tax code master and jurisdiction mappings as a CSV that the customer's admin imports into Dolibarr's tax rules table.

Eclipse user records (with role assignments, warehouse access, and salesperson links) map to Dolibarr User entries. Eclipse salesperson codes transfer as Dolibarr user tags or custom fields so that orders and quotes can be attributed to the correct salesperson. We extract user status (active/inactive) and map to Dolibarr User active flag. Eclipse security settings and authorization keys do not transfer and require reconfiguration in Dolibarr's permission system.