Migrate your Epicor Eclipse data

Eclipse stores customer records in file-based UniVerse dictionaries. We extract via REST API or direct file parsing, normalize address structures (which use dynamic arrays), and map customer-specific pricing, credit limits, and rebate groups to the destination's account model.

Vendor records in Eclipse include PO history, rebate terms, and EDI capabilities. We extract the vendor master, transform multi-value buying codes, and preserve terms and classifications in the destination vendor table.

Part records contain dynamic attributes, substitute/replacement chains, and warehouse-specific stocking data stored as dynamic arrays. We flatten these into standard product tables, flagging user-defined fields that require custom mapping.

Open orders link to customer, part, pricing, and warehouse records. We extract order headers and line detail, preserving order-specific discounts and notes, then insert into the destination's open order table with source reference for reconciliation.

PO records include vendor terms, line items, and receiving status. We extract open POs, map them to destination purchase orders, and flag partially-received orders that require careful line-level migration.

Eclipse tracks on-hand, allocated, and on-order quantities per warehouse per part using multi-value fields. We extract warehouse-level quantities, map bin/location data, and validate that on-hand values match after insertion.

Account structures in Eclipse use non-standard numbering and can include divisions and cost centers in the same field. We extract account masters, segment them per destination requirements, and map existing posting codes to the target system's account structure.

Outstanding invoices and vouchers are extracted with full aging data, customer/vendor references, and payment terms. We preserve open invoice totals, aging buckets, and apply-to information for reconciliation post-migration.

Sales and purchase history spanning 2-5 years is available in Eclipse since it does not auto-purge. We scope historical transactions based on customer requirements (orders, invoices, payments, RMAs), summarize closed jobs, and flag archived documents that should be linked externally rather than imported.

Quote history is optional for migration given cost-benefit tradeoffs. We extract open quotes in full detail and summarize closed quote statistics, noting that Eclipse stores quote lines with configuration and pricing logic that may require transformation.

Tax jurisdiction assignments and rates are tied to customer ship-to locations. We extract the tax code master and associated jurisdiction mappings, flagging any tax code logic embedded in custom UniBASIC programs.

Eclipse organizations may use cost centers as part of the account structure rather than as standalone entities. We extract department definitions and map them to the destination's org structure or account segments.

Eclipse stores document images and attachments in file repositories. We extract document references and metadata, noting that image files may require separate file transfer rather than API insertion.

User records include role assignments, warehouse access, and salesperson links. We extract the user/employee master, map to destination users with role preservation, and flag inactive accounts for review.