Migrate from ECOUNT ERP to Infor CloudSuite Corporate

Ecount Items (the core inventory object covering raw materials, finished goods, and kitted products) map to Infor CloudSuite Item Master with ItemCode, Description, Unit of Measure, Cost, and Price fields. Ecount's BOM links per Item migrate as separate Infor BOM header and BOM lines with multi-level routing. We export item masters via Ecount's Excel download, flatten any print-layout merged cells, normalize unit-of-measure codes to Infor's UoM standard, and load via ION Sync ItemMaster BOD or CSV import. Items with kitting relationships get ItemBOMLink records in Infor.

Ecount Customer records (contact details, payment terms, credit limits, outstanding balances) map to Infor Customer and Ship-To addresses. The Ecount customer code becomes Infor CustomerId; the customer name becomes CustomerName. Payment terms, credit limits, and tax registration numbers migrate to corresponding Infor fields. Outstanding A/R balances from Ecount's auto-retrieved balance fields migrate as opening receivable amounts in Infor CloudSuite Financials.

Ecount Vendor records mirror the customer structure with supplier-specific fields. We map vendor codes, names, contact information, and payment terms to Infor Supplier records. Purchase ordering relationships and vendor-specific lead times also migrate. Incoterms and supplier-specific cost multipliers from Ecount's vendor configuration carry over as supplier attributes in Infor.

Ecount Sales Slips (the transactional document for recording revenue, including line items, quantities, prices, and tax codes) map to Infor CloudSuite Sales Orders and invoices. We extract slips by period from the Ecount report download, preserving line item details, pricing, discount rates, and tax jurisdiction codes. The sales representative from Ecount maps to the Infor salesperson code on the order. Historical Sales Slips migrate as closed Sales Orders with original transaction dates preserved.

Ecount Purchase Slips record incoming inventory and expenses, including incidental cost allocations for landed-cost scenarios. We migrate slip headers and associated incidental cost lines to Infor Purchase Orders and Receipts. Warehouse or plant assignments from Ecount map to Infor Site and Warehouse codes. Open purchase slips migrate as Infor open POs; closed slips migrate as historical receipt records.

Ecount supports multiple BOMs per product with process-level inventory adjustments. We export the full BOM tree (parent item, sub-material links, quantities-per, wastage rates, operation steps) and reconstruct it as Infor BOM Header records with BOM Line children. Multi-level BOMs require iterative tree traversal from Ecount's export. Phantom BOMs in Ecount (non-stocked assemblies) map to Infor Phantom BOM flag. Production routing and work center assignments also migrate where present.

Ecount's accounting structure uses accounts, departments, and cost centers with customizable account codes. We export the full account hierarchy via Ecount's Excel download, cleaning print-layout formatting. Mapping requires aligning Ecount's department-level restrictions to Infor's cost center and company structure (legal entity, business unit, site). Account type (asset, liability, equity, revenue, expense) maps to Infor AccountCategory. We flag any Ecount accounts with formulas or intercompany logic that may require manual reinstallation in Infor OS.

Ecount stores employee data including compensation, attendance, and payroll history. Effective-dated compensation changes need careful sequencing to preserve historical accuracy in Infor. Attendance records migrate as historical time entries; payroll history migrates as closed payroll records. The Ecount employee code becomes Infor EmployeeId; names, department assignments, and employment status map to corresponding Infor fields. Benefits enrollment and deduction codes migrate as benefit plan assignments.

Ecount allows adding, modifying, or deleting input fields with calculation formulas per screen. These custom fields are screen-level and not always exposed in a standard schema. We request the customer's Ecount upload templates during scoping so we can identify active columns. We then create corresponding custom fields in Infor OS with appropriate field types (text, number, date, picklist), and map the Ecount data into those fields during import. Calculation formulas from Ecount screens do not migrate as code; we document them for Infor administrator review.

File attachments linked to Ecount slips and records are downloadable from Ecount but require re-association in Infor. We extract attachment references (file names, linked object type, record ID) and re-link them post-migration in Infor IDM (Infor Document Management) based on the migrated record ID map. PDFs of invoices, purchase orders, and delivery documents migrate as Infor document attachments with appropriate metadata (document type, entity, date).