Migrate from Epicor Eclipse to Infor CloudSuite Corporate

Eclipse Customer records (CUSTOMER file) with ID, name, credit limit, terms, and price class map to Infor Cloudsuite Customer (Distribution) or Party (Industrial) records. Eclipse ship-to addresses (SHIP.TO) with location-specific tax jurisdictions map to Infor Customer Ship-to addresses. We extract customer-specific pricing classes, discount schedules, and credit hold status from Eclipse and flag any pricing rules that require manual rebuild in Infor's pricing engine.

Eclipse Vendor records include PO history, rebate terms, EDI capabilities, and buying codes stored as multi-value fields. We extract the vendor master, transform multi-value buying codes into normalized vendor item cross-reference records in Infor, and preserve terms, classifications, and EDI setup flags. Any vendor-specific rebate accrual balances (SPA, SPJ, rebate claim history) require explicit mapping because Eclipse stores these in separate files that may not be covered by standard Eclipse API endpoints.

Eclipse PRODUCT records contain item ID, description, product group, UOM definitions, and extended attributes stored as dynamic arrays. We flatten dynamic array attributes into Infor Item custom fields, preserving product group hierarchy and UOM conversion definitions. Substitute and replacement part chains from Eclipse's product cross-reference files map to Infor's alternate item relationships. IDW (Industry Data Warehouse) attributes, if used, are extracted as extended item attributes.

Eclipse stores on-hand, allocated, and on-order quantities per warehouse per part using multi-value fields in the INVENTORY file. We split these into Infor warehouse-specific inventory records with bin location, lot/serial tracking, and ranking data extracted from Eclipse's bin location structures. Multi-warehouse operations require branch-level inventory reconciliation because Eclipse may hold different quantities per branch with inter-branch transfer rules that map to Infor's transfer order logic.

Eclipse Order records with headers, line items, pricing, warehouse assignments, and customer references map to Infor Sales Orders. We extract order-specific discounts, notes, and allocation status, preserving the line-level relationship to the source customer and part records. Partially-shipped orders require careful line-level status mapping because Eclipse tracks shipment history that may affect order completeness flags in Infor.

Eclipse PO records include vendor terms, line items, and receiving status. We extract open POs, map them to Infor Purchase Orders, and flag partially-received orders that require line-level migration because Infor tracks received quantities against PO lines and Eclipse tracks receipt history in separate files. Vendor drop-ship flags and special handling codes require explicit mapping to Infor PO terms.

Eclipse account structures use non-standard numbering and may encode divisions and cost centers in the same field. We extract account masters, segment them per Infor's GL account structure (which typically separates company, division, department, and account), and map existing Eclipse account numbers to the Infor hierarchy. Any cost center logic embedded in Eclipse account numbers requires analysis during scoping to determine whether cost centers become separate Infor cost center entities or remain part of the GL segment.

Eclipse outstanding invoices (AR) and vouchers (AP) 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 against Infor's AR/AP aging reports post-migration. Customer credit holds from Eclipse must map to Infor credit limit and hold rules that are configured separately from the data migration.

Open quotes in Eclipse with full line detail migrate to Infor Quotes. Eclipse stores quote configurations and special pricing agreements at the quote line level, which we map to Infor quote line pricing with manual verification of pricing engine results post-load. Closed quote statistics migrate as summary records if scoped by the customer; quote history is typically not migrated in full because of cost-benefit tradeoffs.

Eclipse self-populating work queues (credit hold queue, order exception queue, warehouse-in-process status queue, customer calling queue) are tightly coupled to Eclipse's hot-key interface and user assignment logic. These queues do not have a direct Infor equivalent and do not migrate as functional code. We document the active queue configurations, assignment rules, and escalation logic during scoping and deliver a written inventory for the customer's Infor admin to rebuild using Infor OS workflow tools.

Eclipse stores document images, attachments, and proof-of-delivery scans in file repositories outside the database. We extract document references and metadata, mapping file paths to Infor Document Management (IDM) storage locations. The actual document files require separate file transfer rather than API insertion. Document imaging and signature capture configurations do not migrate and require separate replacement planning.